You press and hold the Copilot key expecting voice input or a quick Copilot action, and nothing happens — yet a quick tap opens Copilot just fine. The key itself is not broken.

If any link in that chain is outdated, remapped, or disabled, the long press silently does nothing while the short press keeps working.

This guide walks you through six fixes in order, starting with the app and software layer and moving down to firmware. Work through them in sequence and test the long press after each step.

Why this happens

  • Outdated Copilot app or missing background service: The long-press action is handled by the Copilot app’s background components. If the app is outdated, disabled at startup, or missing its voice service, Windows has nowhere to send the long-press event.
  • Keyboard driver or firmware mismatch: The keyboard firmware reports the hold duration, and the driver translates it. A generic or stale driver may report the key as a simple tap no matter how long you hold it.
  • Key remapping software intercepting the event: PowerToys, AutoHotkey, or a gaming keyboard utility can swallow the Copilot key event before Windows processes the hold, killing the long press while leaving the tap intact.
  • Windows update changed Copilot key behavior: Microsoft has adjusted what the Copilot key does across Windows 11 builds. An update can reassign the long-press action or require a newer Copilot app version to support it.
  • Copilot voice features disabled or unavailable: On some configurations the long press is tied to voice input. If microphone access is blocked, the voice service is off, or your region build lacks the feature, the long press appears dead.
  • BIOS or embedded-controller change after an update: A BIOS update can alter how special keys are reported to Windows. This is the same firmware layer that affects other Copilot key problems , and it is easy to overlook when the tap still works.

How to fix it

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

Fix 1: Update the Copilot app and check its startup state

The long-press event needs a live Copilot app to receive it. Start by making sure the app is current and actually running in the background.

  1. Open the Microsoft Store, go to Library, and install any pending update for the Copilot app.
  2. Open Settings > Apps > Startup and make sure Copilot is allowed to run at startup if it appears there.
  3. Launch Copilot once by tapping the key, then sign in if prompted — an unsigned-in app may ignore long-press events.
  4. Press and hold the Copilot key for two full seconds and watch whether the voice or action overlay appears.
  5. If it still fails, restart the laptop once so the updated app registers its background handlers cleanly.

Fix 2: Disable key remapping and keyboard utilities temporarily

Remapping tools are a leading cause of lost long-press events because they sit between the keyboard and Windows. A quick test rules them out in minutes.

  1. Close PowerToys, AutoHotkey, SharpKeys, or any gaming keyboard software running in the system tray.
  2. If you use a keyboard utility from your laptop maker, disable its key-customization profile temporarily.
  3. Open Task Manager and end any remaining remapping processes that relaunched themselves.
  4. Test the long press again with a clean hold of about two seconds.
  5. If it works now, re-enable your tools one at a time to find the culprit, then exclude the Copilot key from that tool’s mappings. Similar interception problems affect external keyboards with a Copilot key , so the same isolation test applies there.

Fix 3: Reinstall the keyboard driver

A stale or generic keyboard driver can flatten every key event into a simple tap. Reinstalling the proper driver restores the hold timing information Windows needs.

  1. Open Device Manager > Keyboards, right-click your internal keyboard, and choose Uninstall device.
  2. Restart the laptop — Windows will reinstall the keyboard driver automatically on boot.
  3. If Windows installs a generic driver, download the keyboard or hotkey driver for your exact model from Dell , HP , or Lenovo support.
  4. Install the maker driver, restart again, and test the long press.
  5. Check Microsoft’s Windows support pages if Windows Update keeps replacing the maker driver with a generic one.

Fix 4: Check microphone access and Copilot voice settings

When the long press is bound to voice input, blocked microphone access makes it look dead even though the key event arrives fine. This step separates a key problem from a voice problem.

  1. Open Settings > Privacy & security > Microphone and confirm microphone access is on for the device and for Copilot.
  2. Open the Copilot app settings and look for voice or push-to-talk options — enable voice input if it is toggled off.
  3. Test the microphone in Settings > System > Sound to confirm Windows hears input at all.
  4. Press and hold the Copilot key again and speak a short command to see whether the voice overlay now appears.
  5. If voice works through the app but not the key, the issue is key handling, not audio — move on to the next fix.

Fix 5: Run Windows Update and repair Copilot system components

Microsoft changes Copilot key behavior between builds, and a half-updated system can leave the long-press handler mismatched with the app. Bringing the whole system to the same build fixes that mismatch.

  1. Open Settings > Windows Update and install all pending updates, including optional driver updates.
  2. After updating, open the Store again and update Copilot once more — app and system versions must match.
  3. Run Settings > System > Troubleshoot > Other troubleshooters and run the keyboard troubleshooter if offered.
  4. Restart, then test a two-second hold and a three-second hold separately — some builds changed the required hold duration.
  5. If the long press now triggers a different action than you expected, check the Copilot app settings for the current long-press assignment, since Microsoft occasionally redefines it.

Fix 6: Update the BIOS and embedded controller firmware

If software fixes fail, the keyboard firmware itself may not be reporting holds correctly. This is the deepest layer and the last resort before suspecting hardware, and the same firmware layer can affect high-speed ports, as with Thunderbolt 5 ports not working on Lunar Lake laptops .

  1. Find your exact model in Settings > System > About, then check your maker’s support page for a BIOS update newer than your installed version.
  2. Install the BIOS update on AC power with the battery charged, following the maker’s instructions exactly.
  3. After the update, enter the BIOS setup once and load default settings, then save and exit.
  4. Back in Windows, test the long press — firmware updates often restore special-key reporting immediately.
  5. If it still fails after a BIOS update and a driver reinstall, test with an external USB keyboard that has a Copilot key; if that works, the internal keyboard hardware or its ribbon connection is the likely fault, and a repair ticket is the next step. For related key behavior, see how Copilot keyboard shortcuts can stop responding on the same machines.

Closing

A Copilot key that taps fine but ignores a long press is almost always a software chain problem — the app, a remapping tool, the driver, or the firmware is dropping the hold event. Update Copilot first, clear out remapping tools second, and work down to the BIOS only if the software layer checks out. In most cases the long press comes back long before you reach the firmware step. If this fix did not fully resolve the issue, related troubleshooting for Overwatch 2 Arm Laptop Issues and Copilot Keyboard Shortcut Not Working covers neighboring causes that can produce the same symptom on AI laptops. See also Thunderbolt 5 Lunar Lake Not Working for the other half of this connection chain.

Frequently asked questions

What is the Copilot key long press supposed to do?
On Copilot+ PCs, a short press of the Copilot key opens the Copilot app, while a long press is designed to trigger voice input or a deeper Copilot action depending on your Windows version and app build. If nothing happens on a long press, the key event is usually being intercepted, remapped, or ignored by an outdated app.
Why does a short press work but a long press does not?
Short and long presses are handled as separate key events. A short press works when the basic key mapping is intact, but the long-press event depends on the Copilot app’s background service, keyboard firmware, and Windows key handling. Any one of those layers can drop the long-press event while the short press still works.
Can a BIOS update break the Copilot key long press?
Yes. Some BIOS or embedded-controller updates change how the keyboard reports special keys, which can silently alter long-press behavior. Reinstalling the keyboard driver and checking for a newer BIOS from your laptop maker usually restores it.
Does remapping software block the Copilot key long press?
Often. Tools like PowerToys Keyboard Manager, AutoHotkey, or gaming keyboard utilities can intercept the Copilot key before Windows sees the long-press event. Disabling those tools temporarily is a quick way to confirm whether one of them is the cause.