Skip to content
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: Remapped Shortcut Stops Working After a While #35730

Closed
sudosys opened this issue Nov 3, 2024 · 7 comments
Closed

Keyboard Manager: Remapped Shortcut Stops Working After a While #35730

sudosys opened this issue Nov 3, 2024 · 7 comments
Labels
Issue-Bug Something isn't working Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@sudosys
Copy link

sudosys commented Nov 3, 2024

Microsoft PowerToys version

0.85.1

Installation method

PowerToys auto-update, GitHub

Running as admin

Yes

Area(s) with issue?

Keyboard Manager

Steps to reproduce

  1. Open PowerToys Settings
  2. Go to "Keyboard Manager"
  3. Enable "Keyboard Manager"
  4. Remap a key (e.g. "Ctrl + Q" to "Alt + F4")
  5. Close PowerToys Settings
  6. Use remapped shortcut combination for a while

✔️ Expected Behavior

Remapped shortcuts should behave as expected all the time.

❌ Actual Behavior

I observed that after a bit of time, the remapped key combo stops working as if I did not remap it at all. I had to go to the Keyboard Manager and re-enable it for it to work but unfortunately it stops working again after a while. Also re-opening the PowerToys fixes the issue temporarily.

This bug is reproduced both on Windows 10 (22H2 Build 19045.4780) and Windows 11 (24H2 Build 26100.2161).

Other Software

No response

@sudosys sudosys added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Nov 3, 2024
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@borsodigerii
Copy link

Still a problem, mine stops working as well after a while, not sure what is causing it..

@creative-resort
Copy link

Affirmative,
same problem. Keyboard Manager has become dysfunctional with this.

It takes entering just one combination of keystrokes for me
– in any app, be it notepad or a browser –
and all of them stop working.

@iHeadway
Copy link

iHeadway commented Nov 5, 2024

Same, but it's not only KbM, FancyZones also affected, that means that any "toy" can be.

@borsodigerii
Copy link

borsodigerii commented Nov 7, 2024

I might have a lead on this: for me, this particularly occurs, when I use a modifier key on a shortcut, but not "unpress" the modifier, and execute another shortcut.

Example:

I have the following shortcuts:

  • alt + right => ctrl + right
  • alt + A => ctrl + A
    When I press alt + right, then unpress right, but then press A (so that Alt stays pressed), the Shortcuts stop working. It does occur randomly on other situations, but the main scenario for me was like this
    (Please note, that alt can be alt (Left), or any variation, the issue still persists)

EDIT

I see, that a tracker is on the issue: #17344

@ethanfangg
Copy link
Contributor

/dup #23231

Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug Something isn't working Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

5 participants