-
-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Theme partially disabled after connecting external display #217
Comments
I have the same problem with this latest version of SecureUxTheme and the latest version of UltraUXThemePatcher even after taking ownership of uxtheme.dll, uxinit.dll, themeui.dll before patching. I too only started noticing this issue in November. Right now I am sticking with UltraUXThemePatcher only because the issue seems to occur less often, granted my testing was limited with SecureUxTheme. Windows 11 version 24H2 (64-bit) |
UpdateI no longer thing it's system startup that's causing the issue, I think it's when I connect to an external display (specifically, connecting to a TV via HDMI). So now I don't even know if the issue is exclusive to Win 11 24H2 or not! Hopefully this will help with further debugging. |
Confirming after further testing that the issue is reproducible when connecting an external display/tv via HDMI. Using ThemeTool to re-apply a theme does not work UNLESS I first lock the computer and log back in. (I have the LogonUI hook installed, so presumably that hook is somehow "resetting" whatever part of the injection got corrupted.) |
When I start up my computer, some colors in my custom theme are incorrect. Once I launch ThemeTool and re-apply my current theme, they get corrected. The correct colors persist even after logoff/login; it seems like it's only an issue on system start.See updated comment below.
Below is all the debugging info I can think of. Let me know if there's anything else I can share. I only started noticing this issue around November/December 2024, so it's possible it's a conflict with a recent cumulative update. If you're going to test it out on a VM, maybe start with update KB5046633 and go forward from there?ThemeTool:
Windows:
The text was updated successfully, but these errors were encountered: