MSI Claw Gets Xbox Style Full Screen Experience in Windows 11 Insider Preview

Microsoft has begun rolling out a preview of the Xbox Full Screen Experience (FSE) to MSI’s Claw family as part of a Windows 11 Insider Preview build, extending the console‑style, gamepad‑first navigation layer beyond the ROG Xbox Ally devices and into a broader set of Windows handhelds. The update places a new “home app” model at the center of handheld usage, lets devices boot directly into a full‑screen launcher, and trims background activity to free memory and battery for games. It is available today only via the Insider channel and comes with the caveat that early adopters are likely to encounter rough edges — observers and hands‑on users have already reported several usability and startup problems on devices that received FSE earlier this month.

Background​

Microsoft’s Full Screen Experience is a new Windows 11 mode designed specifically for small, gamepad‑led handheld PCs. At its core, FSE does three things differently from a regular Windows 11 desktop:

• Presents a single, controller‑friendly home app (commonly the Xbox app) as the primary launcher.
• Optimizes system behavior for gaming by reducing background processes, deferring or preventing nonessential apps from auto‑starting, and simplifying navigation for an on‑screen, full‑window experience.
• Offers quick entry/exit from desktop Windows through Game Bar, Task View, or a startup option so users can choose whether the device boots into the full‑screen environment.

Microsoft first shipped FSE with the Xbox Ally and Ally X introductions; the preview now supports “MSI Claw models” in the latest Insider build. On supported devices, Windows Settings exposes the control at Settings > Gaming > Full screen experience, where you can choose the Xbox app (or another installed “gaming home app”) as your home app and opt to enter FSE automatically at startup.

---

What the MSI Claw rollout means​

MSI Claw: where this fits​

The Claw family has been MSI’s bid at the high‑end Windows handheld space: multiple Claw models span Intel Core Ultra and AMD Ryzen Z2 platforms, with 7–8‑inch 120Hz displays, Thunderbolt/USB4 connectivity, and batteries sized for longer sessions on the larger configurations. Those devices ship with full Windows 11 — which is powerful and flexible but historically less friendly to strictly gamepad‑first workflows than console UI.
Bringing FSE to MSI Claw recognizes two facts about the current handheld market: users want a fast, gamepad‑first launcher that feels like a console, and OEMs want a way to make Windows handhelds behave more predictably for gaming workloads. For MSI, supporting FSE is a strategic play to make its handhelds more attractive to the same crowd that might be eyeing the ROG Xbox Ally or Valve/Lenovo handhelds.

What’s arriving in the Insider preview​

On the technical side, enabling FSE on a supported MSI Claw model will:

• Add Xbox (or another selected home app) to the boot flow so the system can launch directly into a full‑screen launcher.
• Give an option to “Enter full screen experience on startup,” which defers many desktop startup apps until the first time the user switches back to the Windows desktop — this is intended to improve performance and battery life when gaming.
• Expose the FSE entry point from Game Bar and Task View, enabling quick switching between desktop and full‑screen home app.

Those controls are visible in Windows Settings under Gaming > Full screen experience. Users who want to try FSE must be on the Windows Insider channel that contains the FSE preview bits; this is not yet a general release.

---

How to enable the Full Screen Experience (step‑by‑step)​

• Join the appropriate Windows 11 Insider Preview channel that includes FSE (Insider builds only).
• Update Windows to the build that contains the FSE preview.
• Open Settings and navigate to Gaming > Full screen experience.
• In the “Set your home app” dropdown, select Xbox (or another installed gaming home app).
• Optionally toggle Enter full screen experience on startup to boot directly into FSE.
• Use Game Bar, Task View, the Xbox app UI, or an assigned hotkey to enter and exit FSE.

These steps reflect the controls visible in the Windows 11 gaming settings for FSE and are intended for supported devices only. If your device isn't listed as supported, the FSE options may not appear or may not function correctly.

---

Early reactions and real‑world problems​

The concept of an FSE is straightforward; the execution is where early talk has centered. Reviewers and user reports from the initial Ally rollouts and early Insider activations have identified several recurring themes:

• Boot and startup reliability: Some devices enabled for FSE booted to the regular Windows desktop or showed the Xbox app as a regular window instead of a full‑screen experience. Users reported needing to disable the Windows login PIN or use advanced tools to force FSE transitions in some cases.
• Wake, sleep and resume quirks: Handhelds depend heavily on predictable sleep/wake behavior; several early devices exhibited inconsistent sleep performance or long resume delays when FSE was engaged.
• OEM software interactions: Vendor‑supplied utilities (for battery profiles, thermal modes, firmware updates) occasionally conflicted with the reduced‑background model FSE enforces, producing unexpected performance or power behavior.
• Edge‑case app compatibility: Some third‑party overlays, anti‑cheat systems, or legacy games didn't behave as expected when the system was prevented from loading typical background services during FSE sessions.

These issues are common with any major UX rework delivered first through Insider channels. They shouldn’t be surprising, but they are meaningful: for handheld owners who want a reliable “just‑turn‑it‑on and play” appliance, the preview state is not an ideal place for primary use.

---

Strengths: where FSE helps handheld gaming most​

The Full Screen Experience is not just a skin on top of Windows; it introduces behavior changes that can materially improve the handheld gaming experience when implemented well.

• Gamepad‑first interface: FSE reorganizes navigation around controllers — a genuine win for handhelds where touch and keyboard are secondary. Menus, library navigation, and app switching are simplified for A/B/X/Y style input.
• Reduced system noise: By deferring nonessential startup apps and background tasks, FSE can free memory and CPU headroom, which handily benefits short burst gaming sessions on modest thermal budgets.
• Cleaner focus for first‑time users: New handheld buyers often find Windows desktop confusing on small screens. FSE lowers the barrier to entry by presenting a single launcher that looks and feels like a console home screen.
• Flexible entry/exit model: Users are not locked out of full Windows; FSE is an alternative environment that can be entered or exited, preserving the ecosystem benefits of Windows for games not serviced by a single store or launcher.
• OEM differentiation: For vendors like MSI, supporting FSE lets them sell a handheld that feels closer to console UX without abandoning the app and peripheral flexibility of Windows.

---

Risks and downsides to weigh​

Any system that alters startup behavior and user flow brings tradeoffs. Installers, IT admins, and buyers should consider these potential drawbacks:

• Preview instability: The initial rollouts contain bugs that affect boot, login, and resume behavior. Relying on Insider builds in daily use is risky — updates can break workflows and require recovery steps.
• Security and login friction: Reports indicate some devices prompted for PINs or didn’t fully integrate with Windows Hello when booting into FSE. That can hamper the “appliance” feel and complicate hands‑off or kiosk‑style setups.
• Firmware and driver dependency: The benefits of FSE depend heavily on OEM firmware and updated drivers. Devices with immature driver stacks (particularly new silicon or GPU drivers) may not realize the promised performance improvements.
• Anti‑cheat and overlay compatibility: Games that rely on kernel‑level anti‑cheat or third‑party overlays may not work smoothly when background services are deferred or suppressed.
• App ecosystem fragmentation: Because FSE centers a chosen “home app,” users may find switching between non‑home apps less discoverable. Consumers who rely on multiple storefronts or launchers may need to adapt their habits.
• Enterprise and manageability concerns: IT administrators may need to adjust policies for managed devices — FSE changes startup app behavior and could interfere with corporate endpoint management expectations.
• Battery unpredictability: While FSE aims to prolong battery life by deferring background activity, real battery outcomes depend on thermal and power profiles, and aggressive gaming uses can still deplete large batteries quickly.

---

Practical guidance: when and how to try FSE on an MSI Claw​

For users who own an MSI Claw and are considering the FSE preview, follow a cautious, staged approach:

• Wait for a non‑Insider release if you want daily stability. Insider preview builds are for testing; they receive rapid updates but can break existing functionality.
• Back up profiles and create a recovery image before enabling FSE on a primary device. If something goes wrong with boot or PIN prompts, a recovery path avoids lengthy reinstallation.
• Update firmware and device drivers first — BIOS, GPU drivers, and vendor utilities should be on the latest firmware recommended by MSI before toggling FSE.
• Test with the apps you use (Steam, Xbox app, Epic, GOG). Verify that your favorite titles and overlays behave properly when FSE is enabled.
• If you encounter problems, disable FSE and report details to Microsoft and MSI. Insider builds are meant to gather diagnostics, so submit bug reports and use vendor recovery options if required.

These steps reduce the chance that a preview feature will leave your handheld in an unusable state.

---

OEM strategy and what this signals for handheld Windows​

Microsoft’s decision to build FSE and encourage OEM adoption is strategic rather than cosmetic. It suggests:

• A recognition that Windows on handhelds requires targeted UX changes to compete with handheld consoles and purpose‑built OSes.
• A pragmatic approach: rather than building a wholly new handheld OS, Microsoft is making Windows behave more like a console when the situation demands it.
• OEMs can use FSE as a product differentiator: shipping devices that boot into a console‑style experience may improve out‑of‑box impressions and lower support friction for consumer buyers.

Multiple OEMs have signaled interest in FSE beyond ROG and MSI. Lenovo has publicly said the Legion Go 2 will receive the Xbox‑style full‑screen mode on a coordinated timeline next year, and Microsoft has indicated additional OEM support in the months ahead. That broadening ecosystem strengthens FSE’s value proposition but also means Microsoft must support a wider variety of hardware and vendor utilities — increasing the risk surface for bugs and interoperability problems.

---

Developer, store, and anti‑cheat implications​

FSE has implications for several stakeholders in the Windows gaming ecosystem:

• Game developers should test titles under FSE to ensure overlays, controllers, and input mappings behave as expected. Controller discovery and remapping are central to handheld UX.
• Store owners and launcher developers will want to ensure their clients work smoothly as home apps or play nicely when not selected as the system launcher.
• Anti‑cheat vendors need to validate compatibility. Because FSE changes the set of processes allowed to auto‑start and can restrict certain background services, certain kernel or service hooks used by anti‑cheat may require vendor updates or exceptions to perform reliably.
• Middleware and overlay packages (streaming, capture, voice) must be tested across both FSE and standard desktop modes to ensure consistent behavior.

Microsoft’s approach leaves actual compatibility work to partners, so cross‑vendor coordination will determine how frictionless FSE becomes for mainstream gaming.

---

Accessibility and input​

FSE simplifies controller navigation, but accessibility is more than gamepad support. The Windows ecosystem still needs to ensure:

• Assistive technologies work in and out of FSE (screen readers, high contrast modes, magnifiers).
• Alternative input methods (e.g., touch, keyboard if docked) remain functional and discoverable from the hardware home screen.
• Customization of input mapping is accessible to players who require remapped controls or device‑specific profiles.

Microsoft and OEMs need to ensure FSE doesn’t inadvertently reduce accessibility in pursuit of a console aesthetic.

---

Final analysis — buyer and OEM checklist​

For buyers, reviewers, and OEMs, FSE is an interesting, practical step toward making Windows handhelds friendlier and closer in behavior to small‑form‑factor consoles. But the preview nature of the build and the variety of device hardware in the Windows ecosystem mean early adopters should temper expectations.
Key items to check before committing to FSE on an MSI Claw:

• Confirm your Claw model is listed as supported in the Insider build you run.
• Update BIOS, GPU, and vendor utilities to the versions recommended by MSI.
• Validate Windows Hello and login behavior when choosing to start FSE on boot.
• Try your most‑used games, and check overlays, streaming apps, and anti‑cheat compatibility.
• Keep recovery media and backups handy, and be prepared to roll back to a stable build if necessary.

For OEMs and Microsoft, the path forward requires attention to the subtle but critical integration points: login behavior, power management, sleep/resume reliability, driver maturity, and consistent Game Bar/Task View behavior. Getting those right will turn FSE from an intriguing optional mode into a compelling default for handhelds.

---

Outlook: does FSE hint at a handheld Windows OS?​

FSE is a pragmatic, stopgap solution that gives Microsoft and its partners breathing room. It lets vendors deliver a console‑like front end while preserving the deep flexibility of Windows for users who want it. That approach reduces fragmentation risks today, but if FSE succeeds and the ecosystem demands tighter optimizations, Microsoft may face pressure to build a more purpose‑built handheld OS in the future.
For now, FSE represents the critical middle ground: a way to make Windows handhelds feel less like mini‑PCs and more like consoles without breaking the Windows app model. If the implementation matures — and OEMs and game developers rally — FSE could be the standard launcher for handheld Windows gaming. If not, it will remain an optional mode that helps some users and frustrates others.

---

Microsoft’s preview arrival of FSE on MSI Claw devices is an important development for Windows handhelds: it delivers an Xbox‑style launcher and memory/power optimizations aimed squarely at improving handheld gaming usability. The benefits are real, but so are the short‑term risks. Users who prize a rock‑solid, daily‑driver experience should wait for wider availability and stable non‑Insider releases; early adopters who enjoy testing cutting‑edge UI changes will find plenty to try — and to report back — as Microsoft and OEMs iterate toward a more polished handheld experience.

---

Source: The Verge Microsoft releases an Xbox Full Screen Experience preview for the MSI Claw