Saying “Hey Copilot” and getting silence is a strange kind of failure — the feature is supposed to be effortless, and when it does not respond you are left wondering whether it is deaf, disabled, or simply not there. Wake word problems are usually settings or microphone issues, not AI failures, which is good news: they are fixable with ordinary checks.
The diagnostic split is simple. First, confirm the feature is actually available and enabled on your PC. Then confirm the microphone works and is the one Copilot is listening to. Most reports resolve in one of those two steps; the rest involve app updates, permissions, or environment noise, each with its own fix below.
Battery and sleep behaviour can also interfere, since wake listening interacts with power states. If your machine drains overnight, see our guide to Copilot+ PC sleep battery drain , and HP users should check HP EliteBook X G1i AI issues . If you run containers or heavy tools on the same machine, our guide to Docker Desktop on ARM Windows covers the resource contention that can starve voice services.
Why this happens
- Wake word disabled: The feature is off by default in some versions or was switched off during setup.
- Microphone permission denied: Copilot cannot listen without microphone access, and a denied permission blocks it silently.
- Wrong microphone selected: A headset, dock, or external mic may be selected while you speak into the laptop’s built-in array.
- Microphone muted or too quiet: Hardware mute keys, low gain, or privacy shutters block input before Copilot ever hears it.
- Feature not yet available: Wake word support rolls out by region and app version, so it may be absent on your PC.
- Background noise or distance: Loud environments and speaking from across the room reduce detection reliability.
- App not running in the background: If Copilot is fully closed, it cannot listen for the wake phrase.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Confirm the wake word is enabled
Start with the setting itself. If the toggle is off, nothing else matters, and turning it on is a ten-second fix.
- Open the Copilot app and go to Settings.
- Find the voice or wake word section.
- Confirm “Hey Copilot” or voice activation is turned on.
- If the option is missing, the feature may not have reached your app version — update Copilot from the Store.
- Toggle it off and back on to clear any stale state.
- Say “Hey Copilot” clearly and check for a response.
Fix 2: Test the microphone itself
If the setting is on but nothing happens, the microphone is the next suspect. A quick test in Windows sound settings tells you whether input is reaching the system at all.
- Open Settings, go to System, then Sound.
- Under Input, select your microphone and speak.
- Watch the input volume bar — it should move as you speak.
- If it does not move, check the hardware mute key and privacy shutter.
- Try a different microphone, such as a headset, to isolate the fault.
- Set the working microphone as the default input device.
Fix 3: Grant microphone permission to Copilot
Windows privacy settings can block Copilot’s microphone access even when the mic works elsewhere. Confirming the permission removes a silent blocker that produces exactly this symptom.
- Open Settings, go to Privacy & security, then Microphone.
- Confirm microphone access is allowed for the device.
- Scroll to Copilot and confirm its permission is on.
- If it was off, turn it on and restart Copilot.
- Say “Hey Copilot” and check for a response.
- If permission keeps reverting, check for a work or school policy controlling it.
Fix 4: Make sure Copilot is running in the background
Wake word listening requires Copilot to be alive in the background. If it is fully closed or blocked from background activity, there is nothing listening for the phrase.
- Open Copilot and leave it running, minimised rather than closed.
- Check Task Manager to confirm Copilot’s background process is present.
- Open Settings, go to Apps, then Copilot’s advanced options.
- Confirm background app permissions allow it to run.
- Add Copilot to startup if you want wake word available after boot.
- Test the wake phrase with Copilot minimised.
Fix 5: Update the Copilot app and Windows
Wake word support improves with app updates, and older versions may lack it entirely or have detection bugs. Updating both the app and Windows aligns the feature with its latest fixes.
- Open the Microsoft Store and update Copilot.
- Open Settings, go to Windows Update, and install pending updates.
- Restart after updating.
- Recheck the wake word setting — it may appear only after the update.
- Enable it and test with a clear “Hey Copilot.”
- For persistent issues, see the official Windows support pages .
Fix 6: Improve the listening environment
Detection is a signal problem as much as a software problem. Speaking clearly, closer to the mic, and in a quieter room can turn an unreliable wake word into a reliable one without changing any setting.
- Move within a couple of metres of the laptop.
- Reduce background noise from fans, music, and TV.
- Speak the phrase clearly, at normal volume, without rushing it.
- Face the laptop’s microphone array directly.
- Test several times to distinguish random misses from total failure.
- If detection works close up but not at distance, that is normal range behaviour.
Fix 7: Reset the Copilot app
When settings, permissions, and hardware all check out but the wake word still fails, the app’s own state may be corrupt. A repair or reset clears it without affecting your files.
- Open Settings, go to Apps, then Installed apps.
- Find Copilot and open Advanced options.
- Choose Repair and test the wake word.
- If Repair fails, choose Reset.
- Sign back into Copilot and re-enable the wake word.
- Test again in a quiet room, close to the microphone.
Closing
“Hey Copilot” silence is almost always a setting, a permission, or a microphone — in that order. Enable the feature, prove the mic works, grant permission, and keep Copilot running, and hands-free activation usually returns. If it works close up but not across the room, that is the normal limit of far-field detection, not a fault worth chasing further.
