XboxFullScreenExperienceTool unlocks the full handheld Xbox mode on any PC

The gap the tool exists to close

Microsoft has rolled out a limited PC edition of Xbox Mode, the full screen gaming experience, to regular PCs, and the readme puts the difference in a table. The Choose home app setting is available in the full handheld edition and missing in the limited PC edition. Auto-launch of the home app on startup is supported in one and not supported in the other. And the default rollout target is handhelds for the full edition and regular PCs for the limited one. The stated purpose of the tool is to enable the full handheld edition on any PC, which unlocks the home app selection and auto-launch behaviour the limited edition lacks. The readme adds a concrete reason to want it: if you use a custom home app such as OmniConsole, the full handheld edition is required, and OmniConsole boots straight into Steam Big Picture, Xbox, Epic, Armoury Crate SE, Playnite or anything else you add. So the audience is someone who has a controller and wants the console behaviour on hardware Microsoft never intended to support it.

Build numbers decide whether the tool will even start

The compatibility rule is stated precisely, and it is the first thing to check. The tool is compatible with Windows 11 24H2 builds 26100.7019 or later, and if your system does not meet the requirement the tool displays an error and exits. The readme then explains how to read a build number, with the instruction to look at the main build number before the dot, because the number after the dot is just a minor update revision. There is a native experience, recommended, which for desktops and laptops does not rely on a screen dimensions override via PhysPanelCS or PhysPanelDrv. It covers 26100.8328 or later, 26200.8328 or later, 26220.7271 or later, 26300.7674 or later, and 28020.1362 or later. The legacy experience covers 26100.7019 to 26100.8327, 26200.7015 to 26200.8327, and 28000.1450 or later, and on those builds desktops and laptops use a screen dimensions override instead. The example given is the trap most people fall into, since a build like 26100.1 is not compatible because its revision is lower than the required .7019, and the advice is to run Windows Update.

What the tool actually does to the system

The feature list is short and each item is a claim about behaviour rather than about marketing. The one-click toggle enables or disables Xbox Mode through a simple interface. An automatic system check verifies the Windows build for compatibility at startup, which is the mechanism behind the error described above. An automatic gamepad keyboard fix and touch simulation simulates touch input at system startup so the on-screen keyboard, including the PIN pad on the sign-in screen, is always ready and accessible via gamepad on a PC with no physical touchscreen. Device type emulation automatically simulates a handheld device type for activation on desktop or laptop systems, which is how the full edition is unlocked rather than the limited one. Convenience shortcuts give dedicated buttons for MS Store updates, Xbox Mode settings, startup apps and UAC settings. Automatic mode selection detects whether the machine is a desktop, a laptop or a handheld and offers the matching screen dimension override options. And the reversibility claim is backed by a mechanism, since backups of the original settings are created so restoration is possible.

The workflow is a restart, then a store update, then a settings toggle

The quick start is a three-part process, and the tool is distributed as an .msi installer so it can be installed, managed and removed cleanly. Preparing the system means downloading the latest .msi from the releases page, running the installer with administrator privileges, launching the tool from the desktop shortcut, clicking the Enable Xbox Mode button, accepting the restart confirmation, and then dealing with the touch question. That last part is the step worth understanding. The tool verifies the environment, and if no physical touchscreen is detected it prompts you to select Yes to enable touch simulation, so that the controller can operate the on-screen virtual keyboard properly. The PC restarts automatically to apply the changes. Then you launch the tool again and click the button to check the MS Store for Xbox updates, or open the Store yourself and go to Downloads or Library and run Check for updates, making sure both Xbox and Xbox Game Bar are fully updated. Finally the feature is enabled in Windows Settings. The tool's own documentation notes that you may need to repeat some of this, which is a fair description of how Windows feature activation tends to work.

The warnings are unusually prominent, and they should be read

The readme opens with a warning block, and the wording is worth taking at face value because this is a tool that patches deep parts of Windows. Using it means acknowledging and agreeing that the tool performs deep modifications to Windows and may cause instability, crashes, data loss, or require OS reinstallation. You are fully responsible for any consequences, and the developer provides no warranty, support or liability for damages. The tool is provided as is with no guarantee of stability, compatibility or functionality, and it may not work correctly on your specific configuration. Always back up your important data and create a system restore point before use. And it is an unofficial tool, not affiliated with, endorsed by or supported by Microsoft or Xbox. That last point is not boilerplate, because the tool works by convincing Windows that the machine is a handheld, and Microsoft has declined to ship that behaviour to desktops.

The repository shows the two halves of the project

The top level of the repository explains the shape of the solution. There is XboxFullScreenExperienceTool.sln as the Visual Studio solution, XboxFullScreenExperienceTool/ holding the application, Setup/ for the installer project, and Modules/ and PhysPanelCPP/ plus PhysPanelLib/ for the native components that handle the screen dimensions override, with .gitmodules indicating those parts are pulled in as submodules. Docs/ holds the documentation, and the two readme files, README.md and README.zh-TW.md, plus matching demo images, show the project is maintained bilingually. The C# and .NET 8 badge in the readme matches the primary language recorded for the repository. The PhysPanelCS and PhysPanelDrv names matter for the legacy path, because the readme says the native experience on desktops and laptops does not rely on the screen dimensions override through those components, while the legacy experience does, so the native components are only involved on the older builds.

Where this is the wrong choice

Three limits are worth naming. The first is the build dependency, which is a hard floor rather than a preference, since anything below the required revision is refused outright and the legacy path pulls in a screen dimensions override that changes how the desktop is presented to the system. The second is the risk profile, which the project itself quantifies in the warning block, and a machine that hosts work rather than games is a poor candidate for a tool that admits data loss and reinstallation are possible. The third is the support model. There is no warranty, no support commitment and no guarantee of compatibility, and the feature is the sort of thing that changes when Microsoft ships a build, since the tool has to keep pace with the operating system rather than with an API. What the tool does well is narrow and real: it removes a configuration gap that Microsoft deliberately left, and it does it reversibly, with backups and a disable path, which is more than the manual registry edits it replaces would have given you.

Editorial conclusion

XboxFullScreenExperienceTool suits a Windows 11 PC owner with a controller who wants the console-like layout and the missing home app picker, particularly if they run a custom launcher such as OmniConsole that needs auto-launch. It is the wrong tool if your machine is not on a supported build, since the tool refuses to run on anything below the required revision. It is also the wrong choice if you want a supported configuration, because the project states plainly that it is unofficial and not endorsed by Microsoft or Xbox. Before running it, check your build number the way the readme describes, since the revision after the dot decides compatibility, and create a restore point, because the tool warns that it performs deep modifications to Windows. The last push was on 2026-05-14 and the current release is v0.9.4 from the same day.

Frequently asked questions

Official sources

1. 8bit2qubit/XboxFullScreenExperienceTool on GitHub
2. Issues
3. License: GPL-3.0
4. README
5. Releases