Windows 11 Shared Audio Preview Streams Audio to Two Bluetooth LE Devices

Microsoft is quietly rolling out a long‑requested convenience: a built‑in Shared audio (preview) for Windows 11 that can stream the same audio feed to two Bluetooth devices at once, leveraging the new Bluetooth Low Energy (LE Audio) stack and arriving first for Windows Insiders in Windows 11 Insider Preview Build 26220.7051.

Background / Overview​

For years, sharing private audio from a PC required awkward workarounds — wired splitters, third‑party apps, or carrier‑grade dongles — because the legacy Bluetooth Classic profiles were not designed for efficient multi‑sink media distribution. The Bluetooth Special Interest Group’s LE Audio specification (LC3 codec, isochronous channels, and Auracast‑style broadcast primitives) changes that by enabling efficient, synchronized one‑to‑many audio streams. Microsoft’s Shared audio is a pragmatic, Windows‑focused implementation of those standards: it exposes a simple Quick Settings control that lets one PC transmit a synchronized audio stream to two compatible Bluetooth LE Audio accessories at the same time. This is a preview feature deployed to Windows Insiders (Dev and Beta channels) and intentionally hardware‑gated: initial availability is restricted to a list of Copilot+ PCs where Bluetooth radios, firmware, and vendor drivers already expose the necessary LE Audio primitives. The official rollout details and supported models are documented in the Windows Insider announcement.

---

Why this matters: the problem LE Audio solves​

Bluetooth on PCs historically forced a trade‑off:

• A2DP gave high‑quality one‑way stereo playback but no reliable mic support.
• HFP/HSP gave mic support but dropped playback quality and often forced mono.

That meant when you wanted to talk (game chat, calls) your music or game audio degraded. LE Audio was designed to end that compromise through several improvements:

• LC3 codec — better perceived audio quality at far lower bitrates than legacy SBC, enabling higher fidelity and less radio time.
• Isochronous Channels (ISO) — timing primitives that provide synchronized packet delivery for low‑jitter multi‑sink playback.
• TMAP (Telephony and Media Audio Profile) and multi‑stream — allow media and telephony streams to coexist without downgrading the media path.

Microsoft’s recent Windows work (including “super wideband stereo”) integrates these plumbing changes into the OS, letting headsets keep stereo media while also supporting higher‑quality mic streams. Shared audio leverages the same foundation to duplicate an audio feed to multiple receivers without the brittle hacks previously required.

---

What Microsoft shipped in Build 26220.7051​

The core user‑facing elements of the preview are straightforward:

• A Shared audio (preview) tile appears in Quick Settings once the OS and vendor drivers expose the capability.
• Users pair and connect two LE Audio‑capable accessories (headphones, earbuds, speakers, or compatible hearing aids).
• From Quick Settings, select the two connected accessories and press Share to begin streaming the same audio to both devices in sync.
• A Stop sharing control terminates the session.

Microsoft phrases the experience as social and accessibility driven (students studying together, families on flights, hearing‑aid support) while noting that initial availability is limited to specific Copilot+ PC SKUs.

---

Supported devices and compatibility​

Microsoft’s preview is intentionally conservative. Compatibility breaks down into two sides: the host PC and the audio accessories.

• Host requirements (initial list — Copilot+ PCs):
• Surface Laptop 13.8‑inch and 15‑inch (Qualcomm Snapdragon X)
• Surface Laptop for Business (13.8 and 15‑inch)
• Surface Pro 13‑inch and Surface Pro for Business 13‑inch (Qualcomm Snapdragon X)
• A “coming soon” list includes several Galaxy Book5 variants and additional Surface SKUs; OEM driver updates will enable more hosts over time.
• Accessory requirements:
• The accessory must support Bluetooth LE Audio (LC3, ISO channels, and relevant profiles).
• Microsoft lists example devices that are already LE Audio capable (or have firmware updates available): Samsung Galaxy Buds2 Pro, Buds3, Buds3 Pro, Sony WH‑1000XM6, and recent LE Audio‑capable hearing aids from vendors such as ReSound and Beltone. This list is illustrative, not exhaustive.

Important caveat: LE Audio support is not guaranteed purely by Bluetooth version numbers. A Bluetooth adapter or chipset may support LE Audio in hardware, but the feature still depends on firmware and vendor drivers exposing the LE Audio stack to Windows. In practice, that means Windows Update and OEM companion apps are likely to deliver the enabling drivers and accessory firmware that make Shared audio appear in Quick Settings.

---

How Shared audio works (technical primer)​

At a high level, Shared audio uses LE Audio’s broadcast and multi‑stream primitives to create a synchronized stream that multiple receivers can consume. The key technical pieces:

• The PC encodes the audio into LC3 frames. LC3 provides better perceived fidelity at lower bitrates, reducing radio airtime and battery drain.
• The host opens Isochronous Channels (ISO) and transmits packets with timing guarantees so receivers play audio in tight sync — crucial to avoid audible drift between listeners.
• Microsoft currently constrains the preview to two simultaneous sinks, rather than enabling an unrestricted Auracast broadcast, to manage complexity and driver interoperability as the ecosystem ramps up.

Why Microsoft chose a two‑sink limit in preview: synchronization, buffering, and vendor differences across headsets make broader, unlimited broadcasts riskier for a first release. A controlled two‑sink surface gives Microsoft and OEM partners a manageable testbed for real‑world behavior and feedback collection.

---

Step‑by‑step: how to try Shared audio (Insiders)​

• Confirm your PC is a supported Copilot+ model on Microsoft’s compatibility list.
• Enroll the device in the Windows Insider Program and choose the Dev or Beta channel.
• Update Windows to Build 26220.7051 (or later) and accept OEM driver updates via Settings > Windows Update.
• Update firmware on your Bluetooth accessories using the manufacturer’s companion app (highly recommended). Many vendors ship LE Audio features by firmware update.
• Pair and connect two LE Audio‑capable devices from Settings > Bluetooth & devices. Verify both show as connected.
• Open Quick Settings, tap Shared audio (preview), select the two accessories, and press Share to begin streaming. Use Stop sharing to end the session.

Troubleshooting tips:

• If an accessory is paired and connected but doesn’t appear in the Shared audio picker, remove and re‑pair it after confirming firmware/driver updates.
• Ensure the OEM driver updates have been applied; the Quick Settings tile only shows up when the drivers expose the capability to Windows.

---

Practical use cases​

• Shared entertainment — two people can watch a movie or stream on a laptop without disturbing others or swapping earbuds.
• Study groups and co‑working — share a lecture, podcast, or language lesson with a partner in near‑perfect sync.
• Travel — private in‑flight listening for two users using their own earbuds.
• Accessibility — direct streaming to LE Audio‑capable hearing aids alongside a companion’s headphones enables shared listening without extra hardware.
• Small venue audio — in time, Auracast‑style broadcasts could power localized audio streams for exhibitions or airport announcements; Shared audio’s early two‑sink model is a stepping stone.

---

Strengths: what Microsoft got right​

• Standards‑based approach — building on LE Audio (LC3, ISO channels, broadcast primitives) maximizes interoperability potential across vendors and avoids proprietary lock‑in.
• User‑friendly UI — surfacing the feature in Quick Settings keeps the workflow simple and discoverable for average users.
• Conservative rollout — gating to Copilot+ PCs and limiting to two sinks during preview reduces the blast radius for driver and firmware bugs, giving partners time to align updates.
• Accessibility focus — explicit mention and support for LE Audio hearing aids is an important inclusion for assistive listening scenarios.

---

Risks, limitations, and areas to watch​

• Ecosystem readiness — the biggest limitation is not Microsoft’s software but the broader ecosystem. Many existing headsets do not support LE Audio or require firmware updates; PC Bluetooth radios also vary by chipset and driver support. Expect uneven availability for months.
• Vendor fragmentation — mixed‑brand setups may exhibit buffering discrepancies or codec fallbacks that harm sync or quality. This is a real risk until vendors converge on stable firmware behavior.
• Latency and synchronization — while LE Audio ISO channels provide timing guarantees, practical latency depends on accessory buffering, Bluetooth radio load, and environmental RF conditions. For professional audio production or tight competitive gaming, wired or dedicated multi‑output workflows may still be necessary. Do not assume Shared audio will meet pro‑audio latency budgets.
• Battery and power claims — LE Audio’s LC3 codec is more efficient in theory, but real battery life gains vary by device and usage pattern; any claim of "better battery life" should be treated as conditional on accessory implementation and the chosen codec bitrate. Flag these as vendor‑dependent.
• Security and privacy — broadcast‑style audio introduces new surfaces (Auracast-like models) where ambiguous discovery settings could expose audio streams to nearby devices. Microsoft’s preview limits sharing to paired devices, but broader broadcast scenarios will need clear discovery controls and consent mechanisms to prevent accidental exposure.

---

How this compares to mobile ecosystems​

Apple has long offered a tightly integrated audio‑sharing workflow for AirPods and Beats — a product advantage born of full vertical control over hardware and firmware. Android vendors (Google, Samsung) began adopting Auracast on phones, and some manufacturers already expose LE Audio broadcast UIs. Microsoft’s Shared audio brings parity to Windows in a standards‑forward way, but because Windows runs on many OEM configurations, the PC experience will necessarily be more fragmented in the near term. The value proposition for Windows is breadth: when the ecosystem aligns, the same open LE Audio stack can support many accessory brands and PC vendors, not just a single proprietary ecosystem.

---

Enterprise and IT considerations​

• Procurement teams should include LE Audio and driver update management in RFPs and evaluation criteria for new mobile devices and laptops.
• IT admins must treat the preview as a pilot. Do not replace wired workflows where determinism and low latency are required (e.g., audio production, contact centers).
• For privacy‑sensitive deployments, audit the Quick Settings exposure and telemetry around any broadcast features — group policies or Intune controls may be required if broad rollout begins. Microsoft’s gradual toggle model suggests administrators will retain control over feature exposure.

---

Recommendations for users and early adopters​

• If you have a supported Copilot+ PC and LE Audio‑capable accessories, enroll in the Windows Insider Program (Dev/Beta) to test Shared audio and provide feedback in Feedback Hub (Bluetooth → Audio quality, glitches, stuttering).
• Update accessory firmware using the vendor’s app before pairing with Windows. Firmware is often the missing piece for LE Audio support.
• Test mixed‑brand pairings early to understand practical behavior: buffering, dropouts, and codec fallbacks may vary.
• Keep a wired fallback for mission‑critical sessions and for tasks that demand low latency or deterministic audio.

---

What Microsoft, OEMs and accessory makers should do next​

• Publish clear compatibility matrices and firmware update guides for consumers, so buyers can understand whether their existing headphones can be upgraded to LE Audio.
• Provide firmware and vendor driver updates via Windows Update or OEM companion tools to minimize friction for deployment.
• Expose robust user consent and discovery UI for any future Auracast‑style public broadcasts to prevent accidental or unauthorized listening.
• Expand the preview beyond Copilot+ gating once driver and firmware ecosystems stabilize, accompanied by telemetry‑backed performance targets (sync accuracy, re‑connect behavior, battery impact).

---

Final assessment: a practical, standards‑first step​

Shared audio (preview) is not a headline‑grabbing revolution; it’s a practical and standards‑based advance that fixes a long‑standing user pain in a way that scales. By building on Bluetooth LE Audio and exposing a simple Quick Settings UX, Microsoft has given Windows a viable path to match mobile platforms’ multi‑sink conveniences — but the real win depends on an ecosystem alignment that includes PC radios, OEM drivers, and accessory firmware.
The preview’s strengths are clear: standards compliance, user‑friendly discovery, and a cautious rollout strategy that minimizes immediate breakage. The risks are equally real: fragmentation, variable latency, and vendor dependence mean many users will have to wait or update hardware before enjoying the experience seamlessly.
For users: test the preview if you can, update firmware, and temper expectations for universal compatibility today. For the industry: Shared audio is a signal that LE Audio is maturing on the PC, and coordinated firmware/driver updates in the coming months will determine whether this becomes a ubiquitous convenience or a niche novelty for early adopters.

---

Microsoft’s Shared audio (preview) shows how a standards‑driven feature can translate into everyday convenience on the desktop — provided the hardware and firmware ecosystems catch up. The immediate experience will be patchy for many, but for those on supported Copilot+ PCs with LE Audio accessories, the feature promises to finally make shared, private listening on Windows simple and reliable.

---

Source: en.bd-pratidin.com Windows 11 to let you stream audio to two Bluetooth devices at once|50042|News24 TV

 

[ChatGPT]

Microsoft has begun testing a more visible Copilot experience in Windows 11 by placing an Ask Copilot entry directly on the taskbar — an opt‑in replacement for the familiar search box that surfaces local files, apps, and conversational AI suggestions while offering one‑click access to Copilot Vision and Copilot Voice. Microsoft describes the change as an effort to make Copilot “a natural part of how you use your PC,” but emphasizes the feature is disabled by default and uses existing Windows search APIs so Copilot does not gain special access to files that Windows Search couldn’t already see.

Background​

What Microsoft announced and where it appears​

In the Windows Insider Preview for the Dev and Beta channels (Build 26220.7051), Microsoft introduced an Ask Copilot box that can replace the current taskbar search field. The feature is being rolled out gradually to Insiders, and users who want to try it must explicitly enable it in Settings > Personalization > Taskbar > Ask Copilot. Microsoft calls it an opt‑in experience and notes that it complements — rather than silently replaces — the existing Windows Search behavior. Third‑party coverage shows the new Ask Copilot box also includes inline icons that launch Copilot Vision (for screen‑aware, session‑scoped visual assistance) and Copilot Voice (wake‑word and press‑to‑talk voice input), which are presented as quick actions inside the taskbar control. Early hands‑on reports indicate the box behaves like a hybrid search/chat field: it returns instant local results as you type and can escalate to a conversational Copilot session when you ask for more context or help.

Why this matters now​

Microsoft is pushing Copilot deeply across Windows and Microsoft 365 as part of a strategy to make AI a first‑class interaction model on PCs. Surfacing Ask Copilot in the taskbar is a visible step: the taskbar is prime real‑estate and is where users naturally go to search, launch apps, and find files. The design explicitly attempts to reduce friction by placing AI capabilities in a familiar location. Microsoft frames this as a productivity win while insisting the feature respects existing privacy boundaries and administrative controls.

---

How Ask Copilot works — the technical and UX essentials​

Hybrid search + chat​

Ask Copilot is a hybrid interface. As you type, it uses Windows Search indexing and APIs to show local matches — apps, files, and settings — in the same way the old search box did. When the input becomes a natural‑language prompt that calls for generative help (for example, “Summarize this document” or “Show me last month’s invoices”), the UI can transition into a Copilot chat session and surface generated suggestions, follow‑ups, or actions. This is meant to reduce context switching by keeping discovery and conversational assistance in one place.

One‑click Vision and Voice​

Two small icons in the Ask Copilot control give quick access to:

• Copilot Vision: a session‑scoped screen‑sharing capability that can OCR a selected window or region, summarize text, extract tables, or help with UI walkthroughs. Vision is explicitly opt‑in per session.
• Copilot Voice: voice input with a local wake‑word “spotter” that triggers transcription and further cloud‑based processing unless the device is a Copilot+ PC with on‑device NPU inference. The architecture is hybrid: small, local detection then cloud inference by default.

Privacy boundary Microsoft stresses​

Microsoft states Ask Copilot “uses existing Windows APIs to return apps, files, and settings — just like Windows Search — and does not grant Copilot access to your personal content.” The company provides in‑app privacy controls for things like Vision and file access, and the Ask Copilot toggle is off by default for Insiders. That privacy position is central to Microsoft’s messaging as it pushes more AI into the OS.

---

Immediate user impact and control options​

Opt‑in by default — how to enable/disable​

Ask Copilot is disabled by default. To try it you must enable it manually: Settings > Personalization > Taskbar > Ask Copilot. If you turn it on, the Search box is replaced by the Ask Copilot entry; turning it off restores the previous search affordance. Microsoft also notes a Copilot auto‑start option in the Copilot app settings for sign‑in behavior.

Quick ways to hide or stop Copilot​

For users who do not want Copilot present, Microsoft and community guidance point to several options — from safe and reversible to administrative blocking:

• Toggle off Ask Copilot in Taskbar settings (fast, reversible).
• Disable Copilot taskbar button or hide the taskbar item — this removes the visual affordance but may not stop every invocation path (Win+C or a Copilot hardware key may still launch it on some builds).
• Uninstall the Copilot app where available (some Windows editions and configurations expose Copilot as an uninstallable app).
• For enterprise control: use Group Policy / MDM policies (for example, TurnOffWindowsCopilot or the corresponding MDM setting) and AppLocker/WDAC to block installation or execution at scale. Community posts and guides show admins pairing multiple controls for robust enforcement.

These choices reflect Microsoft’s multi‑path delivery model: Copilot can be delivered as a Store app, a separable package, or as deeper OS integration, and that packaging affects what removal controls are most effective.

---

Strengths: what Ask Copilot brings to Windows 11​

1) Reduced friction and better discoverability​

Placing a hybrid search/chat field on the taskbar reduces the number of places a user must go to find help. For routine queries that mix local discovery and generative assistance — e.g., “find my expenses and summarize them into a table” — Ask Copilot can shorten task flows and reduce context switching. That can be a real productivity gain for people who adopt conversational AI in their workflows.

2) Unified interface for multimodal inputs​

Integrating Vision and Voice into the same control introduces multimodal input patterns on the desktop: type, speak, or share a window and get immediate help. For accessibility and power‑user scenarios, this is a significant step toward making PCs more flexible interaction platforms. The local wake‑word spotter and session‑bound Vision model are design choices that balance convenience with user control.

3) Administrative visibility and opt‑ins​

Because the feature is opt‑in in the Insider preview and Microsoft documents management policies, IT administrators have routes to control the feature across fleets. That reduces the chance of surprise in managed environments compared with stealthy mandatory changes. Community guides also provide practical remediation steps for admins.

---

Risks and concerns: privacy, performance, and UX friction​

Privacy nuance — promises vs. perception​

Microsoft’s statement that Ask Copilot “uses existing Windows APIs” and “does not grant Copilot access to your personal content” is technically meaningful: local indexing and search APIs already surface local items. However, perception and nuance matter. Many users will interpret a visible AI box that can “see” and “hear” as a deeper access vector regardless of how Microsoft implements it. Copilot Vision’s session sharing model and explicit consent reduce continuous‑scanning fears, but the presence of vision and voice affordances on the taskbar raises privacy questions that require clear UI signals and accessible permissions controls. Reported early hands‑on experiences show Microsoft is aware of these concerns and is positioning controls and disclosures accordingly — but the opt‑in vs. opt‑out UX will determine how users interpret Microsoft’s privacy claims.

Performance and infrastructure cost​

If Ask Copilot becomes widely used, the compute burden of conversational queries, vision OCR, and voice transcription could be significant. Microsoft’s staged rollout via the Insider program and server‑side gating suggests the company is monitoring scale and performance. For users with limited bandwidth or privacy requirements that preclude cloud inference, the default cloud path (unless on Copilot+ hardware) may be a practical blocker for adoption. Early commentary also flags that some Copilot features are unavailable or limited on non‑Copilot+ hardware in previews.

UX clutter and discoverability tension​

Designing the taskbar to promote Copilot risks clutter and prominence bias — the idea that users will assume default affordances are required or preferable. Microsoft’s approach to make Ask Copilot opt‑in helps, but repeated UI nudges (such as easy access to Vision and Voice) create incentives to try the feature. Some users and administrators will prefer a minimal desktop; others will embrace the extra capability. Managing that split without creating friction (for example, removing the old Show Desktop button or changing taskbar layout unexpectedly) is a tricky design problem Microsoft will have to continue to refine. Community threads already show frustration when taskbar elements change unexpectedly.

---

Enterprise considerations​

Policy controls and hardening​

For IT teams, the practical starting points are the supported Group Policy / MDM settings and enterprise controls like AppLocker or Windows Defender Application Control (WDAC) to prevent installation or execution. Microsoft documents TurnOffWindowsCopilot and related administrative policies; however community testing highlights that Insider or preview delivery models occasionally introduce behaviors not covered by older policies, so robust enforcement may require combining the documented policy with app control or tenant settings and monitoring for reprovisioning. Test controls on the exact Windows build used in production before deploying broadly.

User education and consent​

Where Vision or Voice are enabled, enterprises must consider consent, logging, and compliance; session‑scoped Vision sharing and local spotters help mitigate persistent surveillance concerns, but formal policy for voice capture and screenshots is necessary in regulated environments. Guidance and training to make sure employees understand what is shared and when will be required for compliance with corporate data protection rules.

---

Practical recommendations for end users​

• If you want to try Ask Copilot: enable it via Settings > Personalization > Taskbar > Ask Copilot and review Copilot app privacy toggles (Vision, file search, auto‑start) before use.
• If you don’t want Copilot visible: toggle Ask Copilot off in Taskbar settings — that restores the old Search control. For more persistent blocking, uninstall the app where allowed or use the Copilot-related Group Policy/registry setting.
• If you manage fleets: test TurnOffWindowsCopilot and complementary AppLocker/MDM rules on a sample of builds, and document reprovision behaviors after feature updates to avoid surprises.

---

What to watch next​

• How Microsoft evolves the default behavior outside Insider channels: Ask Copilot is opt‑in for Insiders now, but the company may change defaults or packaging in future public releases. Track official Windows update notes.
• Copilot Vision and Voice availability and limitations by region and device class: these features are being rolled out with gating and Copilot+ hardware distinctions; expect staged availability.
• Administrative policy coverage: Microsoft’s policies will need to keep pace with new delivery models; admins should monitor official docs and test against the exact builds they operate. Community guides will continue to document practical enforcement strategies.

---

Assessment: a measured final verdict​

Ask Copilot on the taskbar is a logical product move for Microsoft’s vision of AI‑first computing: it places discovery, conversational assistance, and multimodal inputs where users already search and launch work. For users who embrace AI helpers, the tighter integration reduces friction and can save time on complex, multi‑step tasks. Microsoft’s explicit opt‑in stance during preview, the use of existing Windows Search APIs, and session‑scoped Vision and local wake‑word spotters are sensible engineering and privacy choices that mitigate some legitimate concerns. That said, meaningful risks remain. Perception and clarity around privacy will drive acceptance more than the underlying technical constraints; users will judge based on what they see — a visible AI box with “Vision” and “Voice” buttons — not on API semantics. Enterprises must be prepared for evolving delivery models that may temporarily outpace existing management policies. Lastly, Microsoft’s product team must carefully manage defaults and UI nudges to avoid alienating users who prefer a simpler, less AI‑centric desktop. Early community and press coverage already shows both enthusiasm and resistance, a split that will shape how broadly Ask Copilot is accepted.

---

Microsoft’s Ask Copilot is a clear signal that the company expects AI to be a first‑class part of the Windows experience. For now it’s opt‑in, controllable, and explicitly built on existing OS search plumbing — but the long‑term question is less about whether the feature works and more about how Microsoft balances discoverability with user choice, transparency, and enterprise control as Copilot spreads across the platform.

---

Source: TechRadar https://www.techradar.com/computing...ws-11s-taskbar-but-only-if-you-want-ai-there/