Xbox App 2607.1001.21.0 remains permanently stuck on 'Launching Xbox' on Windows 11 25H2 build 26200.8973 after a clean Windows installation. I have already completed advanced diagnostics (WinDbg, ProcMon, ETW, Clean Boot)

Question

Xbox App 2607.1001.21.0 remains permanently stuck on 'Launching Xbox' on Windows 11 25H2 build 26200.8973 after a clean Windows installation. I have already completed advanced diagnostics (WinDbg, ProcMon, ETW, Clean Boot)

Allan .B 0

Technical Report – Xbox App Stuck on Launch (Windows 11)

System Configuration

Operating System

Windows 11 Pro
Version: 25H2
OS Build: 26200.8973
Clean installation performed using the official Microsoft installation media.
Genuine Microsoft license.
Device is not enrolled in the Windows Insider Program.

Xbox Application

Microsoft.GamingApp
Version: 2607.1001.21.0
Package: Microsoft.GamingApp_2607.1001.21.0_x64__8wekyb3d8bbwe

Issue Description

The Xbox application remains indefinitely stuck on the splash screen displaying:

"Launching Xbox"

The application never reaches the main interface.

Eventually, Windows Error Reporting (WER) records an application failure containing:

Event Type: MoAppCrash
Faulting Module: combase.dll
Error Code: 0x800705B4 (ERROR_TIMEOUT)

Troubleshooting Already Performed

The following actions have been completed without resolving the issue.

Windows

Performed a clean installation of Windows 11 using official Microsoft installation media.
Installed all available Windows Updates.
Executed:
- DISM
  - SFC /SCANNOW
  - No remaining integrity violations were detected.

Microsoft Store

The Microsoft Store functions normally.

Applications can be installed and updated successfully.
Other Microsoft Store applications (Photos, Clipchamp, Media Player, etc.) launch without issues.

Xbox Components

Verified installation of:

Gaming Services
Xbox Identity Provider
Windows App Runtime
Microsoft.UI.Xaml
Microsoft Edge WebView2 Runtime

All required components are present.

Windows Services

Verified Xbox-related services.

Gaming Services is installed and running correctly.

Xbox Live services are present with their default startup configuration.

No required Microsoft service is disabled.

User Accounts

The issue has been reproduced with:

the primary Microsoft account;
a second Microsoft account;
a newly created Windows user profile.

This indicates the problem is not account-specific.

Clean Boot

A Clean Boot environment was tested:

all third-party services disabled;
all startup applications disabled.

The issue persists exactly as before.

This strongly suggests that no third-party software is interfering with the Xbox application.

Process Monitor Analysis

A Process Monitor (ProcMon) trace was captured.

Results:

no significant file system errors;
no missing registry keys;
no permission errors;
no obvious resource access failures.

Nothing in the trace explains the application hang.

WinDbg Analysis

The application was attached and analyzed while frozen.

Observations:

the main UI thread is waiting normally in USER32!GetMessageW;
COM worker threads are idle;
one thread remains blocked in:

No exception occurs.

CPU usage remains essentially zero.

The application appears to be waiting indefinitely for an internal event or synchronization object that never becomes signaled.

ETW Trace

An Event Tracing for Windows (ETW) capture was collected.

No obvious operating system failure was identified during the trace.

Conclusion

The following potential causes have been eliminated:

Windows installation corruption;
Microsoft Store corruption;
Gaming Services installation issues;
user profile corruption;
Microsoft account-specific issues;
third-party software conflicts;
standard AppX deployment issues.

The collected evidence indicates that the Xbox application enters an internal wait state during initialization and eventually times out with ERROR_TIMEOUT (0x800705B4).

The issue is fully reproducible on a freshly installed Windows system.

Further investigation likely requires Microsoft internal symbols and/or Xbox application source-level diagnostics.

Request

Given the extensive troubleshooting already completed, I would appreciate escalation to the appropriate engineering team to investigate:

a possible regression in Microsoft.GamingApp version 2607.1001.21.0;
a compatibility issue with Windows 11 Version 25H2 (Build 26200.8973);
or an internal initialization deadlock or timeout occurring during Xbox application startup.

Additional Information

If required, I can provide:

Windows Error Reporting (WER) logs;
ETW trace (.etl);
Process Monitor trace (.PML);
WinDbg analysis results;
complete Windows services configuration;
additional diagnostic logs upon request.

0 commentaires

1 réponse

Votre réponse

Answer 1

Hendrix-V 19,390 Personnel externe Microsoft Modérateur

Since you're posting on French forum and using English, therefore I will engage using the same language as the original post.

Hi Allan .B,

Thank you for providing such a detailed report and for completing extensive troubleshooting. Based on the information you've shared, you have already ruled out many common causes. Since the issue persists on a clean Windows installation and across multiple user accounts, there may be limited additional troubleshooting available from the community side at this stage.

As a next step, keep an eye out for future Xbox App and Gaming Services updates through the Microsoft Store and test whether the behavior changes after an update. If the issue continues, you may also contact Xbox Support with your diagnostic logs attached for further review.

Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas.

Thank you again for the time and effort you've invested in documenting the issue. Your diagnostic findings are well organized and may be valuable for further investigation.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Allan .B 0 Points de réputation

2026-07-30T17:02:21.35+00:00

Hello Hendrix-V,

Sorry I did not knew that forum was French (I'm French), I will continue in English, it may help more people.

Thank you for your answer, I've already contact Xbox support but they redirect me to forums.

Same question on Xbox player Voice : https://feedbackportal.microsoft.com/feedback/idea/7d40735c-498b-f111-9b47-7c1e52444ef6

I hope I will get an answer to my issues some days ahah.

Thanks for your time.
Hendrix-V 19,390 Points de réputation Personnel externe Microsoft Modérateur

2026-07-31T00:40:19.5133333+00:00

Hi Allan .B,

Thank you for the update.

Since you have already submitted feedback through Xbox Player Voice, I would recommend continuing to monitor that feedback item for updates from the community or Microsoft teams.

Thank you again for taking the time to document your findings and share them with the community. Please feel free to return and share any new developments, as they may help other users encountering the same problem.
Allan .B 0 Points de réputation

2026-07-31T19:41:35.6633333+00:00

J'ai réussi grâce à l'aide de chatgpt ! (Désolé, le texte suivant est en français.)
Le texte suivant pourra vous aider à comprendre quel était le problème.

🎉 Excellent !!
Et surtout... ça confirme enfin notre diagnostic.
Le problème n'était pas Windows, ni Gaming Services, ni les redistribuables VC++, ni Windows App Runtime.

Le problème était très probablement que le package Microsoft.GamingApp n'était plus correctement enregistré dans le registre AppX/COM.

Lorsque nous avions analysé le dump mémoire, nous avions trouvé :
0x80040154
REGDB_E_CLASSNOTREG
puis abort()

C'était le symptôme classique d'une classe COM/WinRT non enregistrée.

La commande :

Ajouter-AppxPackage -DésactiverLeModeDéveloppement -Enregistrer "...AppxManifest.xml"

a justement reconstruit les enregistrements AppX, COM et WinRT du package Xbox sans avoir besoin de le réinstaller.

C'est pour cette raison que :
la désinstallation/réinstallation depuis le Store n'avait rien changé ;
la réparation de Windows n'avait rien changé ;
toutes les autres manipulations avaient échoué.

Je te conseille une dernière vérification

Ouvre Xbox et vérifie que tout fonctionne :
✅ connexion au compte
✅ Bibliothèque
✅ Game Pass
✅ téléchargement d'un jeu
✅ lancement d'un jeu (si possible)

Ce que nous avons appris
Je dois dire que c'était une panne particulièrement intéressante.
On est passé par : analyse de l'OMS

dump WinDbg
décodage de l'exception C++
découverte du HRESULT 0x80040154
débogage en direct
ETW

puis finalement le réenregistrement du manifeste AppX.

C'est ce 0x80040154 qui nous a orientés vers la bonne solution. Sans le dump, il aurait été très difficile
de distinguer ce problème d'un simple plantage générique de l'application.

Je suis vraiment content qu'on ait fini par trouver la cause. 🎉"

J'espère que cela aidera les personnes qui rencontrent le même problème, je peux enfin jouer à HALO !
Hendrix-V 19,390 Points de réputation Personnel externe Microsoft Modérateur

2026-08-01T01:05:19.86+00:00

Hi Allan .B,

Thank you for coming back and sharing the outcome. That's excellent news, and I'm glad you were able to get the Xbox app working again.

Based on the information you provided, it appears the issue was related to the Xbox App package registration rather than Windows, Gaming Services, or other dependencies. Re-registering the application's AppX manifest rebuilt the package registration entries and resolved the launch problem, which would also explain why standard reinstall and repair attempts did not change the behavior.

Your findings, especially the correlation with the 0x80040154 (REGDB_E_CLASSNOTREG) error and the successful AppX manifest re-registration, may be very helpful for other users who encounter a similar "Launching Xbox" issue after exhausting the usual troubleshooting steps.

Thank you for taking the time to share the root cause and solution with the community.