Windows 11 Bluetooth A2DP regression between builds 26200.8037 and 26200.8039 – Samsung HW-J250 audio failure

Highlight / Summary Windows 11 Bluetooth A2DP behaviour with Samsung HW-J250 soundbar has changed between builds 26200.8037 and 26200.8039. In 8037, audio was silent despite successful connection; in 8039, the device disconnects and the audio endpoint disappears. Windows consistently identifies the soundbar as a headphone device rather than a speaker, suggesting Bluetooth profile misclassification. Issue tested on Home and Pro editions, across multiple Intel and ASUS drivers, with ETW traces submitted to Feedback Hub.

System Laptop: ASUS Zenbook 14 UX3405MA Bluetooth adapter: Intel Wireless Bluetooth (AX211)

Audio device Samsung HW-J250 soundbar (Bluetooth 4.1, SBC-only A2DP device)

Driver testing All drivers provided by Intel and ASUS (versions 23.x–24.x) were tested. Device removal, re-pairing, and Bluetooth stack resets were also performed prior to posting.

Behaviour on Windows 11 Build 26200.8037 • Device paired and connected normally • Windows audio meters showed playback activity but the soundbar produced no sound • The device appeared as: "Headphones ([Samsung] Soundbar J-Series)"

Testing suggested incorrect A2DP codec negotiation. When AAC was disabled in the Windows Bluetooth A2DP configuration (forcing SBC), the soundbar produced audio normally.

Behaviour on Windows 11 Build 26200.8039 After updating to this build: • The soundbar connects briefly then disconnects after a few seconds • The audio endpoint never appears and has disappeared entirely

Because of this connection instability the previous workaround cannot currently be tested.

Additional observations • Windows identifies the soundbar as a headphone device rather than a speaker, which may indicate Bluetooth audio profile or endpoint misclassification, explaining the silent audio and disappearance of the endpoint • I have tested this behaviour on both Windows 11 Home and Pro editions • It likely occurs on earlier builds, and based on testing, the issue appears to have started halfway through driver version 22.x

Diagnostics Bluetooth ETW traces were submitted via Feedback Hub (ID: AA108gd5) on March 19, 2026.

Ref of debugging done: https://community.intel.com/t5/Wireless/Windows-11-AAC-A2DP-negotiation-bug-silent-audio-with-Samsung-HW/m-p/1741792/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufE1OMkRTRDdUNjZKRTY3fDE3NDE3OTJ8U1VCU0NSSVBUSU9OU3xoSw#M63717

Has there been a recent change to the Windows Bluetooth stack between builds 26200.8037 and 26200.8039 that could affect A2DP codec negotiation or device profile classification for legacy SBC-only Bluetooth audio devices? Is there a roadmap to restore or maintain compatibility for these devices?