Windows on Arm Gets Mixed Reality Link: Meta Quest 3 Can Now Stream Desktops from Snapdragon X PCs

Microsoft has quietly closed an important compatibility gap between Windows on Arm PCs and Meta Quest headsets, enabling users to stream their Windows 11 desktop directly into virtual reality. The change, spotted by Reddit user Nicalay2 and confirmed by Windows Central, means that Snapdragon X-powered devices—like the Surface Pro 11 and other Copilot+ PCs—can now connect wirelessly to Meta Quest 3 and Quest 3S headsets using Microsoft‘s Mixed Reality Link app.

Mixed Reality Link is Microsoft’s refreshed approach to PC–headset integration, offering a passthrough-aware workspace with up to three virtual monitors. It had been limited to Intel and AMD machines throughout its preview period, but a recent update—seemingly rolled out without a formal announcement—has added support for Qualcomm’s Snapdragon X Elite and X Plus platforms. The app’s Microsoft Store listing shows an August 29 update, though no changelog has been published, and Microsoft’s official support documentation still makes no mention of Arm compatibility.

A software-first pivot years in the making

Mixed Reality Link marks a strategic about-face for Microsoft, which has scaled back its own headset hardware ambitions in favor of software and partnerships. By aligning with Meta’s Quest platform, the company can put Windows 11 at the center of mixed-reality productivity without bearing the cost or risk of building a new device. For Meta, the deal helps position Quest headsets as tools for work, not just gaming, leveraging Windows’ massive enterprise footprint.

The timing is no coincidence. Windows on Arm has been steadily shedding its “second-class” reputation as Qualcomm’s Snapdragon X series delivers meaningful leaps in performance, battery life, and native app availability. Emulation improvements in Windows 11 have made it possible to run a broad range of traditional desktop software on Arm laptops, and features like Mixed Reality Link help close the remaining experiential gaps that once kept business users tethered to x86.

What’s new: Snapdragon X support arrives through a silent update

Community reports indicate that Mixed Reality Link’s Arm support went live sometime after Horizon OS v72 reached Meta Quest headsets. That OS update, which Meta began pushing in early 2025, adds an experimental “Pair to PC with Microsoft Mixed Reality Link” toggle under Advanced Settings. Once enabled, and with Microsoft’s Mixed Reality Link app installed on a Windows 11 PC, the headset can mirror the desktop and even stream a full Windows 365 Cloud PC session.

Crucially, the updated app now runs natively on Snapdragon X processors. Early testers have confirmed successful pairings with a Surface Pro 11 and other Arm devices, though the experience varies based on OEM firmware, GPU drivers, and thermal design. Microsoft has not yet updated its support page to reflect the change, and the preview status means that rough edges are to be expected.

How the pairing flow works

Setting up Mixed Reality Link requires a few deliberate steps:

• On the PC: Install the Mixed Reality Link app from the Microsoft Store and keep the device unlocked.
• On the Quest headset: Navigate to Settings > Advanced > Experimental and enable “Pair to PC with Microsoft Mixed Reality Link.”
• Press Windows + Y on the PC to generate a pairing QR code. Scan it with the Quest headset, accept the prompts on both devices, and the connection is established.

Once paired, the headset presents the Windows desktop as a floating, passthrough-enhanced environment. Users can position up to three virtual monitors and adjust their layout in real time. Input is handled via the headset’s controllers, physical mouse and keyboard (visible in passthrough), or touch gestures. Microsoft recommends a Wi‑Fi 6 or 6E network for low latency and high bandwidth, though Wi‑Fi 5 (802.11ac) may suffice in less demanding scenarios. Bluetooth LE assists with discovery during the initial handshake.

Requirements at a glance

Real-world performance: what early adopters are finding

Community feedback from forums and social media paints a picture of a promising but still maturing experience. On Snapdragon X Elite devices with a strong Wi‑Fi 6E connection, the virtual desktops reportedly feel responsive enough for office work, web browsing, and document editing. Text clarity is generally good, and the passthrough mode helps avoid the disorientation that can come with full-VR workspaces.

However, several pain points have surfaced:

• Audio glitches and Teams issues: Accepting a Teams call while in-headset can sometimes fail to present controls, and audio routing may flop between headset and PC speakers unpredictably. Microsoft acknowledges these bugs in preview notes.
• Connection fragility: Sending Ctrl‑Alt‑Del or switching user accounts can abruptly terminate the session, forcing a re-pair.
• Network sensitivity: On busy or weaker Wi‑Fi, stream quality degrades quickly—artifacts and noticeable lag appear, which makes text-heavy work unpleasant.
• Arm hardware variability: Not all Snapdragon X laptops perform identically. Differences in OEM thermal management and GPU driver maturity mean some users see stuttering while others have a smooth experience.

Security and privacy: what IT departments need to know

Streaming an entire Windows desktop into a headset expands the attack surface in ways that may not be immediately obvious. Every application with screen-capture permission could potentially expose data on the virtual monitors, and the wireless stream itself—if not properly encrypted—could be intercepted. Microsoft’s QR‑code pairing adds a layer of local authentication, but it does not by itself enforce enterprise policies.

Organizations piloting Mixed Reality Link should:

• Treat headset-to-PC connections like any remote desktop client, ensuring they go through VPNs and comply with conditional access rules.
• Log and monitor first-pairing events, especially on shared or kiosk devices.
• Validate that endpoint security agents, particularly those that rely on kernel‑mode drivers, function correctly on Snapdragon X hardware. Some Arm‑specific gaps in driver support may leave endpoints underprotected during mixed‑reality sessions.
• For Windows 365 Cloud PC streaming, verify that tenant policies extend to the headset and that no corporate data leaks into unmanaged local storage.

Competitive landscape: where Mixed Reality Link fits

Mixed Reality Link enters a field where third‑party solutions like Virtual Desktop and Immersed have long dominated PC‑to‑Quest streaming. Those apps offer mature feature sets—including higher custom monitor counts, multi‑codec streaming, and cross‑platform compatibility—and they work on older headsets, not just Quest 3/3S. Microsoft’s advantage is deep Windows integration and zero additional cost. For users already inside the Microsoft ecosystem, the ability to summon a multi‑monitor workspace with a built‑in tool may be enough to forgo third‑party alternatives.

On the other end of the market is Apple Vision Pro, which delivers a tightly integrated spatial OS for macOS users at a substantially higher price. The Meta‑Microsoft pairing prioritizes reach and affordability, leaning on existing PC infrastructure rather than building an all‑new headset‑native operating system.

Strategic implications for Windows on Arm

Supporting Snapdragon X with Mixed Reality Link signals that Microsoft views Arm not as a second‑tier platform but as a first‑class citizen for emerging productivity scenarios. If the user experience stabilizes and driver support broadens, enterprises will have a stronger incentive to deploy thin, long‑runtime Copilot+ laptops for everyday work, offloading heavy workloads to the cloud when needed. Mixed Reality Link effectively turns any Arm PC into a virtual multi‑monitor workstation that fits in a backpack alongside a Quest headset.

For Microsoft, the bet is clear: stay relevant in mixed reality without building hardware, and use software to glue together Windows, Azure, and Meta’s growing installed base. For the Windows on Arm ecosystem, this feature could accelerate adoption among mobile professionals and creatives who crave screen real estate but don’t want to carry bulky monitors.

Practical recommendations for users and IT pilots

• Start small: Test with a dedicated Wi‑Fi 6E access point, a mix of Snapdragon X and x86 devices, and a structured trial plan that covers audio routing, multiple virtual monitors, and Cloud PC streaming.
• Manage expectations: Remember that this is a preview. Expect incremental updates and bug fixes over the coming months. Keep the headset’s Horizon OS and the Mixed Reality Link app up to date.
• Secure the pairing flow: Disable the experimental toggle when not in use, and avoid pairing on untrusted networks. Use endpoint protection that can monitor unusual network activity from the Mixed Reality Link service.
• Keep an eye on alternatives: If Mixed Reality Link proves too unstable for production work, Virtual Desktop or Immersed remain capable fallbacks that work on a wider range of hardware.

Conclusion

The quiet arrival of Snapdragon X support in Mixed Reality Link is a milestone for Windows on Arm, transforming thin-and-light laptops into portable virtual‑workspace hubs. It represents a pragmatic collaboration between Microsoft and Meta, one that sidesteps heavy hardware investments while pushing forward the vision of spatial productivity. Early adopters can already enjoy up to three virtual monitors and Cloud PC integration, but they should brace for preview‑era quirks: audio glitches, fragile connections, and network sensitivity.

For IT teams evaluating Copilot+ hardware, Mixed Reality Link offers a low‑cost, software‑centric proof point that mixed‑reality desktops are more than a gimmick. As driver support matures and Microsoft refines the experience, the headset could become a standard companion to an Arm laptop—a lightweight, immersive display that travels anywhere. The pieces are now in place; the next few months of real‑world testing will determine if they hold together.