How to Remap the Copilot Key in Windows: PowerToys vs AutoHotkey

If you only want the key to open something else, PowerToys is enough. If you need it to act like Right Ctrl, skip straight to AutoHotkey. That's the whole decision, and getting it wrong means spending an hour on a remap that half-works.

This guide covers both methods for how to remap the Copilot key in Windows, explains why the obvious approach usually misfires, and tells you which one to use before you start.

Which method you need: read this first

• Want to launch a different app, open File Explorer, or silence the key? PowerToys handles this well. Start with Method 1.
• Need the key to function as Right Ctrl in keyboard shortcuts, terminal commands, or games? PowerToys won't fully solve this. Skip to Method 2.

The distinction matters because the key itself isn't straightforward. Many 2024-and-later laptops replaced the Right Ctrl key with a Copilot key, a change the copilot-key-fix repository reports across ASUS, Lenovo, HP, Dell, Acer, Samsung, and Surface models. Pressing it launches Microsoft Copilot instead of acting as a modifier, which makes it a poor substitute for Right Ctrl in any shortcut-heavy workflow (estereotipau/copilot-key-fix). For touch typists and developers, that's not a cosmetic change. It's a missing modifier.

Prerequisites: Administrator access on your PC. If you're on a corporate or managed machine, check with IT before installing PowerToys or AutoHotkey, as either may be restricted.

Quick comparison:

Why most Copilot key remaps don't work

Skip this if you just want the steps. But if you've already tried remapping the key and gotten strange results, this is why.

The Copilot key doesn't send one keycode. It fires three separate key events in rapid succession, about 1ms apart: Left Windows key down, Left Shift down, then F23 down (estereotipau/copilot-key-fix). Microsoft's support documentation confirms Copilot uses the Win + Shift + F23 combination (Microsoft Learn Answers).

Most remapping guides target only F23, the third event. Remapping F23 alone is like locking the back door while leaving the front wide open: by the time F23 arrives, LWin and LShift have already passed through to the OS (estereotipau/copilot-key-fix). The Start menu may flicker, Shift modifies the next keypress, and your intended remap fires on top of both those side effects. Users in the PowerToys GitHub tracker specifically documented that using Keyboard Manager to remap the Copilot key to Right Ctrl "does not seem to work reliably" for exactly this reason (microsoft/PowerToys issue #47062).

On some systems, PowerToys captures the key as a distinct unit, which is why it works adequately for app-launch remaps. It doesn't suppress the underlying LWin and LShift events, which is why it fails as a modifier replacement. AutoHotkey intercepts all three events before they reach the OS, which is what makes it reliable for Right Ctrl use.

If your laptop doesn't send LWin + LShift + F23: The three-event sequence is widely reported across major brands, but hardware behavior isn't uniform across every model. The copilot-key-fix repository includes a PowerShell diagnostic script (detectar_tecla.ps1) that logs the exact key events your Copilot key sends. Run that before assuming the standard script applies to your hardware.

Method 1: remap the Copilot key with PowerToys Keyboard Manager

Best for: Launching a specific app, triggering a shortcut, or disabling the key. Not reliable for replacing Right Ctrl as a modifier.

PowerToys is Microsoft's own utility for remapping keys and shortcuts in Windows (Coding Lap). Download it from the Microsoft PowerToys page if you don't have it installed.

Steps:

1. Open PowerToys and select Keyboard Manager from the left sidebar. Enable the Enable Keyboard Manager toggle if it's off (Microsoft Learn Answers).

2. Click Remap a shortcut, not "Remap a key." The Copilot key sends a sequence, not a single keycode, so the shortcut remapper is the correct panel. This is the specific distinction that Microsoft Learn Answers calls out.

3. Click Add shortcut remapping. In the Physical shortcut field, click the pencil icon and press the Copilot key. On some systems, PowerToys will detect it directly, displaying it as VK_C7 or CopilotKey (Coding Lap). If capture fails, manually enter Win + Shift + F23 using the modifier dropdowns and the F23 key selector (Microsoft Learn Answers).

4. In the Mapped to field, set your target. Common choices:

• Win + E to open File Explorer (Coding Lap)
• An app launch action, if available on your version of PowerToys
• Nothing (no output assigned) to effectively disable the key (Coding Lap)
• Avoid mapping to Right Ctrl here; see the previous section for why this produces unreliable results

5. Click OK. The remap takes effect immediately.

6. Test it. Press the Copilot key. If Copilot still launches, or if you see unexpected Start menu or Shift behavior, PowerToys isn't fully intercepting the three-event sequence on your hardware. Move to Method 2.

Gotcha: If the remap has no effect, run PowerToys as administrator. Without elevated privileges, Keyboard Manager can miss certain system-level key events (Microsoft Learn Answers).

No physical Copilot key? If your keyboard lacks the dedicated key but you want to stop accidentally triggering Copilot via Win + C, use the Remap a Shortcut panel to reassign that combination. Win + C to open Notepad or Calculator are straightforward examples (Coding Lap). The same steps above apply; just enter Win + C as the physical shortcut.

Method 2: restore Right Ctrl (or any key) with AutoHotkey

Best for: Making the Copilot key behave as a genuine modifier Right Ctrl, or anything else in shortcuts, games, and terminal workflows. Also works for app-launch and disable use cases if you'd rather use one tool for everything.

An AutoHotkey v2 script in the copilot-key-fix repository uses a three-stage interception approach. When LWin fires, the script holds it at the keyboard hook level rather than passing it to the OS, and enters a waiting state. If LShift arrives immediately after, it gets suppressed too. Then the script waits up to 30ms for F23 (estereotipau/copilot-key-fix). If F23 arrives within that window, the script confirms this was a Copilot key press, discards all three events, and sends Right Ctrl instead. If F23 doesn't arrive within 30ms, the original keypresses pass through to the OS unchanged (estereotipau/copilot-key-fix).

The result: the Copilot key becomes Right Ctrl, with none of the Start-menu flicker or stray-Shift problems that plague F23-only remaps. Normal Win key presses pass through with a delay of about 30ms, which the repository describes as imperceptible (estereotipau/copilot-key-fix).

Prerequisites: AutoHotkey v2 (v2.0 or newer). The script uses v2 syntax and will not run on AHK v1.x. Windows 10 or 11 required (estereotipau/copilot-key-fix).

Steps:

1. Download and install AutoHotkey v2 from autohotkey.com. Accept the defaults during setup.

2. Download copilot_a_ctrl.ahk from the copilot-key-fix repository. Save it somewhere permanent; your Documents folder works fine.

3. Double-click the .ahk file to run it. An AutoHotkey icon appears in the system tray. The script is now active.

4. Test it. Press the Copilot key, then try Copilot key + C. That combination should copy selected text (estereotipau/copilot-key-fix). If Copilot opens instead, the script isn't intercepting your key's specific event sequence. Run the detectar_tecla.ps1 diagnostic from the same repository to confirm what your hardware actually sends.

5. To remap to something other than Right Ctrl: Open the .ahk file in any text editor. Find Send "{RCtrl}" and replace {RCtrl} with your preferred key or action. The script accepts any standard AutoHotkey key name (estereotipau/copilot-key-fix).

6. To disable the Copilot key entirely: Change the Send "{RCtrl}" line to return. The script will intercept all three Copilot key events and send nothing in response (estereotipau/copilot-key-fix).

7. To run at startup: Press Win + R, type shell:startup, press Enter. Copy a shortcut to the .ahk file into the folder that opens. The script will start automatically with Windows.

Gotcha, Win + Shift timing: Because the script holds LWin for up to 30ms, pressing Win and Shift together as a deliberate shortcut within that window may cause a brief delay before Shift registers (estereotipau/copilot-key-fix). Most users won't notice this. If you rely on Win + Shift shortcuts frequently, it's worth knowing before you commit.

Gotcha, one instance only: The script enforces single-instance mode. Running the file a second time replaces the existing instance rather than stacking two copies (estereotipau/copilot-key-fix).

Which to use, and what to check after updates

Use PowerToys if your goal is reassigning the key to an app or shortcut, or if you're on a managed machine where background scripts require IT approval. Use the Remap a Shortcut panel with Win + Shift + F23 as the input, not the single-key remapper. PowerToys is Microsoft's own utility for this kind of remapping (Coding Lap), and for simpler jobs it does the work without any additional tooling.

Use the AutoHotkey script if PowerToys produces unreliable results, or if Right Ctrl modifier behavior is what you're after. It's the only approach in the cited research that explicitly intercepts all three Copilot key events rather than catching just F23 (estereotipau/copilot-key-fix).

Two things worth keeping in mind. Re-test your remap after any major Windows feature update, since neither method has been confirmed to survive them unchanged. And a feature request in the PowerToys GitHub tracker proposes registering PowerToys as a native Copilot key provider, which would let the key trigger features like the Command Palette directly without third-party scripting (microsoft/PowerToys issue #47062). That feature doesn't exist yet, but if it ships, it will likely be the cleanest path forward for PowerToys users.