{
"title": "Windows 11 KB5094126 Brings Shared Audio: Connect Two Bluetooth LE Headsets to One PC",
"content": "Microsoft has quietly rolled out one of the most requested audio features in years: native support for broadcasting system audio to two Bluetooth LE Audio devices simultaneously. Tucked inside the June 2026 cumulative update for Windows 11, KB5094126, the new Shared Audio feature lets a single PC stream synchronized sound—from music to calls—directly to two pairs of Bluetooth LE Audio earbuds, headphones, or speakers. No extra dongles, no sketchy third-party software, just a clean Bluetooth connection that pairs two sinks at once.
This isn’t a gimmick. It solves a real problem: sharing audio without sacrificing personal space. Think long-haul flights with a partner, late-night gaming sessions requiring dual headsets, or collaborative work where both people need crystal-clear voice from the same Teams call. With the proper hardware and the June update, Windows 11 finally treats dual Bluetooth audio as a first-class citizen.
What exactly is Shared Audio in Windows 11?
Shared Audio leverages the Bluetooth LE Audio standard’s broadcast capability, specifically the Common Audio Profile (CAP) and the Public Broadcast Profile (PBP). Unlike classic Bluetooth’s point-to-point limitation, LE Audio supports unicast streams to multiple devices from a single source. Windows 11 extends this by allowing the OS to create a virtual audio endpoint that mirrors the system’s stereo mix to two LE Audio devices in perfect sync.
The result is lip-sync-accurate audio across two headsets with a latency under 30 milliseconds—low enough for video, gaming, and calls. Each listener gets independent volume control from Windows’ side, though fine-tuning still happens on the device itself for most earbuds. The feature works system-wide: any application that pumps audio through the default playback device will be heard on both paired headsets.
It’s important to distinguish this from previous Windows multi-stream attempts. Older Bluetooth Audio options like “Stereo Mix” or third-party virtual cables often introduced lag, dropped quality, or forced mono playback. KB5094126 replaces all that with a native, driver-level implementation that respects LE Audio’s high-efficiency LC3 codec, meaning no re-encoding losses and better battery life on the listening devices.
Which PCs and devices support it?
Shared Audio requires three pieces of the puzzle: a Windows 11 PC running build 26200 or later (post-24H2), a Bluetooth 5.2 or newer adapter with LE Audio support, and two compatible LE Audio sinks—typically earbuds or headphones that advertise CAP or PBP profiles. Most flagship Bluetooth 5.3 headphones released in 2025 and 2026 ship with these profiles, including models from Sony, Samsung, Jabra, and Audio-Technica.
On the PC side, almost any modern laptop with an Intel AX210/211 or MediaTek MT7921/7925 module will work, provided the firmware is up to date. Desktop users may need to upgrade their Bluetooth adapter; dongles like the Plugable USB-BT5LE or the Asus BT500-HD have been confirmed by early testers to enable Shared Audio seamlessly. Microsoft’s Surface line, from the Pro 9 onward, is fully compatible out of the box once KB5094126 is installed.
The update itself is being pushed through Windows Update as an automatic cumulative patch for all editions of Windows 11. Users can manually trigger the download via Settings > Windows Update > Check for updates. After installation, the feature is automatically enabled—no Group Policy or registry tweaks needed, though IT admins can disable it via a new “Bluetooth\DisableSharedAudio” policy in Intune.
How to set up dual Bluetooth LE Audio in under a minute
With all hardware in place, the process is surprisingly simple. Windows 11’s quick settings panel now includes a new “Share Audio” button under the Bluetooth section. Here’s the step-by-step flow:
- Pair both Bluetooth LE Audio headsets with your PC as you normally would. They’ll appear in the audio device list.
- Connect the first headset and start playing audio to verify it’s working.
- Open the quick settings (Win + A) and click the Bluetooth icon to expand connected devices.
- Find the first headset and click the three-dot menu next to its name; select “Start Shared Audio.”
- Windows will scan for nearby, paired LE Audio devices that support the feature and present them in a list. Choose the second headset.
- Within a second or two, both headsets become active, and a small badge appears on the volume mixer indicating “Shared Audio (2 devices).”
Ending a shared session is just as easy: click the same Bluetooth menu, choose “Stop Shared Audio,” or simply disconnect one of the devices. The remaining headset continues without interruption.
Under the hood: latency, codec, and sync magic
The technical backbone of Shared Audio is the inclusion of a low-latency multiplexer in Windows’ audio engine. When the feature activates, the system creates a virtual audio device that takes the stereo output and simultaneously encodes it using the LC3 codec for each connected sink. LC3, mandatory for LE Audio, delivers equivalent or better quality than SBC at half the bitrate—typically 192 kbps per stream—while being more resilient to packet loss.
Synchronization is handled by the Bluetooth controller’s isochronous channels. Windows uses the Controller’s Connected Isochronous Stream (CIS) for each link, aligning timestamps so that both devices render audio within the same 10 ms window. End-to-end latency from application to eardrum hovers around 25–28 ms, making it imperceptible for video lip-sync (which requires <40 ms). For comparison, Samsung’s Dual Audio on Galaxy phones adds about 50–70 ms, and Apple’s Share Audio over AAC lands at 80–120 ms.
Crucially, the connection stays robust even when one listener moves out of range. If a headset drops, the remaining one keeps playing without a hiccup, and Windows automatically attempts to re-add the lost device when it comes back within range. There’s no need to restart the stream.
Battery life and real-world performance impacts
Because LE Audio is designed from the ground up for low energy, streaming to two devices doesn’t double the PC’s Bluetooth power draw. In fact, measurements by early adopters on the Windows Forum show only a 5–8% increase in total battery consumption on a Surface Laptop 7 during a two-hour movie, compared to single-device streaming. On the headset side, battery drain is roughly equivalent to standard LE Audio playback—most earbuds lose about 10% per hour of shared listening, which is on par with solo use.
Audio quality remains pristine. The LC3 codec avoids the generational loss typical of transcoding, because audio is encoded once from PCM to LC3 per device. There’s no decode-reencode cycle, so what you hear is identical to a single-stream experience. Standard stereo content is preserved; spatial audio formats like Dolby Atmos for Headphones and Windows Sonic also work, though the spatial processing is applied independently per device, meaning each listener gets their own head-related transfer function (HRTF) if supported by the headset.
Known issues and community feedback
As with any v1 feature, the rollout isn’t flawless. Windows Forum threads have highlighted several rough edges:
- Manual reconnection trouble: After a system sleep or reboot, Shared Audio sometimes fails to resume automatically. Users must manually stop and restart the session.
- Mic routing confusion: Windows does not yet allow selecting which headset’s microphone is used for input during a shared session; it defaults to the last connected device, which can lead to Teams calls where one person’s voice is lost.
- Third-party device compatibility: While most flagship earbuds work, budget brands and older LE Audio devices that only implement the Telephony and Media Audio Profile (TMAP) without the Public Broadcast Profile may not show up in the sharing list. Microsoft has published a compatibility list, but it’s far from exhaustive.
- Gaming headset limitations: Headsets that use a proprietary low-latency dongle (e.g., Logitech Lightspeed, SteelSeries) cannot participate in Shared Audio unless they also expose a standard LE Audio connection—most do not.
How does this compare to Apple’s Share Audio and Samsung Dual Audio?
For years, Apple and Samsung offered similar functionality, but with heavy ecosystem locks. Apple’s Share Audio works only between Apple devices and select Beats headsets, relying on AAC and H1/W1 chips. Samsung’s Dual Audio is limited to Galaxy phones and specific Samsung earbuds. Windows 11’s Shared Audio is, by contrast, an open standard that works across any Bluetooth LE Audio hardware from any brand—so long as they follow the spec.
That openness means you can pair a Sony WH-1000XM7 with a Nothing Ear (stick) Gen 2, or mix a premium Jabra headset with a budget Anker Soundcore pair, and they’ll play in sync. It also enables flexibility in enterprise: two surgeons using different approved headsets can listen to the same vital-sign alerts during a procedure.
Latency and codec efficiency also tip the scales. Apple’s Share Audio, stuck on AAC, introduces noticeable lag for video, whereas LC3’s design for short packets keeps Windows’ implementation tight. Samsung’s Dual Audio uses a proprietary scalable codec, but it fails when you pivot to a mixed-vendor setup—Windows avoids that entirely.
The bigger picture: what this means for Windows as a platform
Native dual Bluetooth audio isn’t just a convenience feature; it’s a signal that Microsoft is serious about embracing modern Bluetooth standards and reducing reliance on legacy USB dongles. The LE Audio stack in Windows 11 now matches or exceeds what mobile OSes offer, and with Auracast broadcast support already in testing (build 26350), Windows is poised to become a first-rate audio hub.
For enterprise, this unlocks new training and collaboration scenarios. A single laptop can feed audio to multiple participants in a huddle room without a speakerphone. In accessibility, a visually impaired user and their assistant can share TTS output seamlessly. In education, two students can watch an instructional video together during a library session without disturbing others.
Microsoft’s decision to bake this into a standard cumulative update—rather than locking it behind a feature update or hardware check—means the feature will reach over 600 million devices within weeks. That’s a massive install base that will encourage headphone makers to prioritize LE Audio compliance and refine their multipoint implementations.
What’s next? Auracast and beyond
Shared Audio is just the first step. The Bluetooth Special Interest Group’s Auracast specification allows one source to broadcast audio to an unlimited number of receivers. Windows 11 Insider builds have already demonstrated a beta Auracast transmitter function that can flood a classroom with high-quality LC3 audio. Combined with Shared Audio’s unicast pairing, Windows could soon let you dynamically switch between a private dual-listener session and a public broadcast from the same PC.
Microsoft has also hinted at adding a GUI for per-device codec selection, giving power users the ability to force LC3 or fall back to LE Audio’s mandatory compatible mode with legacy SBC. Such granular control would be a boon for audiophiles and IT managers troubleshooting mixed environments.
In the near term, expect a rapid patching cycle to address the reconnection bug and microphone selection. The company’s feedback hub is actively collecting votes for a “Select microphone device during Shared Audio” feature, which currently tops the Bluetooth category with over 12,000 upvotes.
Troubleshooting common Shared Audio problems
If you’ve followed the setup but only hear audio from one headset, or the “Share Audio” button is greyed out, here are the most frequent culprits and fixes:
- Outdated Bluetooth firmware: Even if your adapter supports LE Audio, it may need a firmware update from the PC manufacturer. Check Windows Update optional driver updates, or visit your laptop’s support page for the latest Bluetooth radio firmware.
- Secondary device not in pairing mode: The second headset must be paired but not necessarily connected. However, some earbuds require you to put them in pairing mode again during the “Scan for devices” step. Check your headset’s manual for dual-connection instructions.
- Audio enhancements interfering: Disable all audio enhancements for both the primary and secondary device in Sound settings > Properties > Advanced. Spatial sound can sometimes block shared sessions.
- Bluetooth coexistence with Wi-Fi: 2.4 GHz interference can disrupt the isochronous streams. If audio cuts out, try switching your PC’s Wi-Fi to 5 GHz (or 6 GHz) or moving the Bluetooth adapter away from the router.
- Missing LE Audio profile: Verify the second headset truly supports CAP/PBP. You can check in Device Manager > Bluetooth, find the device, look at Properties > Details > Hardware Ids, and ensure it