Keyboard manager constantly need resetting to function normally

[AbyssinianSTAN]

Microsoft PowerToys version

0.79.0

Installation method

GitHub

Running as admin

Yes

Area(s) with issue?

Keyboard Manager

Steps to reproduce

✔️ Expected Behavior

I mapped "alt (left)" to "ctrl (left)", "ctrl (left)" to "alt (left)", "alt (left) + tab" to "ctrl (left) + tab", "ctrl (left) + tab" to "alt (left) + tab". My goal is to create a mac-like experience, with "alt (left)" being the "command" key on macOS. This setting can work, but not for long before the keyboard mapping gets messed up, meaning one key leads to some random function.

❌ Actual Behavior

This setting can work, but not for long before the keyboard mapping gets messed up, meaning one key leads to some random function. Whenever that happens, I hit "ctrl + alt + delete" and it resets.

Other Software

The same situation has happened many times on many different computers of mine. I don't think it is triggered by other software.

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Remapping shortcuts to include a remapped key works inconsistently (#23231), similarity score: 0.82
• Alt+Tab Remapped to Ctrl+Tab occasionally lose functions. [Keyboard Manager] (#29265), similarity score: 0.82
• The remapping of shortcuts stops functioning (#18342), similarity score: 0.82

Closed similar issues:

• Keyboard management tool shortcut mapping fails after being used for a period of time (#27461), similarity score: 0.85
• Keyboard Manager always stops working (#26457), similarity score: 0.82

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[crutkas]

/dup #17344

[microsoft-github-policy-service]

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!