Windows 11 Release Preview: Auto SR expands to Copilot+ hardware

Microsoft’s latest Release Preview update for Windows 11 brings a concentrated set of AI-driven features to Insiders — and one of the most eye-catching is the expansion of Automatic Super Resolution (Auto SR) to more titles, but with a strict hardware caveat: Auto SR remains gated to Copilot+ PCs for now. This update (delivered as KB5065789 in the Release Preview channel) also bundles enterprise-facing controls such as Administrator Protection Preview, better passkey integration via a plugin model, and several quality-of-life improvements — from Click to Do enhancements and Narrator tweaks to AI actions in File Explorer, a refreshed Windows Share menu, and support for Emoji 16.0. The rollout is deliberately staged, and many features remain tied to Copilot+ hardware and licensing, so this is a practical preview of Microsoft’s AI roadmap rather than an immediate platform-wide shift.

Background: what Microsoft shipped in KB5065789 (Release Preview)​

Microsoft pushed cumulative updates to the Release Preview channel that update Windows 11 version 24H2 and 25H2 to the reported builds associated with KB5065789. The Release Preview announcement documents the build metadata and the staged feature list included in that update, and it explicitly highlights the gradual rollout nature of the features, meaning availability varies by hardware, region, and licensing. The Release Preview blog confirms the builds tied to the update and summarizes the new Copilot+ experiences and enterprise controls included in the package. (blogs.windows.com)
This is not a single, monolithic feature drop. Instead, Microsoft continues to use the enablement-package model for targeted feature rollouts: small KB-style updates that flip switches, add enablement bits, or install light-weight packages (for example, the Auto SR package) while keeping kernel and servicing churn to a minimum. That approach reduces disruption but increases the complexity of determining feature availability across a mixed-fleet environment. (blogs.windows.com)

---

What is Automatic Super Resolution (Auto SR) — a technical primer​

Automatic Super Resolution (Auto SR) is Microsoft’s OS-integrated AI upscaler for gaming. Unlike vendor-specific upscalers that ship inside a GPU driver or a game engine plugin, Auto SR is implemented at the operating-system layer and leverages an on-device Neural Processing Unit (NPU) alongside the GPU to:

• Lower a game’s render resolution to reduce GPU load and increase framerate.
• Run an on-device AI model on the NPU to upscale those frames back toward the target resolution, restoring detail and improving perceived visual fidelity.

Microsoft’s support documentation and DirectX engineering posts explain that Auto SR coordinates GPU, CPU, and NPU workloads to produce an upscaled frame with minimal latency impact, and that it ships pre-configured to enhance a set of tested games out of the box. The initial list of auto-enhanced titles includes popular DX11/DX12 games such as Borderlands 3, Control (DX11), The Witcher 3, and a few others; Microsoft also publishes guidance for manual opt-in for additional games. (support.microsoft.com)
Key technical constraints to note:

• Auto SR is designed for DirectX 11 and DirectX 12 titles. Games using older runtimes (DirectX 9), Vulkan, or OpenGL are not currently supported.
• The feature requires a display of 1080p or greater for the best results.
• Auto SR processing runs on an NPU; in practice this has meant Copilot+ PCs with Snapdragon® X Series chips were the first devices capable of running it at launch. Microsoft’s support pages and the DirectX blog clearly document these hardware requirements. (support.microsoft.com)

---

Copilot+ hardware gating: why Auto SR is limited to a subset of PCs​

The headline limitation is simple: Auto SR is gated to Copilot+ PCs at present. Microsoft’s official support page states that Auto SR “seamlessly integrates with Windows on a Copilot+ PC with a Snapdragon® X Series processor,” and lists the Hexagon NPU and integrated GPU as hardware prerequisites. Early device availability therefore skewed heavily toward Qualcomm Snapdragon X-powered laptops that qualify under Microsoft’s Copilot+ program. (support.microsoft.com)
Independent reporting and developer commentary clarify the nuance: Auto SR is Microsoft’s feature (not a Qualcomm proprietary technology), and the Copilot+ exclusivity is a combination of what is available today (Qualcomm devices have the right NPU/GPU combination and driver stack ready) and Microsoft’s staged rollout approach. Qualcomm itself has stated Auto SR is Microsoft’s implementation, but that Qualcomm devices are where the feature is available today because of performance thresholds and the existing platform integration. Other vendors (Intel and AMD) are bringing NPUs into laptop-class chips and Microsoft has indicated broader Copilot+ hardware support will eventually follow, but concrete timelines remain vendor-dependent and incremental. (theverge.com)
Practical implications for gamers and IT:

• Gamers on Copilot+ laptops (Snapdragon X Elite / X Plus family initially) will see prompts to enable Auto SR when launching supported games.
• If you rely on a particular title for competitive play, verify anti-cheat compatibility and publisher support for ARM/Auto SR scenarios; emulated x64 titles and anti-cheat driver readiness remain a gating factor for many multiplayer releases.

Caveat: Microsoft and ecosystem partners have signaled that Intel and AMD Copilot+ designs (with integrated NPUs) will receive the same features later, but the timeline is not fixed in stone. Treat the Copilot+ requirement as a current fact, not an immutable limitation — but plan around it for procurement and test rollouts. (theverge.com)

---

What Auto SR delivers — measured benefits and real-world trade-offs​

Auto SR’s promise is compelling: improved frame rates and clearer visuals with minimal additional GPU load because the NPU handles upscaling. Field testing and vendor write-ups report:

• Noticeable framerate gains in GPU-bound scenes at the cost of a one-frame average input latency increase in many cases — a small price for single-player fidelity boosts, but a factor for latency-sensitive multiplayer titles. (howtogeek.com)
• Visual fidelity that, in many scenes, matches or exceeds native rendering at the original resolution — but HUD and text may exhibit softening when games render at very low internal resolutions. Microsoft acknowledges this trade-off and excludes certain text-heavy or UI-critical scenarios from automatic application. (devblogs.microsoft.com)
• Compatibility nuances where HDR, certain 10‑bit formats, and graphic runtime idiosyncrasies produce poor results or are unsupported. Microsoft’s support documentation lists these caveats explicitly. (support.microsoft.com)

For gamers: run practical tests for your top titles, confirm in-game capture tools (Game Bar, OBS) and HUD clarity, and look for an Auto SR indicator or notification when a supported game launches. For enterprises or evaluators: plan head-to-head comparisons with existing upscalers (NVIDIA DLSS, AMD FSR, Intel XeSS) and track both performance and input latency across representative workloads. (devblogs.microsoft.com)

---

Broader AI features in KB5065789: what’s new for productivity, accessibility and security​

KB5065789 isn’t just about gaming. The Release Preview notes and associated documentation highlight several additional capabilities:

Administrator Protection Preview​

• Administrator Protection is a reworked elevation model to harden admin privileges by creating a separate system-managed administrator account token and generating just-in-time admin tokens to perform elevated tasks. This aims to reduce the attack surface for elevation-of-privilege malware and to make UAC flows more auditable and secure. Developers and IT pros should note the behavioral changes to elevation flows and the new security boundary introduced by the System Managed Administrator Account (SMAA). (blogs.windows.com)

Passkeys and third-party plugin providers​

• Windows 11 now supports a plugin model for third-party passkey providers, allowing passwordless credential managers (e.g., 1Password, Bitwarden) to integrate on-device so users can create, store, and use passkeys via their chosen provider while still leveraging Windows Hello for verification. Microsoft’s developer and support docs describe the plugin credential manager APIs and demo applications for dev testing. This is a meaningful step toward a practical, cross-provider passwordless UX on Windows. (learn.microsoft.com)

Click to Do and Narrator improvements​

• Click to Do receives table detection and Excel export actions, speeding the extraction of tabular data from images or screenshots into usable spreadsheet format. Narrator (the screen reader) sees functional improvements aligned to professional document workflows and assistive technology needs. These are incremental but welcome accessibility and productivity upgrades for both consumer and enterprise users.

AI actions in File Explorer​

• The File Explorer context menu gains AI actions such as image background blur, object removal, visual search, and content summarization for documents. Some document AI actions may be limited to Microsoft 365 Copilot customers initially, and the availability of AI actions remains staged by hardware and licensing. Right-click AI actions place Copilot-style utilities directly where files live, collapsing task flows that once required multiple steps. (theverge.com)

Windows Share menu refresh and Emoji 16.0​

• The Windows Share dialog now supports pinning favorite share targets to streamline recurring workflows, while system emoji support has been updated to cover Emoji 16.0 designs in the Fluent set. Implementation details (e.g., where emojis render, which apps support the updated glyphs) vary by app and component. (emojipedia.org)

---

Cross-referencing and validation — what we confirmed​

To ensure the facts in this piece are verifiable:

• Microsoft’s official Auto SR support article provides the canonical system/game requirements and the initial list of out-of-the-box titles. That page is the primary reference for how to enable Auto SR and its gating to Copilot+ devices. (support.microsoft.com)
• The DirectX Developer Blog published by Microsoft lays out the implementation mindset and testing guidance for Auto SR and clarifies the model about supported pipelines and the recommended behavior when toggling the feature. This post complements the support article and explains engineering trade-offs. (devblogs.microsoft.com)
• The Windows Insider Release Preview announcement documents the actual KB (KB5065789) and the associated build numbers being shipped to Insiders, confirming the presence of the stated features in the Release Preview channel. (blogs.windows.com)
• Independent coverage and testing commentary (The Verge, How-To Geek) confirm the Copilot+ gating and explain how Qualcomm devices were the initial hardware vector, while also clarifying that Microsoft’s feature is not Qualcomm-proprietary. Those outlets provide a useful outside perspective on vendor and timing nuance. (theverge.com)
• Passkey plugin and developer documentation on Microsoft Learn and Windows Developer Blog outline the API and partner integrations (1Password, Bitwarden): a clear cross-reference for the new passkey plugin model. (learn.microsoft.com)

Where vendor claims were vague or forward-looking (for example, “Intel and AMD support is coming next month”), the public documentation did not present fixed release dates — these statements therefore require cautious interpretation. If a timeline matters to your procurement or deployment plan, treat the availability claims as planned not guaranteed and verify with OEM and Microsoft channel updates before committing.

---

Risks, limitations, and operational recommendations​

The feature set in KB5065789 is exciting, but it introduces operational and security considerations for both consumers and IT organizations.

• Hardware and licensing fragmentation: Many AI features are gated by Copilot+ hardware and/or Copilot licensing (Microsoft 365 Copilot). This means some users will be able to access capabilities that others cannot, complicating support and user expectations. Plan testing and rollout using a representative Copilot+ device fleet before enterprise-wide adoption. (support.microsoft.com)
• Anti-cheat and multiplayer compatibility: For gamers evaluating Auto SR on Copilot+ laptops, anti-cheat support is a real blocking factor. Even if Auto SR can technically run, the absence of signed or ARM-native anti-cheat drivers can prevent multiplayer gameplay. Validate anti-cheat footprints for mission-critical titles before recommending Copilot+ devices for gaming teams.
• Privacy and data governance: Features such as Click to Do, Recall (where enabled), and AI actions sometimes capture or index screen content. Microsoft documents local-processing assurances for many features, but the data governance picture for managed devices (BYOD, shared devices) requires policy configuration and testing. Administrators should audit generative-AI permission surfaces and ensure configuration aligns with corporate privacy policies.
• UI and visual artifacts: Auto SR can introduce softening in small UI text or HUD elements if a game is rendered at a very low internal resolution. For certain competitive scenarios (where HUD clarity is critical), the trade-off may be unacceptable. Provide end-users with guidance on enabling/disabling Auto SR on a per-game basis. (devblogs.microsoft.com)
• Migration pain for legacy tooling: The release notes reiterate that Microsoft continues to phase out very old components and legacy tooling — IT teams should inventory scripts and automation that rely on deprecated modules and update them proactively to avoid disruption when these builds go broader. (blogs.windows.com)

Operational checklist for IT and advanced users:

• Collect representative Copilot+ hardware for testing and install KB5065789 in a Release Preview ring or lab image.
• Test critical apps and games, explicitly exercising anti-cheat flows, in-game overlays, and capture tools.
• Validate passkey provider integration using a controlled pilot (1Password or Bitwarden betas where available).
• Audit and configure generative-AI permissions in Settings and ensure admins understand the new Administrator Protection model.
• Document user guidance for enabling/disabling Auto SR and for reporting visual/UI regressions.

---

The product strategy: why Microsoft is building Auto SR into Windows​

Embedding Auto SR at the OS layer signals a strategic bet: Microsoft wants Windows to be the integrator for device NPUs and AI features, rather than leaving those capabilities siloed in vendor drivers or individual apps. This OS-level approach gives Microsoft centralized control over compatibility lists, enablement, telemetry, and the UX for opting in/out.
Pros:

• Easier discovery and consistent UX for upscaling across many titles.
• Ability to offload to the NPU uniformly and optimize system-level scheduling.
• Faster distribution of new enablement packages through Windows Update and the Microsoft Store.

Cons:

• Tighter coupling between hardware, OS enablement, and licensing can slow broad availability.
• Centralized control may frustrate power users who want fine-grained, per-app upscaling choices outside the OS-managed path.

From a market perspective, Auto SR places Microsoft as a first-class provider of an AI upscaler that can compete in scenarios where DLSS/FSR/XeSS are not available or not supported — especially for DX11/DX12 titles that lack vendor upscalers. Whether that drives broad adoption depends on the speed at which Copilot+ hardware proliferates and on Microsoft’s ability to coordinate with GPU and CPU vendors. (devblogs.microsoft.com)

---

Practical steps for enthusiasts: how to try Auto SR and related features today​

• Join the Windows Insider Program (Release Preview or Dev/Beta depending on the feature you want) and ensure you’re on the builds that include the KB5065789 enablement bits.
• Confirm your device is a Copilot+ PC with an eligible Snapdragon X Series processor (or equivalent Copilot+ hardware if your OEM indicates Intel/AMD support has arrived).
• Update Windows and then check Settings > System > Display > Graphics for the Automatic super resolution toggle; the Auto SR package may also be updated via the Microsoft Store. When you launch a supported game, look for the Auto SR notification. (support.microsoft.com)
• For File Explorer AI actions, right-click supported files (images or Office documents) to surface AI actions. Note that some document summarization features are tied to Microsoft 365 Copilot licensing and may not appear without the appropriate subscription. (theverge.com)
• Try the passkey plugin workflow by installing supported passkey manager betas (1Password or others where available) and enabling the plugin credential manager in Settings under Passkeys > Advanced options. (blogs.windows.com)

---

Conclusion — a pragmatic preview of where Windows AI is headed​

KB5065789’s Release Preview deployment offers a clear view of Microsoft’s near-term strategy: tie compelling AI experiences to specialized hardware (Copilot+ devices), ship integrated OS-level capabilities that reduce friction for everyday users, and layer enterprise-grade controls for admin visibility and security. Automatic Super Resolution is the most visible expression of that approach for gamers — delivering measurable framerate and visual improvements by leveraging the NPU — but it also underscores the fragmentation risk during staged rollouts.
For consumers and enthusiasts, this update is a prompt to test and evaluate: Auto SR can be a transformative single-player experience enhancer on supported Copilot+ laptops, and AI actions in File Explorer plus passkey plugin integration make daily workflows easier. For IT and procurement teams, the update is a call to test, document, and plan: hardware prerequisites, anti-cheat readiness, and licensing constraints must be validated before deploying these features at scale.
The wider platform implications are clear — Microsoft is building an NPU-forward Windows where on-device AI is a first-class resource. The road to ubiquity will be incremental: broader hardware support and clearer timelines from OEMs will decide whether Auto SR and its sibling features move from niche differentiators into mainstream Windows capabilities. In the meantime, KB5065789 is an important step on that path: a staged, measured rollout that shows what is possible while leaving the heavy lifting of full-scale compatibility and enterprise readiness to the months ahead.

---

Source: Windows Report Microsoft brings Auto Super Resolution (Auto SR) to more titles, but only for Copilot+ PCs