Ramblings of an old Doc
Is Windowblinds or is KB5051987 Responsible?
Published on February 13, 2025 By DrJBHL In OS Customization

I ran into a rather knotty problem when trying to import RnD's port of 2of3's WB "Endeavour" docks into Winstep Extreme.

Luckily for me (maybe not so lucky for Jorge), I was able to catch him on IM and work through this and a problem my weather module had connecting as it turns out due to Bitdefender. Thank you, my friend.   

Turns out, the only way I can get the WSX Preferences Theme Import to work that is, to open the Windows File Manager is by changing to the default W11 skin. I don't think Start11 is at all involved in this.

My current W11 is 24H2 build 26100.3194 from a recent update KB5051987 on 2/12/25. My Winstep Extreme is 24.4 and my WB is 11.02 (017 x64 - Windows 11 Edition). My Start11 is Version 2.51.

I'd supply screenies, but I don't think they'd add anything.


Comments
on Feb 13, 2025

Just in case Neil reads this, the problem seems to happen in GetOpenFileName of comdlg32.dll. This should show the standard Open File dialog but the dialog doesn't even get to appear unless WB is using the default W11 skin.

on Feb 13, 2025

You need to update to WB 11.04 rather than 11.02

This is an issue introduced by Microsofts latest update and we updated WB a while back for this but for some reason some people do not have the update.

on Feb 13, 2025

Neil Banfield

You need to update to WB 11.04 rather than 11.02

This is an issue introduced by Microsofts latest update and we updated WB a while back for this but for some reason some people do not have the update.

The reason I never dl'd it was that in the change log Sean stated that "it resolved an issue of not being able to open file explorer on insider builds of Windows 11." I'm not part of the insider program and felt I didn't need it.

Perhaps had "WB 11.04 will be needed in the near future for an anticipated W11 cumulative update" been posted I would have downloaded and installed it. It was never offered via the regular update mechanism as I've never rejected one of those.

on Feb 13, 2025

DrJBHL


Quoting Neil Banfield,

You need to update to WB 11.04 rather than 11.02

This is an issue introduced by Microsofts latest update and we updated WB a while back for this but for some reason some people do not have the update.



The reason I never dl'd it was that in the change log Sean stated that "it resolved an issue of not being able to open file explorer on insider builds of Windows 11." I'm not part of the insider program and felt I didn't need it.

Perhaps had "WB 11.04 will be needed in the near future for an anticipated W11 cumulative update" been posted I would have downloaded and installed it. It was never offered via the regular update mechanism as I've never rejected one of those.


At the time of writing when it went up as beta it was just insider builds.  Microsoft moved it to release sooner than anticipated and on versions of Windows you wouldn't expect too (23H2 for example)

on Feb 13, 2025

Neil Banfield

At the time of writing when it went up as beta it was just insider builds. Microsoft moved it to release sooner than anticipated and on versions of Windows you wouldn't expect too (23H2 for example)

And here we are. I'm very possibly the only non-dev/I.T./Hitech person here on WC...so I rely on those who specialized in those domains (no pun intended) to update things as they change...which isn't really fair as they have more to do than to keep updating me endlessly...but my arm (again no pun intended) could be twisted and I'd admit to harboring the wish it could be so.

Thanks for all you do for us, and your patience with those of us who learned to use the digital abacus later in life than the analog one. Cheers .