namazso
Remove "hook explorer"
Since Win 11, Windows doesnt have classic Control Panel, and a corresponding warning is coming, when enabling the option. Can it then be removed, if should not be used anyway?
What version was it removed in? Some Insider? I'm on 24H2 and it's still available:
Just navigate to shell:::{ED834ED6-4B5A-4bfe-8F11-A626DCB6A921} and it should work for you as well.
Sorry, my bad, its still present in the lastest official Win 11, i must oversee it. But why do the message comes, that its pointless to patch explorer? I looked README and help page but was unable to find answer for it.
Because ThemeTool allows you to set themes nowadays. It didn’t use to be a thing. It’s still useful for a developer - debugging feature.
Because ThemeTool allows you to set themes nowadays. It didn’t use to be a thing. It’s still useful for a developer - debugging feature.
True, except open/save dialogs don't work properly in some programs (e.g. NTlite) when an unsigned theme is loaded via ThemeTool. Seems to have something to do with the way common dialogs are invoked by some programs.
One has to revert to the default "Windows (light)" theme for them to work.
Yet it works fine in others (e.g. ExplorerPatcher's settings window, Notepad++).
I no longer use Start11 as Open Shell now works properly.
Because ThemeTool allows you to set themes nowadays. It didn’t use to be a thing. It’s still useful for a developer - debugging feature.
True, except open/save dialogs don't work properly in some programs (e.g. NTlite) when an unsigned theme is loaded via ThemeTool. Seems to have something to do with the way common dialogs are invoked by some programs.
One has to revert to the default "Windows (light)" theme for them to work.
Yet it works fine in others (e.g. ExplorerPatcher's settings window, Notepad++).
I no longer use Start11 as Open Shell now works properly.
Are these apps 32-bit or 64-bit?
Both. Turns out the theme that I'm using (aero7-11) was buggy. Updating to the latest version fixed the problem.
Also, I've noticed that using SecureUxTheme to apply unsigned is more stable, responsive, and less buggy than using Windhawk's "UXTheme hook" mod. Why is that Winhawk injecting into logonui and winlogon is worse from a performance and stability perspective than using SecureUxTheme?