1
Diagnostic step 1
Open Sound Control Panel → Playback and Communication tabs. In Communication tab, set 'Do nothing' for 'When Windows detects communications activity' and test if apps hold A2DP.
FULL AI ANALYSIS
Windows 11 selects hands-free profile for Bluetooth headset; apps play no high-quality audio
Generated Oct 3, 2026, 12:35:03 AM
Analysis summary
Windows exposes two separate Bluetooth audio endpoints for most headsets: a high-quality A2DP sink for playback and a low-bandwidth Hands-Free profile that provides a bidirectional voice channel. Apps or Windows signaling for 'communications' can force the HFP device, which restricts playback quality. The headset or adapter/driver may be reporting or negotiating audio role incorrectly, or a per-app communications-device selection is causing Windows to switch profiles. Vendor drivers and Bluetooth stack behavior (Microsoft vs WIDCOMM) impact which profiles are exposed and when Windows picks the HFP device.
Possible causes
Vendor headset firmware or negotiation bug that drops A2DP when microphone is queried.
90%Windows marks a running app (Teams, browser) as 'communications' causing automatic switch to Hands-Free device.
75%Per-app device selection (browser/Teams) is pinned to the hands-free endpoint even after changing default device.
35%Bluetooth stack or adapter driver incorrectly advertises or prioritizes the hands-free service, forcing profile selection.
30%Suggested fixes
2
Diagnostic step 2
In Sound Control Panel → Playback, explicitly set 'Headphones (A2DP)' as Default Device, and in Recording set headset mic as Default Communications Device. Then launch the app and use its per-app audio device settings (Teams → Settings → Devices, Chrome → Site settings / WebRTC) to select the A2DP playback endpoint if available.
3
Diagnostic step 3
Temporarily disable the Hands-Free Telephony service for the device: Device Manager → Bluetooth → right-click headset → Properties → Services (or in Control Panel → Devices and Printers right-click device → Properties → Services) and uncheck Hands-Free Telephony. This prevents Windows from exposing the low-quality endpoint; verify audio. This is reversible.
4
Diagnostic step 4
If using Microsoft Bluetooth stack, try vendor (WIDCOMM) driver or vice versa — install one at a time and reboot. Record current driver before changing. If vendor driver is proprietary, keep a rollback plan.
5
Diagnostic step 5
Update headset firmware using vendor updater; test same headset on another Windows PC or phone to confirm behavior is headset-specific or PC-specific. If headset behaves correctly on phone, focus on PC Bluetooth adapter/driver settings or a Windows bug in handling profiles and escalate to adapter vendor or Microsoft if necessary.