Windows 11 Shared Audio Preview: Sync Two Bluetooth LE Sinks

Windows 11’s long-standing one‑output‑only Bluetooth audio world has finally been challenged — but the new Shared audio (preview) is a pragmatic first step, not a cure‑all. Microsoft’s Insider Preview build 26220.7051 surfaces a Quick Settings tile that can stream a single audio feed to two Bluetooth LE Audio devices simultaneously, but the feature is gated by hardware, drivers, and accessory firmware in a way that will frustrate many users who expected “two headphones” to be a simple software toggle.

Background / Overview​

Bluetooth audio on PCs has for years been hamstrung by legacy profile trade‑offs: A2DP for high‑quality one‑way audio, HFP/HSP for two‑way voice but low fidelity. The Bluetooth SIG’s LE Audio family — anchored by the LC3 codec, Isochronous Channels (ISO), and broadcast primitives commonly associated with Auracast — was designed to remove that compromise and enable multi‑sink, low‑power, synchronized audio. Microsoft’s Shared audio builds on these LE Audio primitives and surfaces a simple, user‑facing control in Quick Settings labeled Shared audio (preview). The official Windows Insider blog documents the rollout and the initial compatibility list in detail.
Why this matters now: LE Audio’s efficiency and synchronization primitives make simultaneous multi‑receiver playback practical on battery‑constrained earbuds and on PCs without resorting to ad‑hoc hacks. For the first time on Windows, a native experience wants to do in software what mobile vendors have been shipping through device vendors’ implementations. Early coverage and community reporting corroborate Microsoft’s intent and describe the same technical foundation and rollout strategy.

---

What Shared audio actually does​

At a practical level, Shared audio lets one Windows 11 PC transmit the same audio stream to two paired, LE‑Audio‑capable Bluetooth sinks at once. From the user side the flow is intentionally simple:

• Pair and connect two LE Audio accessories in Settings > Bluetooth & devices.
• Open Quick Settings (taskbar), tap the Shared audio (preview) tile.
• Select the two devices to share to, then press Share.
• Use Stop sharing to end the session.

The OS opens synchronized LE Audio sessions to both receivers using LC3 encoding and isochronous channels so playback remains closely aligned between devices. Microsoft’s documentation and independent reporting both show this user flow and emphasize the Quick Settings UI as the UX surface for Shared audio.

Technical plumbing in brief​

• LC3 codec: Designed to deliver equal or better perceived audio quality at much lower bitrates than legacy SBC. Lower bitrates reduce airtime and help a host serve multiple sinks.
• Isochronous Channels (ISO): Provide timing guarantees and tighter synchronization across multiple receivers, critical to avoid drift when two listeners share a stream.
• Broadcast / Auracast primitives: Allow a source to advertise an audio stream and let receivers subscribe. Microsoft’s preview uses a controlled two‑sink approach rather than an open public broadcast today.

---

Availability and hardware gating: the reality behind the promise​

Microsoft deliberately limited initial availability for Shared audio in Build 26220.7051 to a short list of Copilot+ PCs that already expose the necessary Bluetooth and audio driver stacks. The official compatible list (updated through Microsoft’s Insider blog updates) includes certain Qualcomm Snapdragon‑powered Surface Laptop and Surface Pro models and, as of later Insider updates, the Samsung Galaxy Book4 Edge running Qualcomm silicon. A set of Intel Core Ultra 200‑series Galaxy Book5 models are listed as “coming soon.” Microsoft and multiple outlets confirm these details.
This gating is not arbitrary: Shared audio requires the PC’s Bluetooth controller, OEM firmware, Windows drivers, and accessory firmware to each implement LE Audio primitives correctly. If any layer is missing or out of date, the Shared audio tile won’t appear or the accessory won’t list as a selectable sink. Numerous reports and community threads note this dependency chain as the primary reason many Insiders will not see the feature immediately.

Initial supported PCs (high‑level)​

• Surface Laptop — 13.8" and 15" (Qualcomm Snapdragon X family)
• Surface Pro — 13" (Qualcomm Snapdragon X)
• Surface Laptop for Business / Surface Pro for Business variants with Snapdragon X
• Samsung Galaxy Book4 Edge — added later in the Insider timeline
• Selected Samsung Galaxy Book5 models (Intel Core Ultra 200 series) — coming soon

(Exact SKU support expanded via Insider updates; check the Windows Insider blog for the up‑to‑date compatibility callout when attempting to test.)

Accessory compatibility​

Microsoft lists example LE Audio accessories that should already work — Galaxy Buds2 Pro, Buds3/Buds3 Pro, Sony WH‑1000XM6 and modern LE‑Audio‑capable hearing aids among them — but accessory support depends on the vendor pushing LE Audio firmware updates. Even some headsets advertised as “LE Audio capable” still need companion‑app firmware patches to fully interoperate with Windows’ Shared audio. Community testing repeatedly shows that the missing firmware or a stale driver is the most common blocker.

---

Step‑by‑step: how to test Shared audio (Insider preview)​

If you have a Copilot+ device on Microsoft’s compatibility list and are willing to experiment, here’s the standard path reporters and Microsoft recommend:

• Enroll your PC in the Windows Insider Program (Dev or Beta channel).
• Update Windows to Build 26220.7051 (or later) via Settings > Windows Update.
• Install any OEM Bluetooth and audio driver updates offered in Windows Update (or your vendor’s driver portal).
• Update accessory firmware through the manufacturer’s companion app.
• Pair and connect two LE Audio accessories in Settings > Bluetooth & devices.
• Open Quick Settings, tap the Shared audio (preview) tile, choose two devices, then press Share.
• If a device doesn’t appear, remove and re‑pair it after firmware/driver updates — re‑pairing is often the missing step.

Practical tip: keep a wired fallback for any latency‑sensitive activity (audio editing, live DJing, pro‑audio monitoring). Shared audio in this preview targets consumer scenarios — watching a movie or listening to music — and doesn’t guarantee professional studio‑grade sync or ultra-low latency.

---

Use cases where Shared audio will shine​

Shared audio is a simple convenience that unlocks a number of everyday scenarios:

• Shared viewing on flights or trains where two passengers each want private audio without passing earbuds.
• Classroom or study group settings where two students can listen to the same recording from one laptop.
• Accessibility scenarios where a person using a hearing aid can receive the same stream as someone using regular Bluetooth headphones.
• Quick comparison listening for producers, tutors, or collaborators who want two listeners to judge a clip in sync.

These are the scenarios Microsoft and reporters emphasize; they align with how mobile vendors have positioned Auracast‑style features. For those exact social and accessibility use cases, Shared audio is an immediate win.

---

Strengths: what Microsoft did well​

• Standards‑based approach. Building on LE Audio primitives (LC3, ISO, broadcast) avoids vendor lock‑in and increases the odds of cross‑brand interoperability as firmware and drivers roll out. This is a clear architectural win compared to proprietary one‑off hacks.
• Simple UX. Exposing the capability as a Quick Settings tile hides complexity and keeps the user flow accessible to non‑technical users. The few clicks required match the simplicity users expect from mobile “share audio” workflows.
• Accessibility potential. Direct streaming to hearing aids and to standard headphones at the same time is a valuable accessibility improvement that could simplify assistive listening in many public and private situations.

---

Risks, limitations, and practical caveats​

For all the promise, Shared audio’s immediate value is constrained by several concrete practical issues:

• Ecosystem coordination required. LE Audio’s usefulness depends on aligned updates across silicon vendors, OEMs, driver stacks, and headset firmware. That coordination is gradual; expect many installed PCs and headsets to remain incompatible for months. Multiple community accounts and reporting highlight exactly this coordination problem.
• Fragmentation and inconsistent behavior. Different accessory vendors implement LE Audio features at different times and quality. Reports from early Insiders indicate occasional stutter, device‑specific quirks, and the need to re‑pair devices after firmware updates. Microsoft is intentionally restricting the preview and collecting feedback to tame this fragmentation, but early adopters should temper expectations.
• Latency and synchronization risks for professional use. Even with ISO timing, real‑world buffering, clock drift, and handset firmware buffering strategies can produce perceptible offsets. That makes Shared audio unsuitable for latency‑sensitive professional applications until vendors converge on robust implementations.
• Limited to two receivers in the preview. LE Audio and Auracast support many receivers in broadcast modes, but Microsoft’s initial user experience caps the session at two devices. The choice is conservative and defensible for testing, but users expecting “silent disco” scale broadcasts from a laptop will be disappointed for now.
• Discovery & privacy tradeoffs. LE Audio’s broadcast model can be public or private depending on how vendor UX implements discoverability. Users should be aware of discoverability settings and favor private two‑person sessions for confidential listening.

---

How this compares with mobile implementations​

Apple’s audio sharing for AirPods and many Android phones’ Auracast implementations have already delivered multi‑listener workflows. Microsoft’s Shared audio catches Windows up to that mobile convenience but does so via a standards route rather than vendor‑specific tricks. The tradeoff: greater long‑term interoperability at the cost of a slower, ecosystem‑dependent ramp. Early Windows preview coverage stresses parity with mobile user expectations while noting the PC compatibility complexity is higher because of the wide range of Bluetooth radios and OEM driver practices in the Windows ecosystem.

---

Recommendations — what users, IT teams, and accessory makers should do now​

For curious consumers on Copilot+ hardware:

• Enroll in the Windows Insider Program (Dev/Beta) only if you understand preview instability and are prepared to provide feedback through Feedback Hub.
• Update Windows and vendor drivers via Windows Update, and use the headset vendor’s companion app to install LE Audio firmware updates.
• Re‑pair accessories after firmware updates if a device doesn’t appear in Shared audio.
• Keep a wired or low‑latency wireless fallback for critical work.

For IT and procurement teams:

• Add explicit LE Audio and LC3 support to device procurement requirements where multi‑listener audio or assistive listening is required.
• Pilot Shared audio on a small set of supported Copilot+ hardware before wide deployment; document driver versions and accessory firmware combinations that work.
• Communicate that Shared audio is a consumer/assistive convenience for now, not a replacement for professional audio hardware in controlled environments.

For accessory vendors and OEMs:

• Prioritize firmware updates that expose LE Audio and LC3 support and offer companion‑app workflows that make upgrades simple for end users.
• Test synchronization behavior across a range of Windows Bluetooth radios and driver stacks; interoperability on Windows will determine the feature’s perceived success.
• Provide clear documentation on LE Audio support, firmware build numbers, and known limitations.

---

Developer, security, and privacy considerations​

• Shared audio’s broadcast model can be public or private depending on implementation. Windows’ preview currently exposes a private, paired two‑device experience, which reduces the immediate risk of accidental public streaming. Still, venue operators and IT staff should understand discoverability settings when using Auracast or broadcast style modes in public spaces.
• From a security perspective, LE Audio streams are local RF traffic and do not leave the device by default, reducing the surface for remote interception. However, pairing and join flows should be treated as local‑security operations: keep private sessions private and monitor discoverability settings on shared machines.

---

What to expect next — a realistic timeline​

Microsoft’s staged rollout is intentional: a controlled preview on Copilot+ devices lets engineers, OEMs, and accessory makers iterate on driver and firmware interactions before exposing Shared audio broadly. Industry reporting and community signals suggest a slow rollout over the next several months as OEMs deliver Bluetooth driver updates and accessory vendors publish LE Audio firmware. Expect incremental expansion from Copilot+ machines to additional Windows laptops and tablets as silicon and driver stacks converge; a broader general‑availability window is contingent on that coordination, not on a single Microsoft update.

---

Final assessment: meaningful first step, but patience required​

Shared audio on Windows 11 is a standards‑driven, user‑focused feature that corrects a capability gap many users have tolerated for a decade. Microsoft’s choice to build on LE Audio (LC3, ISO, Auracast primitives) is technically sound and future‑proof; the Quick Settings UX is thoughtful and simple. Yet the real experience will depend on an ecosystem readiness that is not yet universal. Early adopters on gated Copilot+ hardware will enjoy the convenience and accessibility wins immediately, but many users will not see the Shared audio tile, and those who do may face intermittent issues caused by driver or firmware mismatches.
For everyday Windows users the short guidance is clear: update Windows and accessory firmware, try the preview if your hardware is supported, and temper expectations about universal compatibility and professional‑grade latency. For the industry, Shared audio is another strong signal that LE Audio is moving from specification to practical convenience — provided vendors and OEMs coordinate to close the driver and firmware gaps. If they do, the days of “one headphone per PC” will finally be behind us; if not, Shared audio will be a useful but limited preview for early adopters.

---

In the weeks ahead, watch your Windows Update and your accessory vendors’ companion apps: when the right combination of OS build, OEM driver, and headset firmware lines up, the Shared audio tile will appear and let two people listen without cables. Until then, the feature is an important preview that demonstrates where Bluetooth audio on the PC is headed — promising, standards‑based, and very much dependent on the broader ecosystem finishing the work.

---

Source: PCWorld Windows 11 gets multi-device Bluetooth audio, but hold on

 

[ChatGPT]

Microsoft is quietly rolling out a built-in way for Windows 11 PCs to share the same Bluetooth audio feed with another listener, and the implementation — based on Bluetooth LE Audio — is already appearing on a growing list of Copilot+ devices for Windows Insiders and early adopters.

Background / Overview​

Bluetooth audio on PCs has long been hamstrung by legacy trade‑offs between high‑quality playback and simultaneous microphone use. The old Classic Bluetooth profiles split roles across A2DP (good fidelity, one‑way) and HFP/HSP (two‑way voice, lower fidelity), which forced compromises when users wanted both clear voice and music playback. Bluetooth LE Audio (LE Audio) — featuring the LC3 codec and isochronous channels (ISO) — was designed to eliminate that compromise and add modern broadcast-style capabilities. Microsoft’s new Shared audio preview uses these LE Audio primitives to deliver synchronized multi‑sink playback on Windows.
This article breaks down what Microsoft shipped, which PCs and accessories currently support the feature, how to try it, the technical benefits (including super wideband voice and SWB stereo), real‑world limitations, deployment guidance for power users and IT teams, and what to expect next.

---

What Microsoft shipped (the user-facing feature)​

Microsoft surfaced the capability as a Quick Settings tile labeled Shared audio (preview) in recent Windows 11 Insider builds. The UX is intentionally simple: when two compatible Bluetooth LE Audio accessories are paired and connected, you open Quick Settings, select Shared audio (preview), choose two devices, and press Share. A Stop sharing control ends the session. Microsoft is rolling the feature out gradually and gating it at first to a small set of Copilot+ PCs while driver and firmware updates continue to arrive.
Key points about the implementation:

• It requires Bluetooth LE Audio–capable accessories (headphones, earbuds, speakers, or compatible hearing aids).
• Microsoft currently limits simultaneous sinks to two devices in its PC implementation, even though the underlying Auracast family of features supports broader broadcasting. That limitation is a manufacturer choice, not a protocol incapability.
• The initial preview appears in the Windows Insider Dev and Beta channels on compatible Copilot+ hardware running the required builds and drivers.

---

Why LE Audio matters (technical primer)​

Bluetooth LE Audio is not merely an incremental codec update — it changes how devices can use Bluetooth for modern audio scenarios.

• LC3 codec: Improves audio quality at lower bitrates, saving radio airtime and battery life compared with older Bluetooth audio codecs.
• Isochronous Channels (ISO): Provide synchronized timing which allows multiple receivers to play exactly the same audio without perceptible drift.
• Broadcast / Auracast primitives: Allow a single source to broadcast to multiple receivers (Auracast is the Bluetooth SIG branding for the broadcast mode within LE Audio). Microsoft’s Shared audio uses the same standards family, even if Microsoft doesn’t explicitly label the feature “Auracast.”

Beyond multi‑sink playback, LE Audio enables new voice modes. Microsoft has announced super wideband (SWB) support in select Windows 11 PCs, which uses a 32 kHz sampling rate to improve voice clarity for calls and gaming compared with legacy hands‑free profiles. Some devices also support SWB stereo (two audio channels while a mic is active), which preserves immersive stereo media during voice use — something older profiles could not do without a fidelity penalty. Both the PC and the accessory must support LE Audio to realize these benefits.

---

Which Windows PCs support LE Audio today (and which are coming)​

Microsoft is rolling this capability out in stages. As device vendors publish firmware and drivers and Microsoft gates Copilot+ hardware to ensure stability, support will expand.
Reported supported models include recent Surface and Samsung Copilot+ devices (examples cited in the preview rollout notes):

• Surface Laptop — 13.8‑inch and 15‑inch (Qualcomm Snapdragon X)
• Surface Laptop for Business — 13.8 and 15‑inch (Qualcomm Snapdragon X)
• Surface Pro — 12‑inch and 13‑inch models (Qualcomm Snapdragon X variants)
• Samsung Galaxy Book4 Edge — Qualcomm Snapdragon X
  Microsoft also lists additional Samsung Galaxy Book5-series SKUs (with Intel Core Ultra Series 200) as coming soon. These lists reflect the staged nature of the preview and will grow as OEMs publish updates.

Important caveat: hardware families are frequently updated; Microsoft’s compatibility bullets are conservative early on and the practical list of supported PCs will expand as vendors release drivers. If your laptop is not listed today, watch Windows Update and your OEM support channels for updated Bluetooth radio drivers and firmware.

---

How to try Shared audio on your PC — step by step​

If you want to experiment with Shared audio today, follow these steps (high‑level):

• Confirm your PC is eligible for the Copilot+ preview or the specific Insider build that contains Shared audio. You’ll need to be in the Windows Insider Program on the Dev or Beta channel and on a Copilot+ compatible device that the preview targets.
• Update Windows fully via Settings > Windows Update and install the latest Bluetooth and platform updates pushed to the device. Driver and firmware updates from your OEM and accessory manufacturer are often required.
• Pair two Bluetooth LE Audio–capable accessories with the PC and ensure both show as connected. Note: not all devices that advertise “LE Audio” will necessarily interoperate perfectly at first; firmware updates for earbuds/headphones are common.
• Open Quick Settings on the taskbar and look for a tile labeled Shared audio (preview). If the tile appears, select it, pick your two receivers, and press Share. Use Stop sharing to end.

A few practical tips:

• Ensure firmware on wireless earbuds or hearing aids is current — vendor firmware often fixes LE Audio interoperability issues.
• If the Shared audio tile doesn’t appear after updates, your device likely lacks a required OEM driver or isn’t part of the Copilot+ list yet; be patient and check Windows Update again later.

---

Real-life use cases: where this feature shines​

Shared audio isn’t just a demo — it addresses several everyday scenarios:

• Traveling together: Two people can watch the same movie on one laptop while each uses their own wireless headset. No cable splitters, no compromise.
• Accessibility: Hearing‑aid users can receive the same stream as family members using headphones, improving shared content accessibility in public or noisy spaces.
• Collaboration and education: Students and audio professionals can compare playback or listen to the same clip in sync without swapping hardware.
• Quiet public venues: Share audio privately in gyms, libraries, or co‑working spaces without using external speakers.

These are practical, mundane wins — small features that significantly reduce friction in everyday tasks.

---

Limitations, gotchas, and interoperability risks​

No rollout is frictionless, and Bluetooth stacks are notoriously tricky in mixed ecosystems. Be aware of these limitations:

• Hardware and firmware dependency: LE Audio requires coordinated support from the chipset vendor, the OEM’s Bluetooth driver, and accessory firmware. If any link is missing or buggy, the feature will not work reliably. Expect incremental adoption over months rather than instant universal support.
• Two‑device cap (for now): Although Auracast’s broadcast model can scale to many receivers, Microsoft’s current PC implementation limits sharing to two devices. That is an implementation choice and may change in future releases.
• Insider / Copilot+ gating: Initially the feature is limited to Copilot+ hardware and Windows Insider builds. General availability timelines depend on Microsoft and OEM readiness.
• Latency and sync expectations: In ideal cases ISO channels synchronize playback tightly, but real‑world latency and sync depend on accessory firmware and RF conditions. Critical low‑latency uses (pro audio monitoring, live music performance) should still rely on wired or dedicated low‑latency solutions.
• Mic and call behavior: While SWB aims to preserve voice clarity during two‑way audio, behavior during simultaneous microphone use and multi‑sink playback can vary between devices. Verify performance in your target scenario.

If something doesn’t work, the usual troubleshooting checklist applies: update Windows, update the OEM Bluetooth driver, update accessory firmware, unpair and re‑pair, and test with one accessory at a time to isolate issues.

---

For IT teams and power users: rollout advice​

Shared audio is useful, but it introduces a new dependency on wireless firmware and radio drivers — areas IT has limited control over in mixed fleets. Adopt a measured plan:

• Pilot with a small, controlled group before broader deployment. Document fallback workflows (wired headsets, USB audio devices) for users who need deterministic audio.
• Coordinate with OEMs and accessory vendors to get driver and firmware roadmaps. The cadence of vendor updates will determine how quickly the feature becomes practical at scale.
• For public venue or enterprise broadcast scenarios, wait for richer controls (discoverability, access, encryption, and policy settings) before planning any Auracast‑style deployments. Microsoft’s initial PC limit to two sinks means this preview is not yet a venue broadcast solution.

---

The audio fidelity story: SWB and SWB stereo explained​

Microsoft’s earlier LE Audio work introduced super wideband (SWB) for voice, which substantially improves clarity for calls and in-game voice chat by using a 32 kHz sample rate — a significant upgrade over the 8–16 kHz rates typical of older hands‑free profiles. Where supported, SWB can make conversations sound more natural and intelligible.
SWB stereo goes further: it preserves stereo separation while a headset microphone is active, enabling immersive audio while maintaining two‑way voice. This is particularly beneficial for gaming or watching movies where spatial audio matters. Remember: both the PC and the accessory must support SWB/STEREO for you to experience it.

---

Is this Auracast? — understanding the branding and limits​

Auracast is the Bluetooth SIG’s name for LE Audio’s broadcast capability (think one‑to‑many wireless broadcasting). Microsoft’s messaging carefully avoids the Auracast trademark, although the underlying standards are the same family. The practical difference here is Microsoft’s implementation limit: PCs in this preview can share with two receivers rather than open broadcasting to unlimited nearby devices. The Bluetooth SIG confirmed manufacturers can choose to restrict the number of sinks in their implementations, which is what Microsoft has done for these PC builds.
That design decision is defensible for an initial controlled rollout: it reduces complexity for synchronization, power management, and user controls, and keeps the UX simple for Quick Settings. Expect Microsoft and partners to evaluate expanding the sink count or adding Auracast‑style discoverability later.

---

Troubleshooting checklist (quick)​

• Confirm Copilot+ / Insider eligibility for the device and that you’re on the correct Dev/Beta build that includes Shared audio.
• Update Windows via Windows Update, then check your OEM’s support site for Bluetooth radio driver updates.
• Update accessory firmware (earbud/headset vendor apps often push LE Audio fixes).
• Pair and connect each accessory individually, then test both together. If sync or quality issues appear, test each device alone and consult vendor release notes.
• If the Shared audio tile doesn’t appear after all updates, the device likely lacks a required driver or is not yet part of the preview list; wait for OEM/driver updates.

---

What this means for buyers and accessory makers​

For consumers shopping for new headphones or earbuds, look for explicit LE Audio / LC3 / Auracast support in vendor marketing and product spec sheets. Auracast-capable devices will generally be compatible with Microsoft’s Shared audio (subject to firmware/driver interplay), but early adopters should expect firmware updates to improve interoperability over time.
Accessory makers benefit from this shift because LE Audio reduces power consumption and enables richer scenarios (broadcasts, accessibility features for hearing aids, better voice quality). For buyers, the takeaway is simple: if you want to try Shared audio soon, choose accessories that explicitly advertise LE Audio and keep an eye on firmware updates from the vendor.

---

The future outlook — where this is headed​

Shared audio is a pragmatic first step toward broader LE Audio functionality on Windows. The technical foundation (LC3, ISO, Auracast primitives) supports much more ambitious scenarios: open Auracast broadcasts in public venues, synchronized multi‑user listening in classrooms and theaters, and deeper accessibility integrations for hearing devices.
What will determine success:

• Vendor cooperation: chipmakers, OEMs, and accessory vendors must rapidly issue drivers and firmware that interoperate.
• User experience refinements: discoverability, security controls, and management for larger broadcasts will be needed before Auracast‑style broadcasting becomes mainstream on PCs.
• Policy and enterprise controls: enterprises will want policy to control what devices can broadcast or receive audio in public settings. Microsoft and partners will likely add management controls over time.

If these pieces fall into place, the next 6–18 months should be the busiest period for LE Audio adoption on Windows laptops and accessories. Expect the feature set to expand from a convenient two‑device sharing preview into a richer, more flexible broadcast and multi‑sink ecosystem.

---

Final assessment: practical value now, broader promise later​

Shared audio in Windows 11 is the kind of practical, user‑focused improvement that matters every day. It removes friction for common scenarios — two people watching the same video, accessible listening for hearing aid users, quick audio sharing in study groups — and packages it in a one‑tap Quick Settings control when the hardware supports it. The technical foundation is solid: LE Audio’s LC3 codec and ISO channels materially enable synchronized, power‑efficient multi‑sink playback.
However, the feature’s real‑world value today depends heavily on the broader ecosystem of drivers and firmware updates from OEMs and accessory vendors. Microsoft’s cautious Copilot+ gating and the two‑device limit are sensible for an initial rollout, but they mean patience is required for broad adoption. IT teams should pilot before deploy, accessory makers should prioritize firmware, and buyers should prefer explicitly LE Audio‑capable products if they want to experiment now.
For readers who want to try it: join the Windows Insider Dev or Beta channel on a supported Copilot+ PC, update Windows and your accessory firmware, and look for the Shared audio (preview) tile in Quick Settings. If your device or earbuds aren’t supported yet, keep an eye on Windows Update and OEM driver pages — the LE Audio landscape is changing quickly, and broader compatibility is coming.
Conclusion: Shared audio is a welcome, standards‑based step forward for wireless audio on Windows. It won’t instantly replace wired workflows for pro or latency‑sensitive tasks, but as the ecosystem catches up, it will remove a lot of everyday friction and open doors to new listening experiences.

---

Source: ZDNET More Windows 11 PCs are getting this big Bluetooth update - what you need to try it