Microsoft / Xbox sign-in modal crashes and closes immediately (Minecraft Launcher, MS Store, Xbox App)

Question

Microsoft / Xbox sign-in modal crashes and closes immediately (Minecraft Launcher, MS Store, Xbox App)

Chromisek 0

Hello,

I am experiencing a critical issue with Microsoft Account authentication across Windows 11. Whenever I attempt to sign in via the Minecraft Launcher, Xbox App, or Microsoft Store, the authentication modal (Web Account Manager / WebView) pops up for about half a second (rendering as a blank grey window) and immediately crashes/closes without throwing any visible error code.

Troubleshooting steps already performed without success:

PC restarted; Minecraft Launcher and Gaming Services reinstalled (via PowerShell).

Repaired and reset Xbox App, Microsoft Store, and Gaming Services in Windows Settings.

Cleared all Xbox/Xbl credentials from Windows Credential Manager.

Verified relevant Windows services (Xbox Live Auth Manager, Microsoft Account Sign-in Assistant, and Gaming Services are all running).

Ran DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow.

Disabled third-party antivirus web protection and disconnected any VPN/proxy services.

The issue appears to be a crash within the WAM TokenBroker or the UI container responsible for rendering the sign-in modal. How can I repair this system authentication broker without having to perform a full clean install of Windows?

Počet komentářů: 0

1 odpověď

Vaše odpověď

Answer 1

Ian-T 13,360 Externí zaměstnanci Microsoftu Moderátor

Please note that this is Czech Q&A Forum, any threads should be posted in Czech. However, I will still provide an answer in English based on your initial response.

Hi @Chromisek

Since the sign-in window crashes in the Minecraft Launcher, Xbox app, and Microsoft Store, this points to a damaged Windows authentication component rather than an individual app.

First, open Windows Terminal or PowerShell as Administrator and re-register the personal Microsoft account sign-in package:

if (-not (Get-AppxPackage Microsoft.Windows.CloudExperienceHost)) {
 Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\AppxManifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown
}
Get-AppxPackage Microsoft.Windows.CloudExperienceHost

Then restart the Token Broker service from an elevated Command Prompt:

net stop TokenBroker
net start TokenBroker

Restart Windows and test the Store sign-in first.

If the window still closes immediately, test from a newly created local Windows user account. If sign-in works there, the original Windows profile is likely corrupted.

If it fails in the new profile as well, use Settings > System > Recovery > Fix problems using Windows Update > Reinstall now. This reinstalls the current Windows version and repairs system components while preserving installed apps, files, and settings, so it is not a clean installation.

I hope this helps, please feel free to give me an update

Ian-T 13,360 Reputační body Externí zaměstnanci Microsoftu Moderátor

2026-09-13T23:35:25.0166667+00:00

Hi @Chromisek

Just checking in to see if my answer helps, please feel free to let me know if you need any further assistace
Chromisek 0 Reputační body

2026-10-02T19:22:32.9966667+00:00
Hi,

Thanks for the suggestions! I went through the steps you mentioned, along with several other diagnostic fixes, but unfortunately the issue still persists. The auth dialog (Microsoft.AccountsControl / TokenBroker) still flashes white for ~500ms and immediately crashes when attempting to sign in via Microsoft Store, Xbox app, or Windows Settings.

Here is a summary of what was attempted on the affected profile:

Re-registered Microsoft.Windows.CloudExperienceHost via PowerShell (completed successfully with status OK) and restarted the TokenBroker service via Command Prompt.

Verified all core Xbox/auth services (XblAuthManager, XblGameSave, XboxNetApiSvc) are running and set to Automatic.

Re-registered Microsoft.AccountsControl and Microsoft.AAD.BrokerPlugin packages.

Cleared the TokenBroker account cache and IdentityCRL registry keys.

Backed up and removed the DPAPI SID folders inside %APPDATA%\Microsoft\Protect to force recreation of the user cryptographic vault.

Result:

None of these steps resolved the crash on the current user profile.

However, as a test, I created a brand-new local Windows user account, and modern authentication works flawlessly there (Microsoft Store, Xbox app, and system settings sign-in modals open and function normally).

This confirms the issue is isolated to corruption within my specific Windows user profile (likely user registry/NTUSER.DAT or profile-specific cryptographic bindings) rather than a system-wide OS failure.

At the moment, I prefer to keep my single primary profile and do not want to migrate to a new account just yet. If there are any deeper PowerShell, registry, or identity-repair commands that can fix this within the existing profile without a full profile migration, please let me know.

Thanks again!
Ian-T 13,360 Reputační body Externí zaměstnanci Microsoftu Moderátor

2026-10-03T23:17:15.9433333+00:00

Hi

Thank you for the detailed update. Since the sign-in window works correctly in the new Windows account, this confirms that the Windows installation and Microsoft services are functioning, and that the problem is isolated to the original user profile.

You have already reset the relevant WAM packages, caches, registry entries, and DPAPI data. At this stage, I would not recommend further registry or identity-store deletion, as there is no reliable supported command that can guarantee repair of deeper NTUSER.DAT or profile-specific permission corruption.

Before migrating profiles, the remaining supported repair option is:

Settings > System > Recovery > Fix problems using Windows Update > Reinstall now

This reinstalls the current Windows version while preserving installed applications, personal files, and settings. After it finishes, test the sign-in window again in the original profile.

If the issue remains afterward, moving to the working profile would unfortunately be the safest supported resolution. Microsoft’s guidance for a corrupted profile is to create a new account and copy the personal files from the old profile, rather than continuing to modify protected identity data manually.