Bluetooth headset microphone not working
Bluetooth headsets confuse every operating system the same way: one physical headset appears as two audio devices, and only one of them has a microphone. Add the audio-quality drop that happens when the mic engages, and it's easy to conclude the headset is broken when it's really a profile-selection problem. Here's what's going on and how to fix it.
Step-by-step fix
- Understand the two profiles: A2DP ("Stereo") is high-quality playback with no microphone; HFP/HSP ("Hands-Free") carries the mic but plays phone-call-quality audio. Your OS shows both as separate devices for the same headset — that's normal.
- On Windows, open Sound settings and set the "Headset (Hands-Free AG Audio)" entry as the default input. Apps that should hear you must use that Hands-Free device — selecting the Stereo entry as an input gives pure silence, because it has no mic at all.
- Check the Hands-Free service is enabled: in Bluetooth & devices → Devices → More devices and printer settings (or Control Panel → Devices and Printers), right-click the headset → Properties → Services and tick Handsfree Telephony. If it's unticked, Windows never creates the microphone device in the first place.
- Re-pair from scratch: remove/forget the headset, power-cycle it, put it back in pairing mode and pair again. Half-completed pairings register the audio sink but not the mic — fresh pairing fixes more headset-mic cases than any other step.
- Check the headset's own mute: boom-arm headsets often mute by flipping the arm up, and many earbuds mute on a long-press gesture. A voice prompt or LED usually indicates mute — consult the quick-start card if unsure.
- Run the CheckMyMic microphone test, pick the headset's Hands-Free entry in the device dropdown, and watch the meter while you speak. Expect the call-quality sound while the mic is live — that's the HFP trade-off, not damage.
- On macOS the profile switch is automatic, but on Linux you may need to pick it yourself: in pavucontrol's Configuration tab choose the "Headset Head Unit (HSP/HFP)" profile. If that profile is missing, your distro needs an HFP backend enabled (modern PipeWire ships one; PulseAudio setups may need ofono).
Frequently asked questions
Why do I see two audio devices for one headset?
Bluetooth exposes one profile per job: A2DP for high-quality stereo playback (no mic) and HFP/HSP for two-way calls (mic, lower quality). The OS lists each as its own device. Playback can use either; the microphone only exists on the Hands-Free one, so inputs must point there.
Why does my headset's sound quality get worse during calls?
The link drops to the hands-free profile so the microphone can run — that profile carries far less audio bandwidth, and classic Bluetooth can't run mic and high-quality playback together. It's unavoidable on A2DP/HFP headsets; newer LE Audio gear improves this, and a wired connection or separate mic sidesteps it entirely.
The headset connects but no microphone device appears at all.
Either the Hands-Free service is disabled (tick Handsfree Telephony in the headset's Bluetooth properties on Windows), the Bluetooth driver is old (update it from the PC or dongle maker), or — worth checking — the product is actually playback-only headphones with no mic. Re-pair after fixing any of those.
I've tried everything and the headset mic still doesn't work — what now?
Pair the headset with a phone and test there: if the mic works on the phone, your PC's Bluetooth stack or driver is the problem — and if the headset shipped with its own USB dongle, use it; the dongle carries its own radio and skips the PC's Bluetooth entirely. Confirm each attempt with the CheckMyMic mic test, and see our AirPods guide for the Apple-specific version of these pitfalls.