Need my Right Ctrl key back, not Copilot -- PowerToys remap doesn't work

jwhitener

On Nitro V 15, I do not want a Copilot key, I want my right Ctrl key back - same key I've used for decades.

Remapping with PowerToys doesn't work correctly. This drives me nuts many times a day.

Here's why PowerToys doesn't work: On my Acer Nitro laptop, Copilot key comes up as the shortcut / key combination 'Win (Left) + Shift (Left) + F23'

This cannot be remapped to just 'Ctrl' or better yet 'Ctrl (Right)'

Even if I remap both or either the F23 key and the shortcut, it doesn't work right.

Microsoft says when remapping, 'Shortcuts must begin with a modifier key: Ctrl, Shift, Alt, or Win' and that 'Shortcuts must end with an action key (all non-modifier keys): A, B, C, 1, 2, 3, etc.'

So this defeats the attempt to make the unwanted Copilot key just the Ctrl key.

The closest I can get is the key will sometimes function as Shift-Ctrl, but that's not the proper behavior, and it only works at all in some contexts.

It's very inconvenient that I have to relearn typing for some unwanted new key.

Acer: At least enable the restoration of the common, decades-established behavior.

If anyone has a solution, please let me know, but this seems to be a dead end. Sad and annoying.

Puraw

https://community.acer.com/en/discussion/728535/need-my-right-ctrl-key-back-not-copilot-powertoys-remap-doesnt-work

Hi jwhitener,

Unfortunately, it’s unlikely you can fully remap Microsoft‑integrated key functions like the new Copilot key at the firmware level. These functions are hard‑coded into the keyboard matrix and handled by Windows before most remapping tools (including PowerToys) can intercept them.

While I understand the frustration of muscle‑memory changes, AI integration is a core part of Windows’ future direction. Disabling Copilot entirely may limit your ability to benefit from ongoing AI‑driven features and improvements — in effect, isolating yourself from where the platform is headed.

If the Copilot key is disruptive, your best options are:

1. Check your BIOS/UEFI for any “Function Key Behavior” or “Special Key” settings (rare, but worth a look).
2. Use third‑party remapping tools that operate at a lower driver level than PowerToys — though success is not guaranteed.
3. Provide feedback directly to Microsoft via the Feedback Hub so they’re aware of the demand for remapping or disabling this key.