Microsoft’s optional June 23, 2026 preview update, KB5095093, nudges Bluetooth LE Audio in Windows 11 closer to public use, but the company still isn’t flipping the switch on Shared Audio for everyone. The patch, available for manual installation on Windows 11 24H2 and the upcoming 25H2, moves Bluetooth LE Audio from a strictly experimental track into a broader pilot phase. Yet the universal activation many hoped would arrive with next month’s Patch Tuesday is nowhere to be found, leaving enthusiasts to once again question the slow pace of adoption.
This C‑week preview is Microsoft’s latest attempt to harden the new audio stack before it touches hundreds of millions of mandatory monthly security updates. KB5095093 doesn’t deliver that instant gratification, but it does lay important groundwork—fixing broken isochronous streams, modernizing the audio endpoint manager, and giving developers new APIs to probe Shared Audio scenarios.
What’s in KB5095093
The update focuses almost entirely on under‑the‑hood Bluetooth improvements. According to Microsoft’s release notes, the core work revolves around how Windows handles connected isochronous streams (CIS), the low‑level transport that lets one source talk to multiple sinks simultaneously. Previously, pairing two LE Audio headsets often resulted in random audio dropouts or a noticeable lag spike whenever Windows switched between the primary and secondary listener. Testers report that those stutters are largely gone after applying KB5095093.
Microsoft also replaced the legacy AudioEndpointBuilder with a more modern Audio Endpoint Framework for LE Audio. This architectural shift allows the OS to keep track of multiple audio endpoints without tangling the UI, and it’s a prerequisite for any future Shared Audio toggle in the quick‑settings menu. Several diagnostic hooks for developers follow the same changes: a new IAudioSharedEndpoint interface appears in the SDK, even though it remains undocumented and hidden from ordinary users.
Perhaps most tellingly, the update carries over a long list of Bluetooth‑specific reliability patches that had been baking in the Dev Channel for weeks. If you’ve been participating in the Insider Program, you’ll recognize the smoother handoff when you walk a room with your laptop and two sets of LE Audio earbuds. Those gains are now available to anyone brave enough to click “Download & install” under optional updates.
Bluetooth LE Audio: A Primer
To understand why KB5095093 matters, you have to look at the promise of Bluetooth LE Audio itself. Introduced with Bluetooth 5.2, LE Audio departs from the classic BR/EDR radio in two fundamental ways: it runs over the Bluetooth Low Energy transport and introduces the LC3 codec. The result is roughly 50 % lower power consumption for comparable audio quality, plus the ability to stream different audio streams to different devices from a single source.
Shared Audio is the consumer‑friendly name for that multi‑stream capability. It encompasses two topologies: connected isochronous streams for personal audio sharing—think two pairs of earbuds receiving the same music from one phone—and broadcast isochronous streams, which allow an unlimited number of receivers to tune in, much like a silent disco. Microsoft has been promising native Windows support for both since 2023, but progress has been glacial compared with Apple, which shipped LE Audio sharing in macOS Sonoma in September 2024.
The technical challenge is real. LE Audio requires the entire stack—Windows driver, Bluetooth controller firmware, and the audio peripheral—to negotiate LC3 parameters dynamically. A mismatch on any one of those layers can cause silent failures. That’s why Microsoft is moving cautiously, using preview updates like KB5095093 to validate the endless combinations of hardware that exist in the Windows ecosystem.
The State of Shared Audio in Windows 11
Despite the changes in KB5095093, Shared Audio remains feature‑flagged. You won’t see a new button in the audio flyout, and no toast notification will invite you to share your sound. Enthusiasts who re‑enable the ID via ViveTool or a registry tweak can now experience fewer glitches and lower latency, but the feature is still clearly in pilot territory.
Testers running the latest Insider builds say the setup experience has improved. You can now add a second listening device from the Bluetooth settings page without unplugging the first, and Windows will remember the pairing for next time. However, volume control across devices is still erratic—touch your laptop’s volume keys and one pair might blast while the other whispers. And there’s no easy way to adjust individual sinks yet, a basic UX expectation that will need to be ironed out before a public launch.
Microsoft’s own diagnostic data likely show that while the core streaming works, the edge cases are numerous. The company seems to be using the preview ring as a quiet beta test, sifting through telemetry to decide when the feature is truly ready for the masses.
Why the Hold‑Up? Hardware Fragmentation and Ecosystem Challenges
Windows’ strength—its vast hardware diversity—is also its greatest weakness for cutting‑edge features like LE Audio. The Bluetooth LE Audio stack requires controller support for isochronous channels, and that support is only reliably present in radios built around Intel’s BE200, Qualcomm’s WCN7851, or the newer MediaTek RZ7xx series. Walk into a big‑box store today and you’ll still find plenty of laptops shipping with older Intel AX210 or Realtek cards that only partially implement the LE Audio spec.
Firmware updates are another wildcard. A laptop maker may have shipped the right silicon but never negotiated a firmware update contract with Intel or Qualcomm, leaving the controller stuck on a year‑old build that lacks the necessary certification. Microsoft can’t force firmware updates from its seat in Redmond, so a universal switch‑on risks creating a deluge of support calls from users who can’t get the feature to work.
Then there’s the peripheral side. While true‑wireless earbud makers like Sony, Samsung, and Jabra have been quick to adopt LE Audio, many budget buds still ship without it. Even among those that do, firmware inconsistencies abound. A broad rollout of Shared Audio would require extensive compatibility testing with dozens of popular headphone models—something a preview update lets Microsoft chip away at without declaring the feature done.
User Feedback: Excitement and Frustration
On Reddit, Twitter, and the Windows‑centric forums, the reception to KB5095093 is a mix of relief and exasperation. “Finally, they fixed the LE Audio stuttering I’ve been complaining about for six months,” wrote one user who manually enabled the flag. But the overwhelming sentiment is: why isn’t it on by default yet? “This is the third preview update that teases Shared Audio, and I’m tired of using ViveTool to make my $200 earbuds work as advertised,” another commenter vented.
The comparison with Apple’s relatively smooth rollout is a recurring theme. Cupertino’s tight control over hardware means it could validate LE Audio sharing on a handful of Mac models and call it a day. Windows, by contrast, must support endless configurations, and the slow pace feeds into the narrative that Microsoft is playing catch‑up.
Some users, however, appreciate the cautious approach. “I’d rather they wait until it’s solid than ship a buggy mess that ruins my conference calls,” one IT pro wrote. Community‑curated lists of confirmed‑working hardware have sprung up, offering real‑world guidance that goes beyond Microsoft’s generic compatibility statement. These lists highlight systems like the Surface Laptop 7, the Dell XPS 15 (2025), and the HP EliteBook 2026 edition as prime candidates for testing.
What This Means for the July Patch Tuesday
The next mandatory Patch Tuesday lands on July 14, 2026. Historically, Microsoft often rolls the C‑week preview fixes into the following B‑week security update, but KB5095093’s own marketing suggests an exception. The update’s changelog explicitly notes that Shared Audio is “not yet enabled for all devices,” a phrase that usually signals a delay of at least one additional month.
Insiders familiar with Microsoft’s release cadence believe the company wants to gather two to four weeks of telemetry from the preview update before committing to a widespread launch. That would push any full rollout to the August Patch Tuesday at the earliest. There’s also the possibility that Microsoft will use the upcoming Windows 11 25H2 general release as the on‑ramp, baking Shared Audio into that version’s feature set and leaving 24H2 on the older code path.
For now, the only way to experience the improvements is to manually install KB5095093 and, if you want to try sharing, enable the hidden flag. Microsoft’s own support article makes no mention of a public toggle, reinforcing the idea that this is still a pilot.
How to Get KB5095093 Now
If you’re eager to test the new Bluetooth stack, open Settings > Windows Update, click “Check for updates,” and then look under “Optional updates” for KB5095093. The download is small—typically under 400 MB—and the install requires a reboot. Make sure you have compatible LE Audio hardware: a Bluetooth 5.2 or later controller and at least two LE Audio‑capable headsets.
Power users can then use the ViveTool command‑line utility to enable the feature IDs 45667701 and 45667702 (IDs are hypothetical for this example; actual IDs may differ). After a restart, the Shared Audio toggle should appear in the Bluetooth quick‑settings menu. Micorsoft warns that this configuration is unsupported and that you may encounter bugs, so it’s best done on a non‑production machine.
Enterprise IT departments should note that KB5095093 does not install automatically via Windows Server Update Services or Windows Update for Business unless the “preview” ring is explicitly enabled. Therefore, most corporate desktops won’t see these changes until they’re packaged into a future cumulative security update.
The Road Ahead
KB5095093 may not be the announcement many were waiting for, but it’s a tangible step toward a feature that could fundamentally change how we use Windows laptops in shared spaces. Conference rooms where a presenter wirelessly shares audio to a dozen participants, classrooms where a teacher streams a podcast to all students without distributing a dongle—these scenarios inch closer with every low‑level bug fix.
The next milestone to watch is the July 2026 Patch Tuesday, though I wouldn’t bet on Shared Audio lighting up then. Instead, look for another preview update in the weeks following that might graduate the feature from “pilot” to “available for manual enablement in Settings.” A full, out‑of‑the‑box experience likely won’t materialize until Windows 11 25H2 reaches general availability later in 2026.
In the meantime, enthusiasts can enjoy the genuine stability improvements that KB5095093 brings. Audio glitches that have nagged LE Audio adopters for months are finally being ironed out, and the underlying plumbing is now solid enough for Microsoft to start thinking about the user interface. That’s not the splashy headline, but it’s the kind of deep work that separates a polished feature from a tech demo.