Keyboard Manger key remap doesn't correctly apply to the Windows + V clipboard shortcut.

[FatCat1978]

Microsoft PowerToys version

0.64.1

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

Keyboard Manager

Steps to reproduce

I have Left Control and Caps lock rebound using the Keyboard Manager Remap setting. this works as intended when opening the windows + V clipboard menu with zero issues. when selecting an object to paste, whether via enter or clicking via the mouse, it doesn't paste - instead opting to: toggle capslock, and simply put the character V. Running as administrator makes no difference.

This to me suggests that windows isn't respecting the keyboard manager remapping, but I'm not familiar enough with either the program or it's codebase to make a more estimated guess than that.

for Context, I have a Unicomp terminal keyboard, which doesn't abide by typical keycode layouts, hence me swapping ctrl and capslock.

✔️ Expected Behavior

Using the windows + v clipboard menu should abide by the remapped keys.

❌ Actual Behavior

it ignores it, resulting in an odd combo if your keyboard uses non standard key mapping.

Other Software

No response

[Hxs123]

Also seeing this issue. Have to delete the V and toggle Caps Lock each time before pasting from the clipboard

[embender]

/needs-info can you give steps to reproduce this issue? ex:

step one: I want to bind action to this key
step: two: I remapped this key to this key
step three: I then hit these keys
step four: These are the results

etc.

[crutkas]

/needsinfo

[crutkas]

/needinfo

[FatCat1978]

@crutkas here's the information you requested. hopefully this is sufficient

Step one. Rebind Caps-lock to control, and control to Caps-lock via the keyboard manager.

Step two. attempt to copy paste something via control-C, and paste via the windows shortcut win+V.

The result will be the (presumably original) capslock key being "pressed", resulting in caps-lock toggling on/off from it's previous state, and V being pressed, usually resulting in a Capital V.

Configuration used:

This still happens as of Version 0.72.0

[LmioF]

I've been troubled by this issue for a long time. I decided to give up using PowerToys for remapping Caps Lock and Ctrl and opted to directly modify the registry to avoid the problem. You can refer to the following link for guidance: https://gist.github.com/joshschmelzle/5e88dabc71014d7427ff01bca3fed33d.

[LifeJustDLC]

Temporary solution: Use SharpKeys instead.