-
Notifications
You must be signed in to change notification settings - Fork 6.5k
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Keyboard Manager always stops working #26457
Comments
By the way, this problem occurs on all my windows devices, so I infer that it is not an individual problem with my certain computer. Hope you guys fix it, love |
What does your bug report say? I can't reproduce it. |
It happens randomly, it only affects the remap shortcut section of the keyboard manager; the single key remaps still operate as per usual. Restarting the app does fix it but then it stops later! |
Combining similar keyboard manager issues |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
yes, me too. it stopped working , i re-locked the laptop(use the shortcut |
Microsoft PowerToys version
0.70.0
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
Keyboard Manager
Steps to reproduce
The Keyboard Manager always stops working, and at the same time the other functions work well. In my case I remapped ctrl + w to alt + f4 in several applications, but it always failed after the machine restarted or hibernated. Restarting both Powertoys and Keyboard manager functions didn't restore it, but I eventually found that by bringing up task manager and then not having to do anything, it worked again. But that's not elegant and good enough to use, is it?
✔️ Expected Behavior
Make it stable.
❌ Actual Behavior
It frequently fails
Other Software
No response
The text was updated successfully, but these errors were encountered: