Windows

Windows 11 selects hands-free profile for Bluetooth headset; apps play no high-quality audio

Environment

Environment

Windows 11 Pro 22H2 laptop with integrated Intel AX200 Bluetooth adapter, Bose QC45 paired via Windows Bluetooth settings and the vendor app installed

Symptoms

Symptoms

Headset pairs and shows as 'Connected' in Settings → Bluetooth. System notification sounds are audible, but music in Spotify and audio from Teams/Zoom are either muted or only available in mono / very low quality. In Teams the selected device is 'Headset (Hands-Free AG Audio)' and shows 8000 Hz sample rate; Windows shows two device entries for the headset: 'Headphones (A2DP)' and 'Headset (Hands-Free)'. Microphone from headset appears to work in Voice Recorder.

Observations

Observations

When an app is started, Windows sometimes switches the headset to the 'Hands-Free' device (HFP/HSP), shown in Sound settings as Default Communications Device. Changing default playback to 'Headphones (A2DP)' in Sound Control Panel restores quality for system sounds but Teams still shows only the Hands-Free device available. Device Manager shows Microsoft Bluetooth Enumerator and Intel Bluetooth driver; no obvious yellow warnings. Bluetooth Support Service is running. Re-pairing creates same behavior. Vendor-supplied Bluetooth driver (WIDCOMM) was tried and removed; both Microsoft and vendor drivers present at different times with identical symptoms.

Already attempted

Already attempted

Repaired device; toggled 'Allow apps to take exclusive control' in advanced Sound settings; disabled Hands-Free Telephony under device's Services in Control Panel (when visible); uninstalled Bluetooth adapter and reinstalled driver; installed latest Windows updates; tested with different apps (Spotify, Teams, Google Meet in Chrome); tested with a different Bluetooth headset (same laptop) which uses A2DP for music and behaves correctly. Rebooted and created a new local Windows account to rule out per-user setting—issue persisted for the original headset only.

Question

Question

How can I ensure apps use the A2DP/AAC high-quality playback profile while keeping headset microphone available for calls, and how to prevent Windows or apps from forcing the headset into Hands-Free profile?

COMMUNITY RESPONSES

Verified community troubleshooting

0 replies

No answers yet..

Showing 0 of 0 community responses
AI DIAGNOSTICS

Incident analysis

Updated 1w ago• Trouble ID

Most likely 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%

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.

Suggested Fixes

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.
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.
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.

Continue troubleshooting

Matched from the title, description and tags