-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
ADM no longer works on Windows 10 LTSC after updating to new version #508
Comments
Unfortunately I don't have LTSC 1809 to test, but with the development of Windows 11 I am not sure if we can still support LTS operating systems. There is a way to fix this but it's not an easy/quick one. I will update here once we have windows-version specific switching behavior figured out. Sorry for the inconvenience, development for Win11 22H2 has been pretty difficult and currently there are some trade-offs. |
Should be fixed in the latest beta (10.3.0.1) |
I tried now. No change unfortunately. |
Hmm the logic in 10.3.0.1 for your windows build is the same as in 10.1.0 tho. Please upload logs once again so I can take a look. |
"AppsUseLightTheme" works. "SystemUseLightTheme" not works. |
Could you check whether ADM updates the AppsUseLightTheme entry by forcing theme to dark, then pressing F5 in the regedit window to refresh? |
I've tried. There is no changes in the regedit. |
Hm there have been zero code path changes and the logs you uploaded show the correct code path (AppsSwitch) getting called, which hasn't been modified in 13 months.
Never mind I think I found something. Please update once again to 1.3.0.2 |
OK. No problem now. Working properly. |
awesome! |
Description
After updating from stable version 10.1.0.10 to 10.2.0.18 it no longer switches between modes. "Force Dark Theme" and "Force Light Theme" don't work either.
Expected Behavior
No response
Log Data
service.log
config.yaml.txt
Operating System
Windows 10 Enterprise LTSC 1809 17763.3406
Commit Hash and Version
f7a700b
10.2.0.18
2.4.2
10.0.1.0
1.3.1.0
6.0.7
Screenshots
No response
The text was updated successfully, but these errors were encountered: