Bluetooth Headphones Connected but No Sound in Windows 11: Output, Profiles, Services, Drivers, and App Routing

A Bluetooth headset can appear as Connected under Settings > Bluetooth & devices while Windows is still sending playback to speakers, a monitor, a USB DAC, or another remembered endpoint. Treat Bluetooth link state and audio routing as separate layers. Microsoft’s current support guidance for this exact symptom starts by confirming that the Bluetooth device is selected under Settings > System > Sound > Output.

Before changing drivers or removing the device, play a known local system sound or media file, open the taskbar sound control, and select the Bluetooth headphones explicitly. Confirm that neither the system output nor the headset’s own hardware volume is muted. If sound begins immediately, the radio link was working and the fault was routing rather than pairing.

Windows 11 can maintain per-application volume and output choices. If notification sounds or another application play through the headset while one browser, game, player, or voice application remains silent, open Settings > System > Sound > Volume mixer. Microsoft documents that an application can be muted independently and can use an output device different from the system default.

Set the affected application to the intended Bluetooth output or return it to the default route, then fully restart the application if it cached an endpoint when it launched. This branch is especially important after docking, connecting HDMI or DisplayPort displays, using USB audio, or switching between several Bluetooth devices because the application may still be targeting an endpoint that is no longer active.

For classic Bluetooth audio, Microsoft documents A2DP as the playback path and HFP as the hands-free path used when the headset microphone is required. On Windows 11 the user-facing endpoints are unified for devices that support HFP, and Windows can switch profile behavior automatically when an application opens the headset microphone or creates communications audio.

That distinction matters because “connected but sounds wrong” and “connected but completely silent” are different diagnoses. Opening the headset microphone can move the device into the hands-free path; it should not by itself justify deleting drivers or forcing codec utilities. If silence begins only when a voice application opens the microphone, close that application, release microphone use, and retest ordinary playback. Then inspect that application’s input/output choices rather than assuming the Bluetooth radio has failed.

Microsoft currently directs Windows 11 users to the automated Bluetooth troubleshooter in the Get Help app for connected-but-no-sound problems. Windows also provides an audio troubleshooter for general no-sound states. These are reasonable after the output and per-app routing checks because they can detect configuration or service problems without immediately making broader system changes.

If the headset appears under Bluetooth devices but does not appear at all under Sound > Output, treat that as an endpoint-detection problem rather than a simple volume problem. Microsoft notes that missing audio outputs can result from a missing, disabled, outdated, or non-loading driver. That is stronger evidence for the driver/device branch than merely seeing the Bluetooth device listed as paired.

If multiple audio endpoints stop working at once, or the Bluetooth output remains present but Windows audio behaves inconsistently after sleep, an update, or repeated device switching, a temporary Windows audio-service problem becomes plausible. Microsoft documents restarting Windows Audio and Windows Audio Endpoint Builder as a supported recovery step for some audio failures.

Do not make service configuration changes permanent or disable unrelated services. Restart the documented audio services, then retest the same output and application. If ordinary speakers work and only one Bluetooth headset remains silent, move back to Bluetooth-specific pairing, profile, and driver checks rather than repeatedly restarting the entire audio stack.

Microsoft recommends removing and re-adding the Bluetooth device when the connection state is stale or normal playback checks fail. In Windows 11, use Settings > Bluetooth & devices, remove the affected device, put the headset into its documented pairing mode, and add it again. Also try turning Bluetooth off and back on before assuming the headset itself is defective.

Re-pairing rebuilds the Windows device relationship, so it is more disruptive than simply selecting the correct output. Verify the headset is not simultaneously connected to another phone, tablet, console, or PC in a way that changes its active audio source. Multipoint behavior is device-specific, so use the headset manufacturer’s documentation rather than assuming every model handles two hosts the same way.

If the problem began after a Windows or OEM driver update, the Bluetooth output disappears from Sound settings, Device Manager shows an error, or re-pairing repeatedly fails to recreate a usable audio endpoint, inspect the Bluetooth adapter and relevant audio devices in Device Manager. Microsoft’s current Bluetooth guidance recommends updating the Bluetooth adapter driver and restarting when required.

Prefer Windows Update or the PC, motherboard, Bluetooth-adapter, or laptop manufacturer’s supported package. If a known-good previous driver is still available and the failure began immediately after a driver change, use the existing Core Tech Tips Windows 11 driver-rollback guide for the generic rollback procedure. Avoid third-party driver-updater utilities, random INF packages, and registry edits presented as universal Bluetooth fixes.

After each change, test the same known audio source and record what changed: does the device appear under Output, do Windows system sounds work, does only one application fail, does silence begin when the headset microphone opens, and does re-pairing recreate the endpoint? Those observations identify the failing layer far more reliably than applying several fixes at once.

If the headset works normally with another PC or phone but remains silent on this Windows 11 system, focus on this PC’s routing, Bluetooth adapter, Windows audio state, and supported drivers. If the headset is silent on multiple hosts, the device, its firmware, battery/power state, or its own controls become more likely. Conversely, if several Bluetooth headsets fail only on one PC, the common Windows/Bluetooth host path deserves more attention than each headset individually.