You put on the headset, play something, and it sounds good. You join a call and it collapses: thin, hollow, like a phone from 1998. Nothing is broken and no setting has changed.
This is Bluetooth doing what Bluetooth does, and once you know the mechanism the workarounds follow from it.
One headset, two personalities
A Bluetooth headset does not have one connection to your PC. It has two profiles, and they are mutually exclusive.
A2DP, the stereo playback profile, is high bandwidth and one direction only. This is what plays music. The microphone does not exist in this mode.
HFP, the hands-free profile, is bidirectional, so the microphone works — and to fit both directions into the available bandwidth the audio collapses to a narrow, low-bitrate channel in both directions. Classic hands-free is 8 kHz narrowband. Wideband speech at 16 kHz is better and most modern headsets and adapters support it, but it is still a fraction of what A2DP carries.
The radio cannot do both at once. The moment an application opens your Bluetooth microphone, Windows switches the whole connection to hands-free and your playback quality drops with it. That is why the degradation arrives exactly when the call starts and lifts the moment you leave.
Why Windows shows the headset twice
Open the Sound Control Panel — mmsys.cpl, or Settings → System → Sound → More sound settings — and you will usually find two entries for one device.
Headphones is the A2DP endpoint: playback only, good quality. Headset, sometimes listed as Hands-Free AG Audio, is the HFP endpoint: playback plus microphone, poor quality.
This is not a duplicate to be cleaned up. It is the choice, exposed.
The three ways around it
Split the devices
Select Headphones for output and use a different microphone: the laptop's built-in one, a webcam microphone, a USB microphone. Nothing ever opens the Bluetooth microphone, so the connection stays in A2DP and quality holds.
This is the best-sounding option that keeps the headset, and it is underused. A laptop microphone two feet away is often better than the same headset in hands-free mode, because narrowband is a heavier penalty than distance.
Set it in the meeting application's own device pickers, not only in Windows, since applications keep their own selection.
The trade-off is real: no noise isolation from the headset boom, and if you are somewhere loud the boom microphone wins.
Use a wired or USB headset for calls
The reason professional call setups are still wired is this exact limitation. A USB headset, or a wired one into a jack, has no profile problem, no pairing, no latency and no battery. If you take calls all day this is the answer, and it is inexpensive.
A headset with its own 2.4 GHz USB receiver also avoids the problem, because it is not using Bluetooth profiles at all.
Make sure you are at least getting wideband
Staying on Bluetooth, wideband speech is meaningfully better than narrowband. It depends on the headset, the Bluetooth adapter and the driver all supporting it, and there is no reliable switch to force it in Windows. Two things help: update the Bluetooth adapter driver from the laptop manufacturer rather than Windows Update's generic package, since Bluetooth audio behaviour is heavily driver-dependent; and on a machine with an old or add-on adapter, a modern USB Bluetooth 5 adapter can change the result.
Bluetooth LE Audio is the standard that fixes this properly, with one high-quality bidirectional codec and no profile switch. It needs support in the headset, the adapter and Windows. If you are buying hardware now it is the thing to look for; until you have it at both ends the limitation stands.
Related symptoms with the same cause
- "My headset connects but Teams cannot hear me." The Headphones endpoint is selected for input, and it has no microphone. Choose the Headset endpoint, or use a different microphone.
- "The audio cuts out for a second when the call starts." That is the profile switch happening.
- "AirPods sound bad on my PC but fine on my phone." Apple devices negotiate more capable codecs with each other. On Windows they fall back to standard Bluetooth profiles and the hands-free penalty applies in full.
- "There's a delay between the video and the sound." Bluetooth adds tens to hundreds of milliseconds depending on codec and stack. In a call, latency also makes people talk over each other, because your sense of when the other person stopped is late.
- "It worked yesterday." Windows re-evaluates default devices when a device connects. After a reconnect you may be on a different endpoint than the one you set.
Deciding
| Setup | Call audio quality | Convenience |
|---|---|---|
| Bluetooth headset, its own mic | Poor to acceptable | Best |
| Bluetooth for output, separate mic | Good | Good |
| USB or wired headset | Best | Cable |
| Wireless headset with a USB receiver | Very good | Very good, extra hardware |
If calls are occasional the Bluetooth headset is fine and this is background knowledge. If calls are your job, the wired or receiver option is the one that stops the problem existing.
Check before the call, not during it
Every fix above changes which device is selected, and Windows is liable to change it back when the headset reconnects, the dock is attached, or the machine wakes. That is the failure mode: you fixed it on Tuesday and you are on the wrong endpoint on Thursday.
CallReady runs the check in about ten seconds from the system tray. It confirms the microphone is actually receiving signal rather than merely being selected, flags input that is too quiet or clipping, checks that an output device is available, and warns when Windows has switched to a different camera, microphone or speaker since your last successful check — which is precisely what a Bluetooth reconnect does. It also covers camera and framing, lighting, and network latency and jitter, and gives one verdict rather than a set of numbers.
It cannot tell you which Bluetooth profile you are in; nothing user-facing in Windows does. What it can tell you is that the device changed, which is the event that put you there.