How to Remap the Copilot Key to Right Ctrl or Context Menu in Windows 11

There are conditions. The rollout is gradual, it depends on your hardware, and one shortcut limitation is worth knowing about before you change it.

What the setting does​

Microsoft's release notes say the update introduces a new Windows 11 setting that lets you remap the Copilot key to function as the Right Ctrl or Context Menu key, helping preserve familiar keyboard shortcuts and accessibility workflows.

You get two choices:

• Right Ctrl. The key becomes a right-hand Control key again, for shortcuts, keyboard navigation and assistive-technology commands that expect it.
• Context Menu. The key opens the context menu for whatever is selected, much like a right-click.

You can only pick one of these two. This isn't a general key remapper. It won't turn the key into F13, a macro or a media control. For anything beyond these two options you still need a manufacturer utility or a tool such as PowerToys.

Remapping the key doesn't remove Copilot either. The assistant is still available through its other entry points. The physical key just stops being one of them.

Section summary: The Copilot key can act as Right Ctrl or Context Menu, and that's all this setting does. Copilot itself stays on the PC.

Release timeline and supported versions​

The feature has come out through several channels over about seven weeks:

For 26H1, Neowin reported that Microsoft released Windows 11 Insider Release Preview build 28000.3351 (KB5127653) for version 26H1 with a fairly large batch of new features. The production preview followed: KB5127653 (OS Builds 28000.3365) Preview applies to Windows 11 version 26H1, all editions. NinjaOne's update catalog lists it as an optional preview cumulative update for Windows 11 version 26H1 (OS Build 28000.3365), released October 28, 2026.

Two practical points come out of that table.

These are optional preview updates. Microsoft's KB5124010 page says you install them from Settings > Windows Update > Advanced options > Optional updates. If you only take Patch Tuesday security updates, the feature comes with a later cumulative update. Pureinfotech lists the next 26H1 release date as November 10, 2026.

Version 24H2 is close to its end. Microsoft's KB5124010 notes call it the final non-security preview update for version 24H2. The same notes say 24H2 Home and Pro editions reached end of updates on October 13, 2026, while Enterprise and Education editions are supported until October 12, 2027. A Home or Pro machine still on 24H2 should move to a newer version, and that matters far more than getting a Ctrl key back.

Section summary: The setting is documented for 24H2, 25H2, 26H2 and 26H1. It ships first as an optional preview, so it won't show up through security-only patching until a later cumulative update.

How to turn it on​

1. Install the update. On 24H2, 25H2 or 26H2 that's KB5124010 or later. On 26H1 it's KB5127653 or later. Go to Settings > Windows Update > Advanced options > Optional updates, or wait for a later monthly cumulative update.
2. Open the keyboard settings. Go to Settings > Bluetooth & devices > Keyboard.
3. Find the Copilot key option on that page.
4. Choose Right Ctrl or Context Menu.
5. Test it. In a document, press the remapped key together with C on selected text to check Ctrl behavior. For Context Menu, select a file in File Explorer and press the key.

If it works, pressing the key doesn't open Copilot and does what the old key did.

If the option isn't there​

• Gradual rollout. Microsoft's KB5124010 notes say a gradual rollout delivers features over time, so availability varies by device. Installing the update doesn't guarantee you'll see the setting right away.
• Your hardware may not support it. Microsoft's support page on Copilot key changes says keyboard layouts and Copilot key implementations vary by manufacturer, firmware configuration and hardware design. Two laptops on the same Windows build can behave differently.
• Not on the minimum build. Check Settings > System > About against the builds in the table above.

Avoid conflicting remaps​

If your PC maker's software can already remap or manage the Copilot key, Microsoft says to use either the Windows setting or the manufacturer's setting, not both. Running two remapping layers at once is an easy way to get odd key behavior. If you set it up in Windows, turn off any remap in the OEM utility.

The Right Ctrl limitation​

Microsoft notes one exception. If you remap the Copilot key to Right Ctrl, shortcuts that combine Right Ctrl with the Windows key or with Shift may not work as usual. Microsoft recommends using Left Ctrl for those combinations.

That covers more shortcuts than it might seem to. Ctrl+Shift is common across browsers, Office apps and IDEs, and in some apps it's used for input switching. If you press those with your right hand, you'll need to retrain. If you use screen-reader commands built on Right Ctrl, test them yourself before you trust them. Microsoft's own wording is that the feature is meant to help preserve accessibility workflows. It doesn't publish a compatibility list for specific screen readers or apps.

Section summary: Most Right Ctrl use comes back. Right Ctrl+Win and Right Ctrl+Shift combinations may not, so use Left Ctrl for those.

What IT administrators should do​

For admins running fleets with several laptop models, the hardware variability creates extra work. Based on Microsoft's documented caveats, this is a sensible order:

• Check by model. Before publishing instructions for the whole fleet, confirm which models actually show the setting. Record the device model, build and keyboard configuration for each.
• Check for OEM tools. Where a manufacturer utility already remaps the key, decide on one method per model and write it down.
• Test accessibility first. Prioritize staff who use screen readers or navigate by keyboard only, and test the actual commands they use.
• Update training material. If your shortcut guides tell people to press Right Ctrl with Shift, change them to Left Ctrl.
• Watch the rest of the preview update. KB5124010 also lists a known issue: non-admin users may be unable to make Remote Desktop connections to hosts with Administrator protection enabled, with error 0xC000000D. Microsoft says this is fixed for 25H2 and 26H2 by KB5127936 and later. On 24H2 the workaround is a policy change.

Analysis: Microsoft fixes a problem it created​

It's fair to point out that this problem began when Microsoft introduced the Copilot key in 2024. Microsoft's own support documentation acknowledges that people who relied on Right Ctrl or Context Menu, including screen-reader users, had their workflows disrupted.

It has taken roughly two years to get a built-in fix. Until now, people used PowerToys, registry tweaks or whatever OEM utility came with their laptop. A first-party setting is better than any of those because it's documented and supported, and it isn't tied to one manufacturer's software.

Still, a fix that depends on hardware isn't a universal fix. Some owners of Copilot-key laptops won't see the option at all, and Microsoft's documentation doesn't say which models are affected. Those users are back to OEM tools or third-party remappers. The Right Ctrl caveat also means the restored key doesn't fully behave like the original.

The change also fits a pattern of Microsoft giving users a bit more control over where Copilot appears. For anyone who pressed that key by accident more often than on purpose, being able to repurpose it is a welcome change, as long as your keyboard supports it.

If something goes wrong​

Microsoft asks users to send feedback through Feedback Hub (Windows key + F). Users with disabilities can contact Microsoft's Disability Answer Desk. For model-specific behavior, Microsoft points to Windows 11 release information and your PC maker's support documentation.

Bottom line: If you're on 24H2, 25H2, 26H2 or 26H1, install the latest preview or wait for the next monthly update, then look under Settings > Bluetooth & devices > Keyboard. If the option is there, pick Right Ctrl or Context Menu and use Left Ctrl for Ctrl+Shift and Ctrl+Win shortcuts. If it isn't there, you may need to wait for the gradual rollout, or your keyboard may not support the setting.