Orphaning a key under "Remap a key" also orphans all modifier+key possibilities under "Remap a shortcut"

[Watt56]

Microsoft PowerToys version

0.64.1

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

Keyboard Manager

Steps to reproduce

In Remap a Key, set Caps Lock (for example) to "Disable". (The problem occurs with any key I tested, not just Caps Lock.)

In Remap a Shortcut, set Ctrl-Caps Lock (or Win-Caps Lock, or Alt-Caps Lock, etc.) as the Physical Shortcut and the desired operation as the Mapped To key combination.

✔️ Expected Behavior

That the Mapped To action would work using the new Physical Shortcut, Ctrl-Caps Lock.

❌ Actual Behavior

The Physical Shortcut Ctrl-Caps Lock (etc.) does not implement the desired Mapped To action; it does nothing.

Essentially, orphaning a single key under Remap a Key orphans the key not only when the key is used alone, but also when the key is used with a modifier.

This may be an unavoidable result of how Windows works, but it reduces keyboard versatility.

Other Software

No response

[Jay-o-Way]

This is by design. See, when you remap one key, that remapping will be maintained even when "inside bigger shortcuts". It's the key that changes. You might want to look at "Remap a shortcut" if you have specific ones, or try (something like) AutoHotkey or MS Keyboard and Mouse Center. Following your example: you send Ctrl+{nothing}

[crutkas]

This is by design. Key remappings take priority.

We do try and directly call this out in the UX as well for shortcuts.