Quick fix: Run wsreset.exe from Run dialog to clear Store cache, then open Microsoft Store and sign in fresh. If the error persists, sign out of the Microsoft account in Settings → Accounts → Email & accounts and sign back in to refresh the credential token.
Microsoft Store says “Invalid credentials” or “The account credentials you provided are incorrect” — even though you can sign in to account.microsoft.com fine. The Store’s cached credential token is stale or corrupted. A cache reset usually fixes it.
Affects: Windows 11 (and Windows 10) Microsoft Store.
Fix time: ~10 minutes.
What causes this
Microsoft Store caches credentials separately from Windows sign-in. The Store’s cache can go stale after: password changes (you changed the password on another device), Microsoft account security policy changes, expired authentication tokens, or Store package corruption. The fix is to clear the cache and re-acquire fresh tokens.
Method 1: Reset Store cache and re-sign-in
The standard fix.
- Press
Win + R, typewsreset.exe, press Enter. - A blank Command Prompt appears for ~30 seconds. Wait. Microsoft Store opens automatically.
- If Store prompts to sign in, enter your Microsoft account credentials.
- If “Invalid credentials” appears again, try the same password you use at account.microsoft.com.
- For 2FA-enabled accounts, complete the verification challenge.
- Sign-in should succeed.
This is the simplest fix.
Method 2: Sign out from Windows accounts and refresh
When Method 1 doesn’t resolve.
- Open Settings → Accounts → Email & accounts.
- Find your Microsoft account in the list (used by apps).
- Click it → Remove. Confirm.
- Sign out of any other Microsoft account if present.
- Open Settings → Accounts → Your info. If the account here is also a Microsoft account, you may need to sign out, but this signs you out of Windows entirely — typically not required.
- Open Microsoft Store. Click your profile icon. Sign in.
- Enter your Microsoft account. Verify any 2FA prompts.
- Sign-in should now succeed.
This forces fresh credential acquisition.
Method 3: Re-register the Microsoft Store package
For persistent failures after Methods 1 and 2.
- Open Terminal (Admin).
- Re-register Microsoft Store:
Get-AppxPackage *WindowsStore* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppxManifest.xml"} - Restart the Microsoft Store install service:
net stop InstallService net start InstallService - Reset Microsoft Store via Settings: Settings → Apps → Installed apps → Microsoft Store → Advanced options → Reset.
- Reboot.
- Open Store and sign in again.
This rebuilds Store state from scratch while preserving sign-in info at the Windows level.
How to verify the fix worked
- Microsoft Store loads with your profile picture and name displayed.
- Try downloading or updating an app — proceeds without sign-in errors.
- Run
Get-AppxPackage Microsoft.WindowsStore | Select Statusin PowerShell. Status: Ok.
If none of these work
If sign-in continues failing, three causes apply. Account is locked or compromised: visit account.microsoft.com in browser, sign in, check for security alerts. Microsoft may have temporarily locked the account if it detected unusual activity. Date/time wrong: authentication tokens are time-sensitive. Confirm Windows date/time is accurate. Region mismatch: if your Microsoft account is registered in one country but Windows is set to another, sign-in may fail. Settings → Time & language → Region should match the country your account is registered to. For corporate-managed PCs where personal Microsoft accounts are restricted, contact IT.
Bottom line: Store sign-in fails because of cached credential corruption — wsreset.exe clears it. If that doesn’t work, sign out Microsoft account from Windows and sign back in fresh.