-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
PowerToys Run & Keyboard Manager Off on Windows 10 2004 (10.0.19041.264) #3925
Comments
@asecor were you already on Windows 10 2004 when you installed PowerToys or did you update Windows after PowerToys was installed? Which version of Windows were you on before the update? |
I tried reproducing this error on a 2004 VM and on a 1809 VM with PowerToys 0.18.2 which was then updated to 2004 but I could not reproduce the error. @asecor are you still facing this issue? If not can you let us know the information mentioned above? Maybe the update had not completed and a reboot could fix it, but I'm not sure. |
@DavidGretzschel yes the UI screenshot you sent in the second post is what is supposed to be displayed on Windows 1903 or higher, whereas if it's older than that it should show the old UI (the first screenshot), because PowerToys Run and Keyboard Manager use UI platforms that are only supported on 1903 or higher.. |
There was definitely a reboot between those. That doesn't mean that it wasn't down to closing and reopening, I haven't checked that. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment. |
Environment
Steps to reproduce
Upgraded to Windows 10 Pro 2004 [Version 10.0.19041.264]
Expected behavior
The PowerToys Run & Keyboard Manager modules should be enabled or have the possibility to enable them.
Actual behavior
PowerToys Run & Keyboard Manager modules off with the setting greyed out.
Screenshots
The text was updated successfully, but these errors were encountered: