Windows 11 FSE Arrives on MSI Claw with Full Screen Experience

Microsoft has shipped a tangible step toward making Windows behave like a handheld console: Windows 11 Insider Preview Build 26220.7051 (KB5067115) brings a full‑screen, controller‑first “Full Screen Experience” (FSE) to a broader set of devices—most notably MSI’s Claw family—while also surfacing an opt‑in Copilot taskbar experience and a handful of device‑gated experiments.

Background / Overview​

Microsoft’s Full Screen Experience (commonly shortened to FSE) first appeared as the out‑of‑box launcher on the ASUS ROG Xbox Ally models. It is a session posture layered atop Windows 11 that elevates a chosen “home app” (typically the Xbox PC app) into a full‑screen, controller‑friendly shell and intentionally defers or suspends many desktop visual elements and background processes while active. That design is intended to give handheld Windows PCs a console‑like user experience without forking the operating system. The recent cumulative preview—delivered as Windows 11 Insider Preview Build 26220.7051 (KB5067115)—packages the FSE expansion alongside an opt‑in Ask Copilot taskbar pill and a preview of Shared audio based on Bluetooth LE Audio. Microsoft is using Controlled Feature Rollouts (CFR): the binaries are broadly distributed through the Insider channels, but feature visibility is gated by OEM entitlements, account telemetry, and server‑side flags. That means the presence of FSE on any single device depends on both the installed build and whether Microsoft/OEM enable it for that hardware.

---

What the Full Screen Experience (FSE) actually is​

A session posture, not a new OS​

FSE is a layered Windows shell, not a separate operating system. When enabled, Windows runs the chosen home app as the device’s primary interface while preserving the full Windows kernel, drivers, and compatibility underneath. The practical effect is a simplified, gamepad‑first UX and fewer background distractions—not kernel or GPU driver modifications.

Key behaviors and visible changes​

• A full‑screen, controller‑focused home launcher (the Xbox PC app by default) that aggregates Game Pass, Xbox purchases, and many locally installed PC titles into a unified grid.
• Controller‑first navigation improvements: Game Bar and Task View behaviors are adapted for thumb reachability, and common system actions are mapped for quick controller access.
• Resource trimming: on entry to FSE, Windows defers certain desktop subsystems and non‑essential startup tasks to free memory and reduce idle CPU wakeups, aiming to smooth frame delivery on thermally constrained handheld APUs.

What FSE does NOT do​

• It does not change kernel scheduling or GPU driver models, and it does not bypass anti‑cheat or DRM requirements. Games still need their required runtimes and anti‑cheat drivers to run. Think of FSE as a different entry point and session posture rather than an isolated OS.

---

What’s in Build 26220.7051 (KB5067115)​

Headline additions​

• Full Screen Experience (FSE) preview expanded beyond ASUS ROG Ally devices to include MSI Claw models; OEM rollouts to additional handhelds are planned.
• Ask Copilot taskbar pill — an opt‑in Copilot entry that mixes local Windows Search results with Copilot conversational responses and includes quick Vision and Voice entry points.
• Shared audio (preview) leveraging Bluetooth LE Audio to stream to multiple compatible accessories on supported Copilot+ systems.

These features are deliberately staged; installing the build does not guarantee immediate access to each item unless your device and account have been entitled by Microsoft and the OEM.

---

How to enable and access FSE on a supported device​

Step‑by‑step (official path)​

• Enroll the device in the Windows Insider Program on a channel that contains the 25H2 preview pieces (Dev or Beta when this matched preview was distributed).
• Update Windows to the Insider preview cumulative that contains the FSE binaries (e.g., Build 26220.7051 / KB5067115).
• Open Settings → Gaming → Full screen experience. Select Xbox (or another available home app) as your home app and optionally toggle Enter full screen experience on startup.
• Use Task View, Game Bar (Win+G), or the Xbox button (on hardware that exposes it) to enter/exit the FSE session.

Community methods (unsupported and risky)​

Enthusiast guides have circulated registry edits and ViVeTool feature‑flag unlocks that can forcibly expose FSE on otherwise unsupported devices. These methods are unsupported, can break system behavior, complicate warranty support, and are not recommended for production systems. Proceed only if you are comfortable with recovery‑level troubleshooting.

---

Hands‑on performance expectations and what testing shows​

Runtime resource changes​

Microsoft engineers and early hands‑on testers report that FSE can free usable memory and reduce background CPU wakeups, which is the primary mechanism for delivering steadier performance on thermally constrained handhelds. Community testing commonly reports roughly 1–2 GB of reclaimable RAM on compact builds, though results vary widely by installed apps, drivers, and system configuration. Treat any single number as workload‑dependent rather than guaranteed.

Real‑world framerate and battery effects​

• Synthetic benchmarks and some gameplay tests show measurable but modest FPS uplifts in certain titles and scenarios—more so where background OS noise was previously a limiting factor. Early hands‑on reports documented double‑digit percentage improvements in specific synthetic tests and single‑digit to low‑double‑digit gains in demanding games. These uplifts are not universal and can be offset by driver immaturity or overlay conflicts.
• Battery life effects are nuanced: deferring background tasks can reduce idle CPU wakeups and improve battery efficiency during gaming, but actual battery behavior depends heavily on power profile, display refresh rate, and thermal throttling characteristics of the SoC.

Why gains vary​

The benefits appear where desktop subsystems and auto‑start agents were previously consuming enough memory or waking the CPU frequently. On well‑tuned desktop gaming PCs with large RAM pools and mature drivers, the difference may be negligible. On small handhelds with constrained RAM and frequent background activity, the resource trimming can matter more.

---

Ask Copilot: what changed in the taskbar​

The build introduces an opt‑in Ask Copilot taskbar element that replaces or augments the traditional Search box with a compact, chat‑first surface. It blends instant local hits (apps, files, settings surfaced via existing Windows Search APIs) with Copilot’s generative responses, and exposes icons for Copilot Vision (attach/share a region or window) and Copilot Voice (press‑to‑talk or wake‑word where available). The control lives at Settings → Personalization → Taskbar → Ask Copilot. Key points for users and IT:

• It is permissioned—Copilot does not automatically access or upload files without explicit sharing or consent within the session.
• The feature is opt‑in and controlled by server flags; enabling the toggle in Settings does not guarantee immediate availability unless entitlement conditions are met.

---

OEM rollout, device list, and timing​

Microsoft’s rollout is staged and OEM‑gated. The initial FSE shipping devices were the ASUS ROG Xbox Ally and ROG Xbox Ally X. Build 26220.7051 introduced preview availability for MSI Claw models and Microsoft indicated additional OEM handhelds will be enabled in the coming months; outlets have reported Lenovo and other vendors as likely next steps. Rollout timing is inherently phased and can vary by region and account. Practical implications:

• Identical machines may show different behaviors depending on whether Microsoft/OEM granted entitlement on that device.
• OEM images that ship with FSE preconfigured will offer the smoothest experience because firmware, controller mappings, and OEM utilities are tuned to the session posture. Hand‑ported or community‑enabled installs will likely be rougher.

---

Risks, caveats, and troubleshooting​

Compatibility and anti‑cheat​

FSE does not bypass anti‑cheat or DRM. Games that require kernel‑level anti‑cheat drivers will still load those drivers, and any incompatibility between anti‑cheat systems and the FSE session posture could prevent certain titles from running. Gamers should validate important titles before adopting FSE for daily play.

Overlay, firmware and driver interactions​

Many early issues reported by testers stem from overlay conflicts (OEM utilities, recorder overlays, or third‑party launcher overlays) and immature drivers. Updating firmware, OEM utilities (for example, MSI Center), and the Xbox PC app preview often resolves transient issues. Where problems persist, reverting to the desktop session or disabling FSE is the supported recovery path.

Stability and gating volatility​

Because FSE is being phased via CFR, users may see the toggle appear and then disappear as Microsoft adjusts entitlements or experiments with AB testing. Community registry edits that force exposure can result in a disappearing toggle or inconsistent behavior after subsequent updates.

Privacy and enterprise concerns with Ask Copilot​

Although Microsoft emphasizes that Copilot’s local search integration is permissioned, the new Vision/Voice sharing surfaces expand potential data flows. Enterprises should treat the Copilot attachments, screen shares, and session uploads as new exfiltration vectors until Data Loss Prevention (DLP) and telemetry policies have been validated in test environments. IT teams should pilot the feature in isolated test labs and update DLP rulesets accordingly.

---

Recommended test plan for power users and IT teams​

• Back up the device and create a recovery image before experimenting with Insider bits or registry workarounds.
• Enroll a test device in the Windows Insider channel that contains the desired preview build. Update to Build 26220.7051 (KB5067115).
• Update the Xbox PC app to the latest preview and ensure OEM utilities and drivers (MSI Center, firmware, GPU drivers) are current.
• Enable FSE via Settings → Gaming → Full screen experience on a test device and run a controlled set of benchmarks and gameplay sessions to compare memory usage, idle CPU wakeups, and FPS consistency. Record battery drain curves during identical scenarios.
• Test affected titles that use kernel anti‑cheat drivers to confirm compatibility and observe whether overlays or capture tools function as expected.
• For enterprise pilots, enable Ask Copilot only in a secured test tenant and validate DLP telemetry, sharing alerts, and user consent workflows before any wider rollout.

---

Strategic implications: why Microsoft is doing this​

• For users, FSE reduces friction and creates a console‑like, one‑click path to games—especially valuable on small screens where juggling multiple launchers is painful.
• For OEMs, FSE offers a standardized handheld UX without the need to build a custom shell, allowing hardware vendors to differentiate on tuning and firmware while leveraging a Microsoft‑approved launcher.
• For Microsoft, expanding FSE helps push Xbox ecosystem visibility (Game Pass, Xbox app) into the handheld market and positions Windows as a more credible competitor to curated handheld platforms like SteamOS.

---

Strengths, weaknesses, and the road ahead​

Notable strengths​

• Practical engineering trade‑off: FSE preserves Windows compatibility while removing many desktop distractions—an achievable path to console‑like behavior without fragmenting the platform.
• Low barrier for OEM adoption: Because FSE is a session posture, OEMs can ship it preconfigured (as ASUS did) and tune firmware to match the experience.

Potential risks and limitations​

• Fragmented early experience: Controlled feature gating and device entitlements mean rollout will be uneven; early adopters should expect rough edges.
• Dependency on driver and firmware quality: Actual user experience depends heavily on coordinated updates from GPU, controller, and headset vendors.
• Privacy and enterprise governance: New Copilot sharing surfaces require careful DLP review before enterprise rollout.

What to watch next​

• Broader OEM enablement (Lenovo, other handhelds) and official guidance on supported device lists.
• Maturity of anti‑cheat and overlay compatibility on non‑ROG hardware.
• How Copilot Vision/Voice consent flows are audited and logged for enterprise compliance teams.

---

Conclusion​

Windows 11’s Full Screen Experience arriving in Insider Build 26220.7051 is a significant, pragmatic push to make the platform friendlier to handheld gaming. The approach—layering a controller‑first launcher over the existing Windows foundation—delivers real benefits for constrained hardware by reclaiming runtime resources and simplifying navigation. Early results show measurable improvements in memory and, in some scenarios, frame stability; however, those gains are workload‑dependent and vary by device, drivers, and OEM tuning. The build’s simultaneous rollout of an opt‑in Ask Copilot taskbar and Bluetooth LE Shared Audio previews indicates Microsoft’s broader strategy: to fold Copilot and modern connectivity experiences into core shell surfaces while tailoring Windows behavior to new device classes. For enthusiasts, testers, and IT teams, the next steps are straightforward—test on non‑production hardware, update firmware and drivers, and validate compatibility for mission‑critical titles and enterprise policies. If the ecosystem partners and OEMs follow through with driver and firmware updates, FSE could become a dependable way to deliver a console‑like handheld experience without sacrificing the openness that makes Windows valuable to PC gamers.

---

Source: Technetbook Windows 11 Full Screen Gaming Experience Arrives in Insider Build 26220 with Console Like UI and Copilot AI

 

[ChatGPT]

Windows 11 Insiders can now stream the same audio to two separate Bluetooth headphones, earbuds, speakers, or hearing aids at once — a long‑requested convenience feature Microsoft calls Shared audio (preview), built on top of Bluetooth Low Energy (LE) Audio broadcast technology and rolling out to Dev and Beta channel testers in Windows 11 Build 26220.7051 (KB5067115).

Background / Overview​

Bluetooth LE Audio and the new broadcast model (Auracast) have been on the industry radar for more than a year. LE Audio replaces the classic A2DP approach with the LC3 codec and a broadcast mode that lets a single transmitter deliver synchronized audio to multiple receivers without a one‑to‑one connection. That underlying capability is what Microsoft is leveraging to give Windows 11 the ability to play a single audio stream on two Bluetooth LE devices simultaneously. Microsoft published the Shared audio preview details on the Windows Insider blog and began a staged rollout as part of Insider Preview Build 26220.7051. The feature appears as a Quick Settings tile named Shared audio (preview); once two compatible LE Audio accessories are paired and connected, the tile can start the sharing session and a Stop sharing control ends it. The preview is deliberately hardware‑gated to specific Copilot+ PCs for now.

---

What Microsoft released and where to find it​

The update and channels​

• The Shared audio preview is included in Windows 11 Insider Preview Build 26220.7051 and is distributed via the Dev and Beta channels to Insiders. The same build is referenced in Microsoft’s rollout notes and by multiple reporting outlets that tracked the preview.
• The rollout is gradual and device‑gated: installing the build alone does not guarantee the Shared audio tile will appear — the PC also needs specific Bluetooth and audio driver updates and, in many cases, the Copilot+ hardware profile.

Which Windows PCs are supported in the preview​

Microsoft currently enables Shared audio (preview) only on a subset of Copilot+ branded PCs that have the required Bluetooth and audio stack capabilities. The initial supported list includes Surface Laptop models (13.8‑ and 15‑inch) and Surface Pro 13‑inch variants powered by Qualcomm Snapdragon X silicon; other Copilot+ systems from Samsung (Galaxy Book5 360 and Galaxy Book5 Pro) are listed as “coming soon.” Microsoft’s blog also notes additional business variants and other Copilot+ devices will receive support after appropriate driver updates.

---

How Shared audio works (technical deep dive)​

LE Audio broadcast vs classic Bluetooth​

Bluetooth LE Audio introduces two game‑changing features relevant to Shared audio:

• The LC3 codec, which provides comparable or better perceived audio quality at lower bitrates than classic SBC/AAC A2DP streams. That means less power consumption and more efficient radio use.
• Broadcast/Auracast: a transmitter (the PC) can broadcast an isochronous audio feed that multiple receivers (headphones, hearing aids, speakers) can discover and join. This is not the same as opening two independent unicast connections; it’s a broadcast model with options for public or private access.

Microsoft’s Shared audio feature uses these LE Audio broadcast primitives to create a controlled, two‑listener experience on Windows 11. In the preview, Windows exposes that capability through the Quick Settings UX and manages which paired devices may join the session.

Synchronization, latency and quality​

Auracast and LC3 are designed to offer low latency — in practice, under ideal conditions LC3/Auracast can deliver sub‑40 ms round‑trip delays, which is a necessary baseline for lip‑sync when watching video together. However, real‑world latency depends on headset firmware, host Bluetooth chipset drivers, interference, and the particular LE Audio implementation of each accessory. Expect variability between brands and models. Microsoft has also been improving how Windows handles Bluetooth audio in parallel areas — for example, later Windows 11 updates introduced a “super wideband stereo” path that prevents stereo from collapsing to mono when headsets’ mics are active — an indication Microsoft is actively tuning its Bluetooth audio stack while adding features like Shared audio.

---

Devices, compatibility and firmware​

What accessories are supported (examples)​

Microsoft’s preview notes call out compatible accessories and manufacturers explicitly, and independent reporting has repeatedly echoed the list. Early compatible models mentioned by Microsoft and press coverage include:

• Samsung Galaxy Buds2 Pro, Galaxy Buds3 and Buds3 Pro
• Sony WH‑1000XM6
• Modern LE Audio‑capable hearing aids from ReSound and Beltone

The key requirement is that the accessory advertises Bluetooth LE Audio support (Auracast/LC3/ISOBROADCAST capabilities) in firmware. Microsoft recommends updating device firmware via the manufacturer’s app before testing Shared audio. Sony and other manufacturers have separately rolled out firmware updates to add Auracast/LE Audio broadcast support to newer headphones, which is a meaningful part of the story: Microsoft can enable a host feature, but multi‑device listening depends on accessory vendors shipping compliant firmware.

Why firmware and apps matter​

LE Audio is a joint specification spanning host controllers, link management, the LC3 codec, and the new broadcast/isochronous groups. In practice:

• Headphones and hearing aids must explicitly support LE Audio and the broadcast/join behavior. Older Bluetooth Classic devices (A2DP only) will not work.
• Many vendors expose LE Audio settings or firmware updates through their smartphone apps; updating those to the latest firmware is typically required.
• If a paired device doesn’t appear under the Shared audio tile, Microsoft’s guidance is to re‑pair after updating firmware and drivers.

---

How to try Shared audio today (step‑by‑step)​

• Enroll a compatible Copilot+ PC in the Windows Insider Program (Dev or Beta channel) and install the latest build (26220.7051) and available driver updates.
• Make sure your Bluetooth accessories support LE Audio and have the latest firmware installed via their manufacturer’s app.
• Pair and connect two compatible Bluetooth LE Audio accessories to the PC.
• Open Quick Settings (Windows Key + A) and look for the Shared audio (preview) tile. Select the two paired devices and click Share to start the session. Use Stop sharing to end it.

This UX is intentionally simple: Microsoft’s goal in the preview is to let Insiders experience the basics and provide feedback about stability, pairing quirks, audio glitches, or latency issues.

---

Real‑world caveats, limitations and risks​

Hardware and driver gating​

Microsoft has intentionally gated Shared audio to certain Copilot+ PCs initially. That is both a performance and compatibility safeguard: handling two LE Audio streams (even as broadcasts) still involves driver and controller responsibilities, and not all Bluetooth radios or their drivers will behave identically. Users of unsupported hardware should not assume the feature will work even after the build is installed.

Two‑device limit (preview) and future expectations​

The current preview experience is explicitly for two receivers. The Auracast specification can support many more, and venue‑scale broadcast scenarios are envisioned, but Microsoft’s first step is deliberate — two listeners is the pragmatic consumer use case (movie on a plane, share a playlist). Expect that number to change later, but do not assume unlimited receivers are supported in this initial rollout.

Latency, sync and codec mismatches​

• Because headsets implement LC3 and broadcast joins differently, the two paired devices might not be perfectly in lockstep under all conditions. Slight inter‑device latency differences or resampling artifacts are possible, especially when the host needs to bridge different Bluetooth chipsets and firmware implementations.
• When microphones are involved (for calls or voice capture), some devices or stacks may still fall back to modes that compromise stereo or increase latency. Microsoft’s ongoing stereo improvements are promising, but don’t expect identical behavior to wired splitters in every scenario.

Battery and RF congestion​

Broadcasting to multiple devices increases the host radio’s workload and may drain battery faster on laptops compared with single‑device streaming. In crowded RF environments (airports, conferences), scanning and joins might be slower or interrupted. Users should plan for higher power draw and possible interference.

Privacy and security concerns​

Auracast/broadcasted LE Audio can be configured as public or protected. Public streams are discoverable and joinable by anyone in range; private broadcasts may require a broadcast code or QR/NFC join mechanisms. For ad hoc two‑person sharing, the risk is low — you’re pairing devices to your machine — but using broadcast in public venues without privacy protections could expose audio to unintended listeners. Security researchers have noted that broadcast codes and their strength matter; simple numeric codes are less secure than 16‑byte secrets. Treat public broadcasts like public Wi‑Fi: convenient but not for sensitive audio content.

Support and troubleshooting surface area​

• If a device doesn’t appear in Shared audio, re‑pairing and firmware updates are the first fixes.
• Expect queueing issues when multiple Bluetooth accessories are connected; Windows may default to one device type for certain profiles.
• Because the feature is preview and device‑gated, users should file feedback via Feedback Hub under Bluetooth → Audio quality if they see glitches.

---

Accessibility and hearing aids: a meaningful use case​

One of the most compelling scenarios is accessibility: people who use hearing aids can join the same broadcast as someone wearing consumer headphones, allowing simultaneous access to media, lectures, or TV audio without complex hardware. Microsoft explicitly calls this out in the preview documentation, and hearing aid vendors such as ReSound and Beltone have LE Audio roadmaps that align with this functionality. For accessibility professionals, Shared audio can reduce friction when sharing content in classrooms, group therapy, or family settings. Caveat: hearing aids often have very conservative power and latency targets. In practice, ensure hearing‑aid firmware is up to date and that users test synchronization and audio quality before relying on the setup for critical listening tasks.

---

What this means for OEMs, accessory manufacturers and IT admins​

• OEMs and ODMs who ship Copilot+ PCs must ensure Bluetooth controllers and firmware are updated and that Windows Update can deliver appropriate drivers. Microsoft’s staged rollout implies driver and OEM coordination will be crucial.
• Accessory makers must ship LE Audio firmware (LC3 + broadcast join) in a stable form and provide update paths via mobile apps. Some companies (Sony, Samsung) have already released firmware updates to enable LE Audio broadcast in their newest models.
• Enterprise IT should consider privacy and policy implications before enabling Auracast broadcasts in public or shared corporate spaces. For large meeting rooms, a managed, password‑protected broadcast model is safer than an open public stream.

---

How to evaluate whether you should try the preview​

• You should test it if: you own a Copilot+ PC on the supported list, you have two LE Audio accessories with their latest firmware, and you want to experiment with sharing movie audio or music locally. Testing in a quiet environment will reveal sync and quality limits.
• Wait if: your primary headphones are Bluetooth Classic only, you rely on perfectly synchronized multi‑device audio for professional work, or you need guaranteed enterprise privacy for broadcasts. The preview is a convenience feature in active testing; it’s not yet the production‑grade Auracast rollout expected in venues.

---

Practical tips and troubleshooting checklist​

• Update everything: Windows build 26220.7051, Bluetooth controller drivers, and accessory firmware.
• Use manufacturer apps to confirm LE Audio / Auracast support and firmware version.
• Pair one device at a time, then pair the second; re‑pair if a device fails to appear in Shared audio.
• Test with simple local videos first to evaluate lip‑sync, then try music and multi‑app audio.
• If audio stutters or drops, try moving away from crowded RF areas, disable other Bluetooth devices temporarily, and confirm the PC’s power plan isn’t aggressively throttling radios.
• File feedback in Feedback Hub under Bluetooth → Audio quality, glitches, choppiness and stuttering if you encounter reproducible issues.

---

The bigger picture: where Shared audio fits in the Bluetooth audio roadmap​

Shared audio on Windows 11 is a pragmatic piece of a larger industry trend: bringing Auracast/LE Audio broadcast to more platforms (Android, Samsung, Windows) and to a broader set of accessories (headphones, earbuds, hearing aids, venue systems). Google and Samsung have already integrated similar broadcast features on Android devices, and accessory vendors are shipping firmware that supports multi‑listen scenarios. Windows catching up brings desktop and laptop environments into the same multi‑listener ecosystem. For consumers, the benefits are immediate: fewer cables, simpler shared listening, and the ability to use personal hearing devices in shared scenarios. For the industry, it creates new product differentiation (Auracast support, low latency tuning, UX polish) and operational challenges (driver coordination, privacy policy, RF management).

---

Final assessment: strengths, weaknesses and the near‑term forecast​

Strengths​

• Practical convenience: Simple UX in Quick Settings that solves a common annoyance — sharing audio without physical splitters.
• Built on modern standards: LC3 and Auracast are designed for low power and low latency, enabling viable multi‑listener experiences.
• Accessibility gains: Hearing aid support opens inclusive scenarios that were previously awkward or impossible.

Weaknesses / risks​

• Hardware and firmware dependence: The experience is only as good as the slowest component — radio, driver, or headset firmware. Expect fragmentation and intermittent behavior during preview.
• Privacy model nuances: Broadcast codes and join methods are useful but not bulletproof; venues and users must be conscious about what they broadcast publicly. Security researchers caution about simplistic codes and potential overspill.
• Limited scope in preview: Two devices only, Copilot+ gating, and staged rollouts mean the full promise of Auracast (many simultaneous listeners, large venues) isn’t realized yet.

Near‑term forecast​

Shared audio will mature as OEMs update drivers and accessory manufacturers ship LE Audio firmware. Expect Microsoft to widen device support beyond the initial Copilot+ list, raise the device count supported, and refine latency/quality issues through driver updates. The underlying standard (Auracast) is ready; the ecosystem coordination is the remaining piece.

---

Shared audio is not merely a convenience trick — it’s the desktop arrival of LE Audio’s broadcast era. For Windows users who’ve endured passing single earbuds or fumbling splitters, the preview is a meaningful step forward. But adoption will be incremental, driven by firmware updates, Bluetooth driver readiness and Microsoft’s staged release plan. Test it if you can, but temper expectations: the technology is promising, the standards are mature, but the ecosystem still needs time to knit together a consistently reliable, low‑latency multi‑listener experience.

---

Source: fakti.bg Windows 11 will play music simultaneously on two pairs of Bluetooth headphones