Windows 11 Auto SR on ROG Xbox Ally X: Handheld Setup, 1080p Support and Performance Mode

As Jay Peters reports in The Verge, the release adds battery-powered handheld operation and support for games running at 1080p. However, the accompanying Performance Mode and Auto HDR compatibility are arriving through Windows updates, rather than necessarily appearing on every eligible device immediately. That distinction matters before anyone spends an evening looking for a missing switch.

The useful story here is not simply “Microsoft has a DLSS competitor.” It is that an existing Windows graphics feature is becoming more practical—and that enabling it, confirming it works, and judging whether it helps are three separate tasks.

What changed, and what is still rolling out?​

Microsoft began the Ally X preview on April 30, 2026, limiting it to Xbox Insiders using the device docked. The company explained that larger external displays made the compromise between image detail and frame rate especially noticeable.

The new release removes that dock-only restriction. Mezha.net’s coverage, which attributes the announcement to The Verge, also identifies the two other headline changes: 1080p game support and a forthcoming Performance Mode supporting up to 120 frames per second. These are accounts of the same rollout, not separate releases or independent performance tests.

Here is the availability distinction owners should keep in mind:

The Verge and Mezha both distinguish the released handheld capabilities from the Windows-update-delivered additions. “Out of preview” therefore should not be read as “every announced option is already on every device.”

For owners, that suggests a sensible order: establish that ordinary Auto SR works first, then investigate whether the additional modes have reached the machine. Treating the entire announcement as a single on/off condition makes troubleshooting unnecessarily confusing.

Why handheld support matters more than the headline suggests​

The practical importance is straightforward. Docked upscaling addresses the challenge of putting a handheld’s output on a larger screen. Undocked support addresses the way an owner may actually spend most of a session: using the built-in display, without external equipment.

That does not make the docked preview misguided. Microsoft explicitly designed its initial testing around external-screen image quality. But it does change the feature’s usefulness from something tied to one arrangement of hardware into an option worth evaluating during ordinary portable play.

There is an important distinction between working on battery and improving battery endurance. The announcement establishes the former; it does not supply a battery-runtime comparison. Owners should not interpret the removal of a power-connection restriction as a promise of longer sessions between charges.

Our practical recommendation is to evaluate handheld mode on its own terms. A configuration that looks attractive on a television is not automatically the setting you will prefer on the internal screen. Decide whether the goal is sharper detail, steadier motion, or a particular balance—not merely whether an additional graphics feature can be switched on.

1080p support removes a usability trap​

During the preview, a game’s resolution could prevent Auto SR from engaging. Microsoft now supports a 1080p base resolution and describes external-display upscaling up to 1440p. It nevertheless cautions that 1080p handheld operation may offer less favorable performance than other configurations.

The Verge reports Microsoft’s expectation of visual improvements, particularly in older games, despite that performance caveat. This is a quality claim with a qualification, not a blanket promise that every 1080p game will become faster.

The useful interpretation is that compatibility and optimal settings are different things. Supporting a common resolution removes a potential activation obstacle; it does not establish that this resolution is the best choice for every title.

When evaluating it, ask two questions separately:

• Does Auto SR actually activate with the chosen settings?
• Once active, do you prefer the result to the alternative?

A “yes” to the first does not oblige you to answer “yes” to the second. Graphics options are tools, not loyalty tests.

A DLSS alternative, but not an identical implementation​

Microsoft’s April technical explanation distinguishes Auto SR from game-integrated upscalers such as Nvidia DLSS, AMD FSR, and Intel XeSS. Those implementations can use information supplied by the game, including motion vectors. Auto SR instead operates through Windows, making upscaling available to supported titles without requiring each developer to integrate it.

Microsoft also describes an NPU-based approach that runs alongside GPU rendering. Its explanation emphasizes reconstructing detail with larger models and reducing dependence on texture-data movement—an issue it identifies as important on bandwidth-constrained handhelds. These are Microsoft’s architectural explanations, not independent proof that Auto SR always produces the best result.

That distinction changes how to interpret “DLSS competitor.” The phrase describes a similar objective, not interchangeable hardware requirements, identical reconstruction methods, or an established winner.

The strongest practical case is straightforward: consider a supported older game without a useful built-in upscaler. An operating-system option gives the player something new to evaluate without waiting for that game’s developer to revisit its rendering pipeline.

Where multiple options exist, our recommendation is comparison rather than assumption. Choose a repeatable section of gameplay, keep unrelated settings unchanged, and inspect the result while moving—not just while admiring a paused scene. Pay attention to the elements you actually notice during play: text legibility, fine detail, motion, and consistency.

This is a suggested evaluation method, not a claim that we have benchmarked the release.

What the 120-FPS announcement actually means​

Microsoft’s example uses Rocket League on an Ally X at 720p with the high graphics preset: it reports averages of 70 FPS in Quality Mode and 115 FPS in Performance Mode. These are vendor-provided results for that configuration.

Mezha reports that Performance Mode raises the feature’s previous approximate 60–75 FPS limit to as much as 120 FPS. The upper figure describes supported capability, not a guaranteed outcome in every game.

The settings are essential to understanding the example. A 720p demonstration should not be silently converted into a 1080p handheld benchmark. Nor does one game establish what happens across an entire library.

Our reading is that Performance Mode creates another tuning choice. It does not remove the need to choose. Once available, compare modes in the same game and scene before deciding which belongs in your normal configuration.

For competitive play, a player might prioritize responsiveness and smooth motion. For slower-paced exploration, another might prefer the image they find cleaner. Neither preference can be settled by a single headline frame-rate number. The meaningful result is the one that survives comparison under the settings you intend to use.

How to prepare and enable Auto SR​

Microsoft Support lists Windows 11 version 24H2 or later, fully updated, a display resolution of at least 1080p, and current graphics and neural-processor drivers. Its requirements identify supported NPU-equipped hardware; this is not a universal feature for every Windows 11 gaming PC.

For the November release, Microsoft gives this setup sequence:

1. Update Game Bar and install current Windows 11 updates.
2. Install or update the Auto Super Resolution Package through Microsoft Store.
3. Open Game Bar with the Xbox button, or Win + G on a keyboard.
4. Navigate to Widgets menu > Display > Graphics.
5. Select Quality or Performance, where available.

Do not assume a missing Performance choice means the entire installation has failed: that addition has a separate Windows-update rollout.

A useful setup checklist should distinguish prerequisites from results. Installing the package establishes that a component is present. Selecting a mode establishes your preference. Neither, by itself, proves that the running game is being processed as intended.

Microsoft’s support guidance says the Game Bar Display widget can show whether Auto SR is active or requires another action, such as changing resolution or restarting the game. Use that status as the confirmation point rather than relying solely on whether the picture seems different.

Troubleshooting without changing everything at once​

Start with eligibility. Microsoft’s requirements specify DirectX 10 or later games, alongside supported hardware and software. A general Windows update cannot, by itself, establish that every title or rendering configuration is compatible.

Next, follow the guidance shown for the running game. Microsoft’s support instructions identify supported resolutions and Fullscreen or Exclusive Fullscreen operation where required. If the widget requests a restart, complete it before judging whether the change worked.

Our recommended diagnostic sequence is deliberately conservative:

• Record the game’s starting resolution, graphics preset, and display mode.
• Check Auto SR’s status before making another change.
• Follow the specific action requested.
• Recheck the status and repeat the same gameplay section.
• Keep or reverse the change based on the result.

This avoids the classic troubleshooting problem: changing five settings, seeing an improvement, and having no idea which setting mattered.

Separate activation problems from quality preferences, too. If the feature never becomes active, investigate prerequisites and compatibility. If it activates but you dislike the result, that is a comparison outcome—not necessarily an installation fault.

For a useful support report, record the device, game, resolution, selected mode, and whether the issue occurs docked or undocked. Those details are more actionable than “the upscaler looks wrong,” and they make your own retesting easier.

Auto HDR is a separate compatibility improvement​

Microsoft is also adding the ability to use Auto SR with Auto HDR, including on suitable HDR displays. This combination belongs to the staged Windows-update rollout.

The practical distinction is between two different visual goals: reconstructing image detail and extending the presentation of games without native HDR support. Microsoft describes Auto HDR as providing richer colors and brighter highlights on HDR-capable displays.

Our advice is to evaluate these changes separately before combining them. First establish that Auto SR behaves as expected. Then assess HDR. Otherwise, an altered image leaves you trying to diagnose two variables at once.

The useful takeaway​

This release deserves attention because it removes a concrete restriction, not because “AI upscaling” makes an impressive label. The important improvement is practical access to Auto SR during handheld play, with further choices arriving separately.

For eligible owners, the sensible approach is measured: update the required components, confirm activation, compare a familiar game, and retain the settings that genuinely improve the experience. Treat vendor benchmarks as examples and rollout announcements as availability guidance—not as promises about your entire library.

A handheld graphics feature has finally escaped the dock. The next test is whether it earns a permanent place in your settings.