I am posting this because I have been fighting Bluetooth instability for months, and I have now found several other 2026 reports that look less like unrelated hardware failures and more like variants of the same Windows Bluetooth-audio state problem.
Rather than adding another “Bluetooth is broken” anecdote, I want to document exactly what I can reproduce, what has already been ruled out, and link the similar reports together.
System
Laptop: HP OMEN Gaming Laptop 16-wf0777ng
OS: Windows 11 Pro 25H2
Build: 10.0.26200.9278
BIOS: HP F.30, 30 March 2026
RAM: 32 GB
The original internal wireless module is a Realtek RTL8852AE combination Wi-Fi/Bluetooth device.
Internal Bluetooth:
USB\VID_0BDA&PID_2852
Driver:
16.4041.2603.1300
oem53.inf
Lower filter: RtkBtFilter2
I have also reproduced the current Bluetooth-audio failure while using external Bluetooth adapters instead of the internal radio.
External adapter #1:
Realtek Bluetooth 6.0 Adapter
USB\VID_0BDA&PID_A760
Driver:
20.11.3038.3001
8 June 2026
oem37.inf
Lower filter: RtkBtFilterD
External adapter #2:
TP-Link UB500 Bluetooth 5.4 USB Adapter
USB\VID_2357&PID_0604
Driver:
1.9.1038.3023
24 December 2024
oem126.inf
Lower filter: RtkBtFilter
The internal Bluetooth radio is disabled while an external adapter is active. Windows therefore has only one active Bluetooth radio.
The Bluetooth audio devices used for testing are:
Apple AirPods Pro 3
Marshall MAJOR V
Non-Bluetooth audio through the laptop's internal Realtek speakers continues to work normally while the Bluetooth-audio failure is present.
The actual failure
Bluetooth audio initially works normally. It may work for minutes or hours.
A common warning sign is a short crack/pop or brief audio corruption.
Then Bluetooth audio stops.
The interesting part is that this is not a simple disconnect.
Windows may continue to show the headphones as connected. The Bluetooth device and A2DP MEDIA device can remain OK / CM_PROB_NONE, yet there is no audio.
For both the AirPods and MAJOR V, Windows uses:
DEVPKEY_Device_Service = BthA2dp
Microsoft Bluetooth A2dp Source
Driver:
10.0.26100.1
INF:
microsoft_bluetooth_a2dp_src.inf
During some failures the MMDEVAPI playback endpoint itself also transitions to:
Unknown / CM_PROB_PHANTOM
while the underlying Bluetooth and A2DP MEDIA nodes remain OK.
In other failures the playback endpoint remains OK, is even selected as the default output, but produces no sound. The Windows test-tone button may simply do nothing.
Reconnect behaviour then becomes inconsistent.
Windows can say that the device is connected while the headphones appear to disagree. A reconnect may fail. Sometimes the Bluetooth device reconnects but never becomes a usable audio output. Sometimes another Bluetooth audio device also refuses to establish audio while the system is in this state.
The internal laptop speakers continue working throughout this.
Recovery tests
This is where the case becomes more interesting.
Restarting the Windows Audio service succeeds:
Restart-Service Audiosrv -Force
but does not restore Bluetooth audio.
Restarting bthserv also succeeds but does not restore Bluetooth audio.
BthAvctpSvc behaved differently.
During an active failure:
Restart-Service BthAvctpSvc -Force
became stuck trying to stop the service.
A second elevated shell showed:
STATE : STOP_PENDING
Status : Degraded
PID : 2516
CHECKPOINT : 0
WAIT_HINT : 10000 ms
The process was an isolated svchost.exe hosting only BthAvctpSvc.
I force-terminated that process. Windows immediately created a new instance of BthAvctpSvc under PID 7452 and reported the service as RUNNING / OK.
Bluetooth audio still did not recover. In that test, the AirPods subsequently disappeared from the normal Windows sound-output list even though their underlying Bluetooth/A2DP device nodes were still present.
This makes the AVCTP service hang interesting, but it does not look like restarting that user-mode service alone resolves the underlying condition.
What does recover it
Cycling the Bluetooth radio itself OFF and ON is the smallest recovery action found so far.
No reboot is normally necessary.
After the radio cycle the Bluetooth profiles/endpoints are rebuilt and audio works again.
Occasionally one OFF/ON cycle only partially recovers the system — for example one device reconnects while another still does not — and a second radio cycle is required.
That behaviour is one reason I suspect a state/reinitialisation problem rather than a permanently broken device or static configuration error.
Things already tested
Fast Startup is disabled.
USB selective suspend is disabled on AC and DC.
PCIe ASPM is disabled.
The system is using the High Performance power configuration and WLAN maximum-performance settings.
DISM health check is clean.
SFC verification is clean.
HP hardware/wireless diagnostics pass.
The headphones themselves work with other devices.
The problem occurs with both AirPods and Marshall headphones.
Audiosrv restart does not recover it.
bthserv restart does not recover it.
Hard-restarting the stuck BthAvctpSvc does not recover it.
A Bluetooth radio OFF/ON cycle does.
An older but potentially relevant finding
Before switching to external adapters, the internal RTL8852AE Bluetooth controller had a more severe failure mode in which all Bluetooth devices stopped together, including mouse and keyboard.
I captured that failure with ETW/HCI tracing.
The controller emitted this vendor-specific HCI event:
FF373400010100FFFF2404000005000000E5A00580120000000E000500000025550780000000000000000000010000000024040000A1A00580
The event type is 0xFF (vendor specific) and its first subevent byte is 0x34.
Linux btusb source defines Realtek subevent 0x34 as:
RTK_SUB_EVENT_CODE_COREDUMP
After that event my captured trace stopped showing normal ACL Type-3 traffic while HCI commands/events continued.
I do not claim that this proves the current Bluetooth-audio problem has the same cause. In fact, the newer audio-specific failures have a different fingerprint and have now appeared with external adapters as well. I mention it because there may be more than one Realtek/Windows Bluetooth failure mode on this machine.
The Realtek handling in Linux btusb defines 0x34 as the Realtek coredump subevent.
Important limitation of my adapter comparison
The TP-Link UB500 reproduced the audio failure after I hot-swapped it for the previous USB adapter in the same Windows session.
So I am not yet claiming this is a perfectly independent two-adapter experiment. The next test is a fresh Windows boot with only the UB500 present.
However, the fact that the failure survives a switch from VID_0BDA&PID_A760 / RtkBtFilterD to VID_2357&PID_0604 / RtkBtFilter is enough that I no longer think a physically defective first USB dongle is a satisfactory explanation.
What I am trying to determine
The remaining candidates I see are roughly:
Windows Bluetooth Classic Audio / BthA2dp / AVDTP state
a deeper BTHPORT/BTHUSB state problem
a Realtek Bluetooth filter/firmware interaction shared by these devices
some machine-specific Windows driver-store/state interaction
A generic Realtek HD Audio problem looks less convincing because the internal speakers continue to work and restarting Audiosrv has no effect.
I also have a roughly 65 MB Windows WPR Bluetooth trace containing failure → Bluetooth radio reset → successful recovery, including the Microsoft Bluetooth Audio/A2DP/BTHPORT providers, if somebody familiar with Windows Bluetooth ETW wants to inspect it.
Similar reports
I am linking these because several details overlap strongly, although I am not claiming they are proven to have the same root cause.
1. “Issues with Bluetooth audio volume and disconnecting in Windows 11” — r/WindowsHelp
This is the closest case I have found. Build 26200, several headphones, several Bluetooth adapters, popping/cutoff immediately before audio failure, Windows continuing to behave as if the device is working.
Reddit — Issues with Bluetooth audio volume and disconnecting in Windows 11
2. “Bluetooth issues on Windows 11” — r/techsupport, September 2026
Audio works for a random period and then dies. Windows temporarily still sees the device as connected, subsequent reconnects become unreliable and eventually produce “Couldn’t connect.” Another user in the thread reports that volume control also stops working after the failure.
Reddit — Bluetooth issues on Windows 11
3. “Bluetooth earbuds and headphones disconnecting from Windows 11” — r/bluetooth
Especially interesting because this is another HP OMEN 16, also on Windows Build 26200. Two different audio devices work normally and later lose sound; they initially remain visible as outputs and then disappear. That user reports resolving it by changing the Realtek Bluetooth driver, although the adapter was an RTL8852BE rather than my RTL8852AE, so the driver result is not directly transferable.
Reddit — Bluetooth earbuds and headphones disconnecting from Windows 11
4. Microsoft Q&A — “[Bug] Win11 25H2 - Audio device missing after disconnecting Bluetooth”
Windows 11 25H2, Build 26200.7623. The author describes audio endpoints disappearing after Bluetooth activity and finds that changing Audio Enhancements/format can force reinitialisation. It is not identical to my case, but the endpoint-state behaviour is relevant.
Microsoft Q&A — Audio device missing after disconnecting Bluetooth-win11-25h2-audio-device-missing-after-discon?utm_source=chatgpt.com)
5. Microsoft Q&A — “bluetooth audio that doesn't work”, August 2026
Any Bluetooth audio device connects, Windows shows activity, yet no audio is produced.
Microsoft Q&A — bluetooth audio that doesn't work
6. Microsoft Q&A — “How to fix no bluetooth audio output”, July 2026
Another explicit Windows 11 25H2 report of connected Bluetooth earbuds with no Bluetooth audio output.
Microsoft Q&A — How to fix no bluetooth audio output
7. “Windows 11 Bluetooth Audio Broken: Connected but no sound to ANY device” — r/techsupport
This one is less exact because the failure is persistent rather than intermittent, but it has the same useful distinction: ordinary Bluetooth devices work while Bluetooth audio does not, and the author reports that driver reinstalls and even a Windows reset did not resolve it.
Reddit — Windows 11 Bluetooth Audio Broken: Connected but no sound to ANY device
Question
Has anyone on Windows 11 25H2 / Build 26200 seen this specific state?
Bluetooth/A2DP device nodes still present or OK, but the render endpoint becomes silent or CM_PROB_PHANTOM; Audiosrv and bthserv restarts do not recover it; BthAvctpSvc may hang in STOP_PENDING; only cycling the actual Bluetooth radio reliably rebuilds the audio path.
I am particularly interested in people who can reproduce it with more than one headset or Bluetooth adapter, or who understand the Microsoft BthA2dp / AVDTP / BTHPORT ETW traces.
I am happy to provide the ETL capture and exact event timestamps.
My aim here is not to guess at a registry key. It is to establish whether several of us are observing the same failure class and give Microsoft or a driver vendor enough reproducible evidence to investigate it.
— Mark