New Version of ExplorerPatcher

The-Hive · Jul 3, 2022

Johnboy200 said:
Just be aware that when MS update KB5014668 installs the Start Menus will stop working if you have EP installed. At the moment you can uninstall KB5014668 and continue to use EP but soon that won't be an option.

The only thing I had trouble with was win+x not working with that update, Start menu worked fine on one machine but not another, not a problem as I use OpenShell for a start menu

austinjklim · Jul 3, 2022

The-Hive said:
The only thing I had trouble with was win+x not working with that update, Start menu worked fine on one machine but not another, not a problem as I use OpenShell for a start menu

Same here. Only issue was win+x on that update, everything else worked fine. It isn't a big thing but I guess i got used to using Win+x to go into apps and features and other settings quickly.

Another question on symbols, valinet previously mentioned that the symbol files are provided by windows for stable build "b" releases. So would downloading those symbol files make EP work on a newer build windows, despite EP not being supported for said newer build? And if so, could anyone show me how to do just that. To be very honest, i just converted over to win11, and the taskbar is a deal-breaker for me. really appreciate valinet for all the time and work he done so far.

Johnboy200 · Jul 4, 2022

austinjklim said:
Same here. Only issue was win+x on that update, everything else worked fine. It isn't a big thing but I guess i got used to using Win+x to go into apps and features and other settings quickly.

Another question on symbols, valinet previously mentioned that the symbol files are provided by windows for stable build "b" releases. So would downloading those symbol files make EP work on a newer build windows, despite EP not being supported for said newer build? And if so, could anyone show me how to do just that. To be very honest, i just converted over to win11, and the taskbar is a deal-breaker for me. really appreciate valinet for all the time and work he done so far.

Isn't Win+X the same as right clicking the start button?

The-Hive · Jul 4, 2022

austinjklim said:
Same here. Only issue was win+x on that update, everything else worked fine. It isn't a big thing but I guess i got used to using Win+x to go into apps and features and other settings quickly.

Another question on symbols, valinet previously mentioned that the symbol files are provided by windows for stable build "b" releases. So would downloading those symbol files make EP work on a newer build windows, despite EP not being supported for said newer build? And if so, could anyone show me how to do just that. To be very honest, i just converted over to win11, and the taskbar is a deal-breaker for me. really appreciate valinet for all the time and work he done so far.

That is all a bit beyond me, it either works or it don't :ROFLMAO:

valinet · Jul 4, 2022

austinjklim said:
Same here. Only issue was win+x on that update, everything else worked fine. It isn't a big thing but I guess i got used to using Win+x to go into apps and features and other settings quickly.

Another question on symbols, valinet previously mentioned that the symbol files are provided by windows for stable build "b" releases. So would downloading those symbol files make EP work on a newer build windows, despite EP not being supported for said newer build? And if so, could anyone show me how to do just that. To be very honest, i just converted over to win11, and the taskbar is a deal-breaker for me. really appreciate valinet for all the time and work he done so far.

EP already downloads and extracts the required info from the symbol files, if any and if the files are available.

I have investigated the issue with Win-X here, the problem was not the unavailability of symbol files, or maybe that plus the fact that the layout of the internal class that represents the context menu (`CLauncherTipContextMenu` from `twinui.pcshell.dll`) has changed a bit: it now implements a new interface (`ILauncherTipContextMenuMigration`) which, at the moment, seems only to implement some method that deletes "obsolete" links from the Win-X menu. Maybe this has something to do with people failing to mod the menu contents as of lately...? I think I read about this somewhere. Anyway, this should be explored more, I think the behavior can be disabled by (maybe) setting `WinXMigrationLevel` (DWORD) to `1` in `HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced` prior to installing the newer OS build, but yeah, I haven't tested that. The disassembly of `twinui.pcshell.dll` references that (look in `CLauncherTipContextMenu::RunMigrationTasks`). More details in the commit notes, but, again, I haven't explored this more, so don't know much more info (I use the stock Win-X menu): General: Fixed a bug that had the Start button context menu / Win-X m… · valinet/ExplorerPatcher@e988bbb. As far as this menu is concerned, the internal implementation is the same and shared between what is presented when the Windows 10 taskbar is used and when the Windows 11 taskbar is used.

Anyway, the latest version of EP (22000.778.47.1) should end this saga, for now: it fixes the problem with Win-X not working (and potentially locking the shell).

hdmi · Jul 4, 2022

tbmljk · Jul 4, 2022

Nice job, Valinet. Thanks for the effort. I did look into the registry setting for WinXMigrationLevel` (DWORD) to `1`, unfortunately it was preset to 1, nothing to change, after the update. Yeah, the Win X menu used to be modifiable, no longer.

valinet · Jul 5, 2022

tbmljk said:
Nice job, Valinet. Thanks for the effort. I did look into the registry setting for WinXMigrationLevel` (DWORD) to `1`, unfortunately it was preset to 1, nothing to change, after the update. Yeah, the Win X menu used to be modifiable, no longer.

Thanks. When it is set to 1, the code skips removing things. Try some old method of populating the menu with something and check if the value in the registry changes, triggering explorer to clear the menu…? After the code executes and removes stuff, it sets that registry entry to 1.

austinjklim · Jul 5, 2022

Thanks valinet for your time and effort. Prior to 778 the WinXMigrationLevel was also at 1, after update to 778 it's the same at least for now. Win+x is working for me. But if I come across this issue again i'll try mess with said registry.

valinet · Jul 5, 2022

austinjklim said:
Thanks valinet for your time and effort. Prior to 778 the WinXMigrationLevel was also at 1, after update to 778 it's the same at least for now. Win+x is working for me. But if I come across this issue again i'll try mess with said registry.

Win-X works indeed, what is not working anymore with this new build is adding custom things to the menu, since Microsoft apparently changed something regarding this.

Johnboy200 · Jul 5, 2022

Thanks valinet, your work is much appreciated.
I think I'd have to go back to W10 if EPatcher ever stops working

jab8356 · Jul 5, 2022

Thank you Valinet! From reading some of your recent posts here and on Github, I didn't know if EP would be updated much anymore or not. Very pleased that it has been again! I've even discovered some new things that I wasn't aware of. I hope you can continue this work, even though your life might not give you as much time for it as you had before.

The-Hive · Jul 5, 2022

Brilliant job @valinet . Thanks, After updating EP I went ahead with the KB5014668 upgrade and all is fine

shadowz1337 · Jul 6, 2022

Good to see that EP is updated to support the latest Windows Update. In case anyone needs a backup option, StartIsBack works fine and I've been using that while waiting for EP to be updated. It's a little bit more basic, but it has all the features I need from EP, so I didn't really find anything missing when using StartIsBack. It's not free though (although you could technically get it for "free" if you know what I mean) and the developer has an attitude problem.

valinet · Jul 6, 2022

shadowz1337 said:
Good to see that EP is updated to support the latest Windows Update. In case anyone needs a backup option, StartIsBack works fine and I've been using that while waiting for EP to be updated. It's a little bit more basic, but it has all the features I need from EP, so I didn't really find anything missing when using StartIsBack. It's not free though (although you could technically get it for "free" if you know what I mean) and the developer has an attitude problem.

Why do you say the developer has an attitude problem? Can you share your experience? Thanks.

shadowz1337 · Jul 7, 2022

valinet said:
Why do you say the developer has an attitude problem? Can you share your experience? Thanks.

Well, when I installed StartIsBack, it removed the Windows Action Center buttons and the fly-out menu. Basically this:

And if I uninstall the app, everything goes back to normal. In the app settings, there's nothing remotely related to removing the Action Center buttons. So naturally, I emailed the dev to ask him if there's a bug or if there's a setting that I'm missing. Sometimes, there are hidden settings in .ini config files that aren't available in the GUI. For example, Windows Terminal app have a JSON that you can modify to add hidden attributes/properties to allow multiline pasting.

Anyway, I emailed the dev nicely and even began the email saying that I'm trailing the app and encountered this error. The dev assumed that I screwed up the install or messed up the Action Center setting somehow and tells me to Google on how to restore it. Obviously doesn't care about scaring off potential customers. In the end, I didn't buy his app.

Edwin · Jul 7, 2022

shadowz1337 said:
... there's nothing remotely related to removing the Action Center buttons....

shadowz1337 · Jul 7, 2022

Edwin said:
View attachment 33285

Take a look at it again. It says Notification Area icon, which isn't the same as Action Center buttons. If you actually clicked to verify it, you would see that it's completely different to my screenshot. Also, those are just shortcuts to native Windows settings, they're not unique settings specific to StartIsBack itself. None of my native Windows were changed and like I said, uninstalling StartIsBack fixes the issue, it's only when it's installed that it creates the issue. ExplorerPatcher never had this problem for me.

Anyway, I had already resolved my issue.

Edwin · Jul 7, 2022

shadowz1337 · Jul 7, 2022

Edwin said:
View attachment 33287

Yup, I know....

As I said, that's not a unique setting to StartIsBack. It's literally just a shortcut to a native Windows setting....mine's already enabled and it just wasn't there when StartIsBack is installed. That setting was never modified after installing StartIsBack.