You set the Copilot key to open your favourite app, and it either ignores the change entirely or reverts after a restart. Remapping should be simple — it is a supported feature — but when it does not stick, the cause is almost always a competing layer that reasserts its own assignment. The trick is to find that layer and make your choice the one that wins.

Remap failures come in two flavours: the change never takes effect, or it works briefly and then reverts. Never taking effect usually means the setting is being overridden in real time. Reverting after restart usually means a startup service re-applies its own mapping at boot. Both are fixable once you identify the competing owner.

Fan and thermal behaviour can also hint at competing manufacturer software, since the same utilities that manage keys often manage cooling. If your machine is loud, see our guide to AI PC fan noise fixes , and Surface users should check Surface Laptop 13 AI issues . If Copilot’s widgets are also misbehaving, our guide to Copilot widgets not working covers the related settings layer.

Why this happens

  • Manufacturer utility override: A maker utility reapplies its own key assignment, overriding Windows.
  • Conflicting remapping tools: Two tools remapping the same key fight, and the last one loaded wins unpredictably.
  • Setting needs a restart: Some key assignments only apply after sign-out or restart, looking like failure before that point.
  • Target app not recognised: If the chosen app is not installed, is a web app, or is not a valid target, Windows silently falls back to Copilot.
  • Startup service reapplying defaults: A service at boot resets the key before you even press it.
  • Windows update reset: Updates can restore default key assignments, wiping custom remaps.
  • Insufficient permissions: Changing key assignments from a restricted account can appear to succeed without actually saving.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Apply the remap the Windows way and restart

Use the built-in setting alone, with no third-party tools running, and restart afterwards. This establishes whether the basic mechanism works before you blame competing software.

  1. Close all keyboard remapping tools.
  2. Open Settings and find the Copilot key assignment.
  3. Set it to your chosen app.
  4. Sign out and back in, or restart the PC.
  5. Press the Copilot key and confirm the chosen app opens.
  6. If it works, the mechanism is fine — a competing tool is the likely culprit when it later breaks.

Fix 2: Remove competing remapping tools

Running two remapping methods at once guarantees conflict. Pick one — built-in or a single tool — and remove or disable the others entirely, not just their Copilot key entries.

  1. List every keyboard tool installed: PowerToys, manufacturer utilities, and others.
  2. Choose one method to keep.
  3. Disable or uninstall the others.
  4. Clear their Copilot key entries before uninstalling if possible.
  5. Restart your PC.
  6. Reapply your remap in the remaining method and test.

Fix 3: Stop manufacturer services from overriding at boot

Manufacturer utilities often run a background service that restores key assignments at startup. Disabling that service’s key management — or the service itself, if you do not need it — stops the revert cycle.

  1. Open your manufacturer’s utility and find its key management settings.
  2. Disable Copilot key management there.
  3. Open Task Manager, go to Startup, and note related entries.
  4. Disable the manufacturer’s key service from starting if the utility allows it.
  5. Restart and test whether your remap survives.
  6. Re-enable other manufacturer features you use, keeping key management off.

Fix 4: Verify the target app is a valid target

A remap to an app Windows does not recognise as a launchable target silently fails. Confirm the app is a proper installed desktop or Store app, and test with a different target to isolate the problem.

  1. Confirm the target app is installed and launches normally from Start.
  2. Try remapping the key to a different, simple app such as Calculator.
  3. If Calculator works but your app does not, the app is the problem.
  4. Try the app’s desktop edition instead of its Store edition, or vice versa.
  5. Reinstall the app if its registration seems broken.
  6. Reapply the remap once the app is recognised.

Fix 5: Apply the remap from an administrator account

Permission problems can make a remap look saved while it never writes to the system setting. Applying it from an administrator account rules this out cleanly.

  1. Confirm your account has administrator rights.
  2. If not, switch to an administrator account temporarily.
  3. Apply the Copilot key remap there.
  4. Restart and test in both accounts if needed.
  5. If it works as administrator but not as a standard user, the issue is permissions.
  6. Adjust account permissions or keep the remap managed by the administrator account.

If your remap worked for weeks and then vanished, an update likely reset it. Reapplying after the update — and checking again after the next one — confirms the pattern and tells you to expect it.

  1. Check Windows Update history for a recent update matching the revert date.
  2. Reapply your remap.
  3. Restart and confirm it holds.
  4. After the next update, check the key assignment again.
  5. If updates keep resetting it, use a manufacturer tool or script that reapplies your choice at login.
  6. Report the pattern to the manufacturer’s support if it is their utility resetting it.

Fix 7: Reset all key settings and start clean

When layers are too tangled to untangle, a clean reset gives you a known starting point. Remove all tools, reset Windows key settings, then apply exactly one remap method and verify it before adding anything back.

  1. Note your desired remap and any other shortcuts you need.
  2. Uninstall or disable all keyboard remapping tools.
  3. Reset Copilot key and keyboard settings to defaults in Windows.
  4. Restart your PC.
  5. Apply your remap using the built-in setting only.
  6. Test across several restarts before reinstalling other keyboard tools.
  7. For persistent issues, see the official Windows support pages .

Closing

A Copilot key remap that will not stick is almost always a competing owner — a manufacturer utility, a second remapping tool, or a startup service — rather than a broken key. Use one remapping method, disable the others’ key management, and verify across restarts. Once a single owner controls the key, your remap stays put, and the key opens exactly what you chose.

Frequently asked questions

Why won't my Copilot key remap work?
Remaps can fail when a manufacturer utility overrides Windows, when a remapping tool conflicts with another, when the setting needs a restart, or when the target app is not installed or not recognised as a valid target.
What apps can the Copilot key open?
Windows allows Copilot or a supported app of your choice, depending on your version. Manufacturer tools may allow more options, but the key cannot launch arbitrary scripts or system commands through the standard setting.
Do I need third-party software to remap the key?
Not for the built-in choice between Copilot and a custom app. Third-party tools like PowerToys add flexibility, but they also add a layer that can conflict with the built-in setting, so use one method at a time.
Why does my remap revert after a restart?
A startup utility, manufacturer service, or group policy may be reapplying its own assignment at boot. Finding and disabling that override is the key to making your remap stick.