Bluetooth Headset Mic Not Working on Windows: Hands-Free vs Stereo Audio Profiles Explained
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic TestYour Bluetooth headset mic is not working on Windows because Windows switched the device to the Stereo profile, which disables the microphone entirely. Bluetooth audio runs on two mutually exclusive profiles: A2DP (Advanced Audio Distribution Profile) handles high-quality stereo playback but carries no microphone channel, while HFP/HSP (Hands-Free Profile / Headset Profile) enables the mic but drops audio quality to a narrow 8 kHz or 16 kHz codec. Windows selects between these automatically and gets it wrong constantly, especially after driver updates, pairing resets, or when a second audio application opens.
Why Windows Breaks the Bluetooth Audio Profile
The root cause is the Windows Bluetooth audio stack managing two separate virtual devices from one physical headset. In Device Manager under Sound, video and game controllers you will see your headset listed twice: once as a stereo playback device and once as a Hands-Free AG audio device. When any application requests high-fidelity playback, the audio engine switches the radio link to A2DP. The microphone endpoint disappears from the system because HFP is no longer active on that SCO (Synchronous Connection-Oriented) link.
This is not a driver bug in the traditional sense. It is a bandwidth arbitration problem at the Bluetooth controller level. The SCO link for HFP and the ACL link for A2DP cannot both run at full capacity simultaneously on most Bluetooth 4.x and early 5.0 chipsets. Qualcomm aptX and LC3 codecs on Bluetooth 5.2 hardware handle this better, but most consumer headsets still fall back to the old arbitration behavior.
Step-by-Step Fix: Force the Correct Audio Profile
- Right-click the speaker icon in the system tray and select Sound settings.
- Under Input, open the dropdown for your microphone device. If you see your headset listed with a name ending in Stereo or A2DP, that is the wrong endpoint. Select the entry that ends in Hands-Free AG or Headset.
- Open Control Panel > Hardware and Sound > Sound, then go to the Playback tab. Right-click your headset's Hands-Free AG playback entry and set it as the Default Communication Device. Do not set it as the Default Device; leave that on your speakers or the A2DP entry for general audio.
- Go to the Recording tab. Right-click the Hands-Free AG microphone and set it as both Default Device and Default Communication Device.
- Double-click the Hands-Free AG microphone entry, go to Levels, and set the microphone volume to 80. Values above 85 introduce AGC saturation artifacts on most headsets using CVSD encoding.
- Under the Advanced tab, set the Default Format to 1 channel, 16 bit, 16000 Hz. Do not attempt 44100 Hz here; the HFP codec does not support it and Windows will silently fail the format negotiation.
After applying these settings, use the Mic Test tool to confirm the microphone is capturing audio. Speak at a normal distance of 20 to 30 cm and watch the level meter respond. If it stays flat, the profile switch has not taken effect yet.
Fixing Bluetooth Headset Mic Not Working in Discord
Discord has its own audio subsystem that overrides Windows defaults and makes this problem worse. A bluetooth headphones mic not working in Discord specifically is almost always Discord selecting the A2DP endpoint on its own.
- Open Discord and go to User Settings > Voice & Video.
- Under Input Device, manually select your headset's Hands-Free AG microphone from the dropdown. Do not leave it on Default.
- Under Output Device, you can leave this on your headset's stereo entry if you want full-quality playback, but understand that during an active voice call Discord will try to hold both links simultaneously. On chipsets that cannot handle this, audio will stutter or the mic will cut out.
- Scroll down to Voice Processing and disable Echo Cancellation, Noise Suppression, and Automatic Gain Control as a test. Discord's processing stack running on top of Windows's own AGC on an HFP stream causes double-processing artifacts that can make the mic appear silent to other users.
- Set Input Sensitivity to manual and drag the threshold to -60 dB as a starting point.
| Bluetooth Profile | Microphone Available | Playback Quality | Sample Rate | Use Case |
|---|---|---|---|---|
| A2DP | No | High (stereo) | Up to 44100 Hz | Music, video playback |
| HFP (Hands-Free Profile) | Yes | Low (mono) | 8000 Hz or 16000 Hz | Calls, voice chat, Discord |
| HSP (Headset Profile) | Yes | Low (mono) | 8000 Hz | Older devices, basic calls |
Driver-Level and Registry Fixes When the Profile Switch Fails
If the Hands-Free AG device does not appear in your Sound settings at all, the HFP service is disabled or the Bluetooth driver is not enumerating the profile correctly.
- Open Device Manager, expand Bluetooth, and look for your Bluetooth radio adapter. Right-click it and select Update driver > Browse my computer > Let me pick. Select the Microsoft-generic Bluetooth driver rather than any OEM-branded entry. OEM Bluetooth stacks from Intel and Realtek frequently suppress HFP enumeration on non-certified headsets.
- Open Services (services.msc) and verify that Bluetooth Audio Gateway Service (BthAGService) is set to Automatic and is running. If it is stopped, start it. If it will not start, the Bluetooth Support Service (bthserv) is likely also stopped; start that first.
- In the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}, locate the subkey for your Bluetooth adapter and check for a DWORD value named DisableHFP. If it exists and is set to 1, change it to 0.
- Unpair the headset completely, reboot, and re-pair. During re-pairing, Windows re-negotiates which profiles to expose. Do this with no other audio applications open.
Once you have audio routing confirmed, you can also run a quick Speaker Test to verify your playback path is intact and a Meeting Check to simulate a full voice call environment before jumping back into a live session.
Frequently Asked Questions
Why does my Bluetooth headset mic stop working when I play music?
Playing music through the headset triggers A2DP mode. The moment A2DP activates, the SCO link carrying HFP drops and the microphone disappears from Windows. You either need to route music playback through a different output device, or accept the lower audio quality of HFP for everything during calls.
My headset mic shows up in Device Manager but has no signal. What is wrong?
The device is enumerated but the SCO audio link is not open. This happens when the Bluetooth Audio Gateway Service is running but the headset firmware is not completing the HFP connection handshake. Try toggling the headset off and on while it is connected. Some headsets, particularly those using older CSR8645 chipsets, require a manual mode switch via a physical button to activate the microphone channel.
Does Windows 11 handle Bluetooth audio profiles better than Windows 10?
Marginally. Windows 11 22H2 and later include an updated Bluetooth audio driver (bthhfenum.sys version 10.0.22621 and above) that is faster at profile arbitration. The fundamental A2DP vs HFP conflict is unchanged because it is a Bluetooth specification constraint, not a Windows bug.
Why is my bluetooth headset mic not working in Discord but fine in other apps?
Discord's audio engine opens its own exclusive audio session and frequently re-selects the default device rather than the one you configured in Windows. Always set the input device explicitly inside Discord's Voice and Video settings, and disable Discord's Krisp-based noise suppression as a first diagnostic step since it can silently block input from HFP streams it classifies as too low quality.
Can I use my Bluetooth headset mic for recording in Audacity or a DAW?
Yes, but you are limited to 16000 Hz mono at best. Set Audacity's project sample rate to 16000 Hz under Edit > Preferences > Quality before recording. Attempting to record at 44100 Hz with an HFP microphone source will produce a file that appears to record but contains silence or heavily aliased audio because Windows is resampling a 16 kHz signal through a mismatched buffer.
My headset is paired but the Hands-Free AG option never appears. What now?
The headset's HFP profile may not be advertising correctly to Windows. Remove the device from Bluetooth settings, open Device Manager and under View select Show hidden devices, then delete every instance of that headset under Bluetooth and under Sound. Reboot, re-pair, and allow Windows a full 30 seconds after pairing to enumerate all profiles before opening Sound settings.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Mic Test