The setting is now documented in Windows 11 Release Preview update KB5124010. But it is important to separate what has been tested from what has been broadly delivered. The option is not a new keyboard customization control for every Windows 11 PC, and Microsoft has not committed to a single day on which every eligible device will receive it.
What KB5124010 brings to Release Preview
Microsoft’s September 2026 Release Preview notes identify KB5124010 across three Windows 11 development baselines:
- Version 24H2: build 26100.9539
- Version 25H2: build 26200.9539
- Version 26H2: build 26300.9539
Among the changes is an option for a dedicated Copilot key to take on one of two conventional keyboard roles:
- Right Ctrl
- Context Menu
The configuration is expected under Settings > Bluetooth & devices > Keyboard.
This matters because, on select devices, the Copilot key has sometimes occupied the physical position previously used for Right Ctrl or the Context Menu key. The new setting is therefore best understood as a way to restore a familiar input function where the hardware design has changed it, rather than as a universal remapping tool for arbitrary keys.
Who should expect to see the setting
Eligibility begins with the keyboard, not simply the Windows version. Microsoft frames this option around Windows 11 devices with a dedicated Copilot key. A desktop connected to an ordinary keyboard without that key should not be expected to gain a new physical key or a broadly applicable remapping control from this update.
Even among Copilot-key devices, behavior may vary. Microsoft notes that implementations depend on the manufacturer, firmware configuration, and hardware design. That qualification is consequential: two machines running the same Windows build could expose different options, or a manufacturer’s keyboard software could affect how the key is handled.
Owners of an eligible laptop or keyboard should first check the Keyboard page in Settings once their device has received the update. If the control is absent, that does not by itself establish that Windows is malfunctioning; the staged rollout and device-specific implementation both matter. It is also sensible not to layer manufacturer-specific Copilot-key controls on top of the Windows setting, as conflicting configurations could make the resulting behavior unclear.
Why Right Ctrl and Context Menu are not interchangeable
The two available roles solve related but distinct problems.
Restoring Right Ctrl
The Right Ctrl key is not merely a duplicate label on all keyboard workflows. Some users deliberately distinguish left and right modifier keys in shortcut systems, specialized applications, remote desktop configurations, or accessibility setups. Returning this function can therefore help users regain a layout they already know.
There is, however, a documented limitation. When the Copilot key is remapped as Right Ctrl, combinations containing Right Ctrl+Windows and Right Ctrl+Shift will not work normally. Microsoft’s practical recommendation is to use the Left Ctrl key for those combinations instead.
That caveat should be weighed before making the switch. For someone who mainly needs a physical Right Ctrl key for a particular workflow, the trade-off may be acceptable. For someone whose shortcuts explicitly depend on the right-side modifier in combination with Windows or Shift, it may not be a complete restoration.
Restoring Context Menu
The Context Menu key offers a keyboard-based way to open the menu normally associated with a right-click. In Windows, the same context-menu action can arise from a mouse right-click, the Shift+F10 shortcut, or the Applications/Context Menu key found on some keyboards.
This makes the remapping useful for users who prefer keyboard navigation, work without a mouse at times, or need a predictable way to open item-specific commands in File Explorer, desktop views, and compatible applications. It can also preserve a familiar function for users whose former Menu-key position is now dedicated to Copilot.
The choice is not about which function is objectively better. It is about which missing key creates the greater practical cost on a given machine. A user who rarely invokes contextual actions may prioritize Right Ctrl; a keyboard-first user who frequently manages files, text, or application commands may find the Context Menu role more valuable.
An accessibility and workflow correction, not proof of a universal problem
Microsoft explicitly recognizes that changes to the Copilot-key position can create workflow challenges for people who rely on Right Ctrl or Context Menu actions for shortcuts or assistive technologies, including screen readers. That acknowledgment is significant because hardware-key changes are not neutral when established input patterns are involved.
Still, the available documentation does not quantify how many people are affected or establish that the new setting resulted from widespread user complaints. It would be an overstatement to characterize the change as proof that every Copilot-key design has failed, or that the key itself has been rejected across the market.
A more grounded interpretation is that Microsoft is adding a fallback for users for whom the original key positions remain important. It is a form of choice that can reduce disruption without requiring manufacturers to redesign keyboards already in circulation.
There is also a reasonable counterargument: software reassignment cannot fully replicate every aspect of a traditional physical layout. Key legends remain different, the key’s location may not match a user’s muscle memory, and firmware or OEM customization can complicate the final experience. The setting addresses the function sent to Windows; it does not make every Copilot-key implementation identical to the keyboard it replaced.
This is different from prior Copilot-key customization
Windows had already tested a separate Copilot-key configuration path in October 2024. In that earlier Insider work, users could choose a signed, MSIX-packaged app to launch from the key through a setting then located under Settings > Personalization > Text input.
That earlier approach and the current Right Ctrl/Context Menu choices address different needs. Launching an app treats the key as an application shortcut. Mapping it to Right Ctrl or Context Menu restores a traditional keyboard input role.
The distinction matters for readers assessing what is genuinely new. KB5124010 is not the first sign that Microsoft considered Copilot-key configuration. It is the documented addition of these two legacy-key roles, which are especially relevant on devices where a conventional key position was repurposed.
Release Preview does not mean simultaneous availability
KB5124010 is in the Release Preview channel, a stage that signals a change is moving closer to broader distribution but does not make it immediately universal. Microsoft describes both gradual and normal rollout phases, with gradual availability occurring over time and varying by device.
An independent report expects the September Release Preview content to become part of the October 13, 2026 Patch Tuesday update. That is a forecast about the likely servicing schedule, not a Microsoft commitment that this particular feature will arrive on every eligible system that day.
The distinction is useful for anyone waiting to change the behavior of their Copilot key. Even if the update becomes available through the normal Windows Update process in October, the feature itself may arrive at a different pace on different hardware. Microsoft’s Copilot-key guidance only says that the relevant Windows 11 update will ship later in 2026.
Users should therefore avoid treating an October date as a deadline or assuming a missing option proves their PC is unsupported. Check the installed Windows version and build, install updates through the usual supported path, then inspect Settings > Bluetooth & devices > Keyboard on a device that actually has a Copilot key.
A reminder to read Windows rollout claims closely
The Copilot-key story also illustrates a broader Windows 11 lesson: a feature announcement, an Insider test, a Release Preview build, and general availability are different milestones.
That distinction is relevant to comparisons with movable taskbar positions. Microsoft announced that taskbar placement at the top, bottom, left, or right was rolling out to Windows Insiders in the Experimental channel in May 2026. It also listed incomplete elements, including alternate-position auto-hide and tablet-optimized taskbar support. That was not the same as a completed, broad Windows 11 restoration.
Likewise, KB5124010 should not be described as a mandatory feature rollout for all supported PCs. The verified position is narrower and more useful: Windows 11 Release Preview now includes a setting intended for dedicated Copilot-key devices, with two familiar fallback functions and specific limits when Right Ctrl is selected.
What eligible Windows 11 users can do now
For a device already running one of the documented Release Preview builds, the practical process is straightforward:
- Confirm that the keyboard includes a dedicated Copilot key.
- Open Settings > Bluetooth & devices > Keyboard.
- Look for the Copilot-key behavior option.
- Choose Right Ctrl if restoring that modifier matters most, while accounting for the Right Ctrl+Windows and Right Ctrl+Shift limitation.
- Choose Context Menu if a keyboard-accessible right-click equivalent is more important.
For everyone else, the most useful action is patience rather than forced troubleshooting. The feature has a defined hardware audience, and its release is staged. If Microsoft’s eventual rollout reaches a particular Copilot-key device, the benefit is clear: the key can be made to serve the workflow that was displaced, instead of being locked permanently to a single dedicated action.