When the Microsoft Store in Windows 10 or Windows 11 repeatedly prompts you to sign in, rejects a working Microsoft account password, or hangs on a blank or spinning login window, the failure almost always stems from one of three local issues: a corrupted Store cache, damaged app package state, or stale authentication tokens stored in Windows Credential Manager and the Web Account Manager (WAM) TokenBroker cache. You can resolve the issue without reinstalling Windows by running wsreset.exe to flush the Store cache, repairing or resetting the Microsoft Store app package through Windows Settings, and purging expired MicrosoftAccount entries in Credential Manager while verifying that core Windows authentication services are running. These steps apply to all editions of Windows 11 and Windows 10 (version 15063 and later; note that Windows 10 reached end of free mainstream support on October 14, 2025, though its Store and account architecture still follow these exact paths).

A Windows laptop displays an account sign-in transition, with icons suggesting cleanup, settings, and key recovery. Prerequisites and Pre-Flight Checks​

Before clearing local caches or altering saved credentials, rule out external account or network blockers that prevent Windows from validating your identity tokens with Microsoft's authentication servers:

  • Verify your account in a web browser: Open a private or Incognito browser window and sign in to your Microsoft account dashboard on the web. If your account is locked, requires a security challenge, or has a pending terms-of-service prompt, the Microsoft Store app cannot complete its background token exchange until you clear that prompt in a browser.
  • Confirm system clock and time zone synchronization: Token-based authentication (OAuth and Web Account Manager) fails immediately if your PC clock drifts by more than a few minutes from Coordinated Universal Time (UTC).
    • Windows 11: Open Start > Settings > Time & language > Date & time. Ensure Set time automatically and Set time zone automatically are toggled On, then click Sync now under Additional settings.
    • Windows 10: Open Start > Settings > Time & Language > Date & time. Turn On both Set time automatically and Set time zone automatically, then click Sync now under Synchronize your clock.
  • Disable active proxies or split-tunnel VPNs temporarily: The Microsoft Store uses Windows HTTP Services (WinHTTP) and background delivery optimization services that frequently fail when a third-party VPN or local proxy intercepts traffic. Turn off any active VPN client before starting the procedure.
  • Administrator access: Clearing the Store cache and repairing the Store app work from a standard user account, but restarting Windows services or re-registering system packages in PowerShell requires an account with local administrator privileges.

Step 1: Clear the Microsoft Store Cache with WSReset​

The fastest non-destructive fix is flushing the local Store cache using Microsoft's built-in Windows Store Reset utility (wsreset.exe). This tool clears cached storefront assets and temporary session cookies without deleting your installed apps or signing you out of Windows.

  1. Close the Microsoft Store app completely if it is open.
  2. Press Windows Key + R on your keyboard to open the Run dialog box.
  3. Type wsreset.exe into the Open field and click OK (or press Enter).
  4. A blank Command Prompt window (C:\Windows\System32\WSReset.exe) will open with a blinking cursor and no text. Do not close this window; leave it running for about 10 to 30 seconds while it clears the local cache directories.
  5. Wait for the Command Prompt window to close automatically. As soon as it finishes, the Microsoft Store app will launch on its own.
  6. Click the Profile icon in the top-right corner of the Microsoft Store window, select Sign in (or select your account if listed), and test whether the login prompt completes.

If wsreset.exe throws an error or the Store still loops back to an unauthenticated state after you enter your credentials, proceed to Step 2.

Step 2: Repair or Reset the Microsoft Store App in Windows Settings​

When wsreset.exe only clears temporary data and leaves damaged configuration files or a corrupted local database behind, use the built-in Windows app repair and reset controls. Repair attempts to fix the app package while preserving local preferences; Reset wipes the app's local data directory (%LocalAppData%\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe) and returns the Microsoft Store app to its clean first-run state without uninstalling any apps or games you previously downloaded from the Store.

On Windows 11​

  1. Press Windows Key + I to open Settings.
  2. In the left sidebar, select System, then click SystemComponents (on Windows 11 22H2 with late-2023 updates, 23H2, 24H2, and later) or go to Apps > Installed apps on earlier Windows 11 releases where Microsoft Store appears directly in the main app list.
  3. Locate Microsoft Store in the list (use the Search apps box at the top if needed).
  4. Click the three-dot More options button (...) on the right side of the Microsoft Store entry and select Advanced options.
  5. Scroll down to the Reset section.
  6. Click Repair first. Wait a few seconds until a checkmark appears next to the Repair button.
  7. Launch the Microsoft Store and test signing in.
  8. If the sign-in problem persists, return to the same Advanced options page, click Terminate to stop all background Store processes, and then click Reset. Read the confirmation prompt and click Reset again. Wait for the checkmark to appear next to the button.

On Windows 10​

  1. Press Windows Key + I to open Settings.
  2. Select Apps, ensuring Apps & features is selected in the left navigation pane.
  3. In the Search this list box under Apps & features, type Microsoft Store.
  4. Click Microsoft Store in the results list to expand it, then click the Advanced options link.
  5. Scroll down to the Reset section and click Repair. Wait for the progress indicator to finish and display a checkmark next to Repair.
  6. Open the Microsoft Store and attempt to sign in.
  7. If sign-in still fails, return to Advanced options, click Terminate at the top of the section, scroll down, click Reset, and confirm by clicking Reset in the pop-up confirmation box.

Step 3: Remove Outdated Saved Credentials in Windows Credential Manager​

When you change your Microsoft account password, update two-factor authentication methods, or switch between local and Microsoft accounts, Windows Credential Manager can retain expired identity tokens. When the Microsoft Store requests a session token, Windows may pass the cached, invalid credential instead of prompting for a fresh token, causing silent sign-in drops or repeated password prompts.

Warning: Only remove credentials specifically tied to MicrosoftAccount or SSO_POP tokens as instructed below. Deleting unrelated entries under Windows Credentials or Generic Credentials can remove saved logins for network file shares, Remote Desktop connections, Git repositories, or third-party applications. If you want a full safety net before editing credentials, you can click Back up Credentials at the top of the Windows Credentials view to save an encrypted backup file, though note that Windows only backs up traditional Windows credentials and cannot export dynamic cloud session tokens.
  1. Close the Microsoft Store app and any open Microsoft 365 or Xbox apps.
  2. Click the Search box on the taskbar (or press Windows Key + S), type credential manager, and select Credential Manager (Control Panel) from the results.
  3. Click the Windows Credentials tile (the right-hand icon at the top of the window).
  4. Scroll down to the Generic Credentials section at the bottom of the list.
  5. Look for entries that begin with any of the following prefixes:
    • MicrosoftAccount:user= (followed by your email address)
    • MicrosoftAccount:target=SSO_POP_Device
    • SSO_POP_User or SSO_POP_Device
    • Xbl| or XblGrts| (if your Store sign-in failure also affects the Xbox app or gaming services)
  6. Click the drop-down arrow on the right side of the first matching MicrosoftAccount entry to expand its details.
  7. Click Remove, then click Yes in the Delete Generic Credential confirmation dialog box.
  8. Repeat this step for any remaining MicrosoftAccount:user= entries associated with the email address that cannot sign in to the Store.
  9. Restart your PC. A full restart forces the Windows Web Account Manager (TokenBroker) service to discard in-memory authentication tokens and request a clean sign-in session after reboot.

Verification of Success​

After your PC restarts, verify that the Store sign-in token and license acquisition pipeline are working properly:

  1. Open Start and launch Microsoft Store.
  2. Click the Profile circle in the top bar (to the left of the minimize button) and click Sign in.
  3. If your Windows user profile is already linked to a Microsoft account, select that account in the Sign in dialog and click Continue. If you use a local Windows account, select Microsoft account (or Use a different account), enter your email address and password, and complete any multi-factor authentication prompt.
  4. Confirm that your profile picture or initials now remain visible in the top-right corner of the Store window without reverting to the generic user icon.
  5. Click Library in the bottom-left corner of the Microsoft Store window, then click Get updates. If the Store checks for updates and begins downloading or reports that your apps are up to date without asking you to sign in again, both identity authentication and Store licensing are functioning normally.

Alternate Method: Clear the Web Account Manager (TokenBroker) Cache and Re-Register the Store​

If Credential Manager cleanup and app resets do not stop the sign-in loop, the underlying Web Account Manager (WAM) plugin cache—which handles the modern dark/light gray sign-in pop-up window (Microsoft.AAD.BrokerPlugin and Microsoft.Windows.CloudExperienceHost)—may be corrupted, or the Store package registration itself may be broken.

Warning: Clearing the TokenBroker cache signs you out of current background sessions for the Microsoft Store, Xbox app, and other UWP apps that rely on Web Account Manager, requiring you to click Sign in once inside those apps afterward. It does not delete your Windows user profile or local files.

Clear the TokenBroker Cache​

  1. Close the Microsoft Store app.
  2. Press Windows Key + R to open the Run dialog box.
  3. Type %localappdata%\Microsoft\TokenBroker\Cache and click OK.
  4. If the folder opens and contains .tbres cache files, press Ctrl + A to select all files in the Cache folder and press Delete. (If Windows reports that a file is in use, skip that file or run net stop TokenBroker from an elevated Command Prompt first, delete the files, and restart your PC.)

Re-Register the Microsoft Store Package in PowerShell​

  1. Right-click the Start button and select Terminal (Admin) on Windows 11, or Windows PowerShell (Admin) on Windows 10. Click Yes at the User Account Control (UAC) prompt.
  2. Copy and paste the following command into the administrator PowerShell window and press Enter:
    Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  3. Wait a few seconds for the yellow deployment progress banner at the top of the PowerShell window to disappear and return you to the command prompt without red error text.
  4. Restart your computer and open the Microsoft Store.

Troubleshooting Common Failure Modes and Rollback​

If you still cannot sign in after completing the primary procedure and alternate method, match your specific error code or symptom to the targeted fixes below.

Sign-In Window Opens Blank, Flashes and Closes Immediately, or Shows Error 0x80070422​

Error 0x80070422 (or a sign-in box that flashes on screen and immediately vanishes) indicates that one or more background Windows services required for Microsoft account authentication are disabled in the Service Control Manager.

  1. Press Windows Key + R, type services.msc, and click OK.
  2. Scroll through the Services (Local) list and check the Startup Type and Status for each of these four services:
    • Microsoft Account Sign-in Assistant (wlidsvc)
    • Web Account Manager (TokenBroker)
    • Windows License Manager Service (LicenseManager)
    • Microsoft Store Install Service (InstallService)
  3. If any of these services shows a Startup Type of Disabled:
    • Double-click the service to open its Properties window.
    • Change Startup type from Disabled to Manual (Trigger Start).
    • Click Apply, then click Start to launch the service immediately, and click OK.
  4. Retry signing in to the Microsoft Store.

Windows Profile Shows "Verify" or "Fix Now" Banner in Account Settings​

If your Windows login itself is signed in with a Microsoft account whose token has expired system-wide, the Microsoft Store cannot override the broken OS-level token.

  • Windows 11: Go to Start > Settings > Accounts > Your info and Accounts > Email & accounts. If you see a prompt asking you to Verify your identity or fix a shared experiences account error, click Verify and complete the authentication prompt.
  • Windows 10: Go to Start > Settings > Accounts > Your info. If you see a Verify link under your account details, click it and follow the on-screen sign-in steps. Also check Settings > System > Shared experiences; if it says Some of your accounts require attention, click Fix now.

Error 0x80131500 or 0x80072EE7 When Attempting to Sign In​

These errors indicate that WinHTTP or TLS settings are blocking the Store from reaching Microsoft's login endpoints, even when your web browser works normally.

  1. Press Windows Key + R, type inetcpl.cpl, and click OK to open Internet Properties.
  2. Click the Connections tab, then click LAN settings.
  3. Ensure Automatically detect settings is checked and Use a proxy server for your LAN is unchecked (unless your corporate network requires one), then click OK.
  4. Click the Advanced tab inside Internet Properties, scroll to the bottom of the Settings list, and ensure Use TLS 1.2 and Use TLS 1.3 (if present) are checked. Click Apply and OK.

Run the Built-In Windows Store Apps Troubleshooter (Windows 10 and Earlier Windows 11 Builds)​

  • Windows 10: Open Start > Settings > Update & Security > Troubleshoot > Additional troubleshooters, select Windows Store Apps, and click Run the troubleshooter.
  • Windows 11: Open Start > Settings > System > Troubleshoot > Other troubleshooters. On Windows 11 22H2 and earlier, locate Windows Store Apps and click Run. Note that on newer Windows 11 releases where Microsoft has transitioned legacy MSDT troubleshooters to the Get Help app, clicking Get Help runs an automated Microsoft Store diagnostic and cache reset directly inside the support window.

Restoring or Rolling Back Account Changes​

  • Restoring backed-up credentials: If you created a credential backup before Step 3 and need to restore a deleted entry, open Credential Manager > Windows Credentials, click Restore Credentials, browse to your saved .crd backup file, press Ctrl + Alt + Delete as prompted by the secure desktop, and enter the backup password.
  • Switching Store accounts cleanly without affecting your Windows login: If the Store automatically signs you in with the wrong Microsoft account after a reset, click your Profile icon in the top-right corner of the Microsoft Store, click Sign out, then click the Profile icon again, select Sign in, and choose Use a different account so only the Store app uses the alternate Microsoft account while your main Windows user profile remains untouched.