Xbox App Will Not Launch on Windows PC After Extensive Troubleshooting (Including In-Place Upgrade)

Question

Xbox App Will Not Launch on Windows PC After Extensive Troubleshooting (Including In-Place Upgrade)

Thiago Fontinelli 5

I am contacting support regarding a critical issue where the Xbox app on my Windows PC will not launch at all. The app is 100% installed on my system, but when I try to open it, absolutely nothing happens. No window appears, no error message is displayed, and the app just fails silently.

As a monthly Xbox Game Pass subscriber, I am currently paying for a service that I am completely locked out of due to this software failure. This is not just a minor glitch; it is a fundamental breakdown of a core Microsoft application within its own native operating system.

To save time and avoid standard, repetitive troubleshooting loops, please do not suggest generic tier-1 solutions such as running wsreset, checking time zones, or clearing temporary files. I have already performed extensive, advanced diagnostics to isolate this issue before opening this ticket. Here is exactly what has already been done:

I cleanly reinstalled the Xbox app using Windows Package Manager (winget).

I cleared Windows Credential Manager tokens associated with Xbox (Xbl).

I ran PowerShell commands to re-register Windows AppX packages.

I performed a full Windows In-Place Upgrade using the official ISO.

Think about how absurd this is: Even a full Windows repair install failed to fix this. The app is sitting right there on my drive, but the operating system completely refuses to execute it. It is unacceptable that a core Microsoft application can break so fundamentally within its own OS.

The Microsoft Store works perfectly and other features work normally. The problem is isolated specifically to the Xbox app execution failing silently.

Since your own system upgrade couldn't fix this mess, I need a real solution from an actual engineer who can explain why this runtime is dead and how to force it to open. Fix your software. I am tired of paying for a broken ecosystem.

Thiago Fontinelli 5 Reputation points

2026-06-01T02:23:11.55+00:00

I have successfully captured the silent launch failure using Process Monitor (ProcMon) with the correct process filters, and the root cause has been fully isolated. This is not a permission issue or a standard deployment failure; the application is suffering a fatal runtime crash immediately upon execution.

According to the log analysis, the application attempts to load the native Windows UI library (C:\Windows\System32\Windows.UI.Xaml.dll), triggers a registry query for UsePrivateHeap, and immediately invokes WerFault.exe (Windows Error Reporting).

The process then terminates abruptly with the following parameters:

Process: XboxPcApp.exe

Trigger: C:\Windows\System32\Windows.UI.Xaml.dll

Exit Status: -1073740791 which translates directly to NTSTATUS 0xC0000409 (STATUS_STACK_BUFFER_OVERRUN).

This proves that the application package is executing, but a critical stack buffer overrun occurs during the XAML user interface initialization layer, forcing the operating system to terminate the process before a single frame or error UI can be rendered.

Since an In-Place Upgrade preserves system states and user registries, this specific memory corruption has survived the OS repair. I have attached the full CSV log. Please escalate this packet to a tier-3 engineering team capable of diagnosing why the current build of XboxPcApp.exe is triggering a stack buffer overrun against the native Windows 11 XAML subsystem. I expect a structural fix, not generic tier-1 scripts.

Answer recommended by moderator

0 additional answers

Your answer

Thiago Fontinelli 5 Reputation points

2026-06-01T02:23:11.55+00:00

I have successfully captured the silent launch failure using Process Monitor (ProcMon) with the correct process filters, and the root cause has been fully isolated. This is not a permission issue or a standard deployment failure; the application is suffering a fatal runtime crash immediately upon execution.

According to the log analysis, the application attempts to load the native Windows UI library (C:\Windows\System32\Windows.UI.Xaml.dll), triggers a registry query for UsePrivateHeap, and immediately invokes WerFault.exe (Windows Error Reporting).

The process then terminates abruptly with the following parameters:

Process: XboxPcApp.exe

Trigger: C:\Windows\System32\Windows.UI.Xaml.dll

Exit Status: -1073740791 which translates directly to NTSTATUS 0xC0000409 (STATUS_STACK_BUFFER_OVERRUN).

This proves that the application package is executing, but a critical stack buffer overrun occurs during the XAML user interface initialization layer, forcing the operating system to terminate the process before a single frame or error UI can be rendered.

Since an In-Place Upgrade preserves system states and user registries, this specific memory corruption has survived the OS repair. I have attached the full CSV log. Please escalate this packet to a tier-3 engineering team capable of diagnosing why the current build of XboxPcApp.exe is triggering a stack buffer overrun against the native Windows 11 XAML subsystem. I expect a structural fix, not generic tier-1 scripts.

Answer 1

RESOLVED — Root cause identified and fixed locally. Posting for anyone who hits the same wall.

Update: I solved this myself. Sharing the actual cause and fix here, since no tier-1 script would ever have found it.

What it really was

The 0xC0000409 is not a random memory corruption, as I first assumed. On modern Windows 11, this NTSTATUS is a controlled security fast-fail — the app deliberately terminates itself when an integrity or dependency check fails during startup. It only looked like the app was "dying at the XAML layer" because that's the exact moment the WinAppSDK runtime bootstrapper initializes.

The Xbox app (Microsoft.GamingApp) depends on WindowsAppRuntime 1.8. That framework package was present and healthy. But its mandatory companion packages — MicrosoftCorporationII.WinAppRuntime.Main.1.8 and ...Singleton — were stuck in a broken state: PackageOffline, DataOffline, NotAvailable, and pinned to an older build (8000.675.1142.0) than the framework the app required (8000.859.21.0).

So on every launch, the bootstrapper tried to compose the runtime, found its companion packages registered-but-unavailable, and fast-failed before a single frame could render. No window, no error dialog, nothing in Event Viewer. Completely silent.

Why none of the "official" fixes worked

This is the part worth flagging. Reinstalling the app didn't help, because the app was never the problem. Re-registering AppX packages didn't help, because the broken companion packages stayed registered in their offline state. And — most absurd of all — the In-Place Upgrade didn't help, because it preserves the existing package registrations and quietly carried the orphaned, broken runtime packages straight across the repair. The repair install rebuilt almost everything except the one thing that was actually broken.

The fix

Remove the broken companion packages so the system can no longer reference them in their dead state, then let the runtime bootstrapper re-provision a clean, consistent set on next launch. Once the corrupted Main and Singleton packages were gone and the framework was left clean at a single consistent version, the Xbox app opened on the very first try.

The note to Microsoft

I'll be honest: it's a poor look that a paying Game Pass subscriber had to capture a ProcMon trace, decode an NTSTATUS code, and manually surgery the WinAppSDK dependency chain to open a first-party app — on Microsoft's own OS. A broken companion package leaving an app to fail completely silently, with nothing in Event Viewer and surviving a full In-Place Upgrade, is a serious diagnosability gap. At minimum, the runtime should surface a real error when its companion packages are unavailable, instead of fast-failing into a void. The platform clearly has the information; it just throws it away.

Leaving this here for the next person who finds themselves staring at a silent XboxPcApp.exe wondering if they're losing their mind. You're not. Check your WindowsAppRuntime companion packages.

Alex-L 7,060 Reputation points Microsoft External Staff Moderator

2026-06-02T08:43:18.5833333+00:00

Hi Thiago Fontinelli

Thanks for coming back and sharing the resolution!

That level of detail is extremely helpful for anyone hitting the same silent launch issue. From what you outlined, this clearly wasn’t a typical Xbox app or Gaming Services problem, but a dependency failure within the Windows App Runtime where the companion packages were left in an inconsistent offline state. That explains why the app fast‑failed with no UI and why standard steps like reinstalling the app, re-registering packages, or even an in-place upgrade didn’t help, since those methods preserved the broken registrations. Your approach of removing the invalid WinAppRuntime companion packages so the runtime could re‑provision clean dependencies is a solid diagnosis and fix, and it’s a useful reference point for similar cases going forward.

I’ll also recommend your answer so that others encountering this issue can more easily find this resolution.

Have a great day!

Share via

Xbox App Will Not Launch on Windows PC After Extensive Troubleshooting (Including In-Place Upgrade)

0 additional answers

Your answer