Microsoft Store login problem: sign-in fails and what to do
A Microsoft Store login problem usually means the account in Windows doesn’t match the one you want, the Store has stale cached sign-in data, Windows’ clock or network is off, or the app itself is glitching. Start with the safest checks first: confirm the account works outside the Store, make sure Windows time and network are correct, then clear the Store cache if needed. If the account fails on the web too, stop troubleshooting the app and use Microsoft’s current account recovery or verification flow.
What usually causes a Microsoft Store login problem
The most common cause is an account mismatch. The Store may be trying to use a different Microsoft account than the one you expect, especially after a password change, after switching accounts, or when a work or school account is involved.
Cached credentials are another common cause. The Store can keep stale sign-in data and get stuck even when your password is correct.
App glitches can also block sign-in. If the Store opens but keeps rejecting your login or loops back to the sign-in screen, the app may have a broken session or cache.
Date and time problems can break sign-in checks. If Windows has the wrong clock or time zone, secure sign-in can fail before the Store finishes authenticating.
Network issues can cause the same symptom. VPNs, proxies, captive Wi-Fi portals, DNS problems, or a blocked connection can stop the Store from reaching Microsoft’s sign-in service.
Work, school, family, and region settings can add another layer. A managed device may restrict the Store or the type of account it accepts, family settings can limit purchases or access, and region settings can affect what the Store allows for that account and location.
Before you start
- Make sure you know which Microsoft account you want the Store to use.
- If you have more than one Microsoft account, be careful not to test the wrong one in the browser and the Store.
- Have a way to restart Windows if needed.
- If this is a work or school device, expect organization policies to override local fixes.
- If you recently changed your password or completed account recovery, use the updated credentials everywhere.
- If the account is locked, challenged, or waiting for verification, local Store fixes will not finish the sign-in for you.
The quickest fixes to try first
- Check which account the Store is using.
Open the Microsoft Store and look at the profile area. If the wrong account is signed in, sign out and sign back in with the Microsoft account you actually want tied to purchases and downloads. If you recently changed your password, use the new one, not anything saved in an old prompt or browser.
- Confirm the account works outside the Store.
Sign in to your Microsoft account in a browser. If that sign-in fails too, the problem is with the account, not the Store app. Use Microsoft’s current account recovery or verification flow before you keep troubleshooting Windows.
If the browser sign-in works, the account itself is probably fine and the problem is local to Windows or the Store.
- Rule out a network or portal problem.
Turn off VPN or proxy software and try again on a normal connection. If you are on public Wi-Fi or a network that needs browser sign-in, finish that network sign-in first. If the Store only fails on one network, the connection is part of the problem.
- Sync Windows date and time.
Open Date & time settings and make sure the clock, time zone, and automatic time sync are correct. A wrong clock can block secure sign-in even when the password is right. After you fix the time, close and reopen the Store.
- Sign out and back in.
Sign out of the Microsoft Store, then sign in again with the same account you confirmed in the browser. If another Microsoft account is already signed in elsewhere on the PC, that can confuse the session. Keep the account consistent across Windows, the browser, and the Store.
- Clear the Store cache.
Use the Store reset command to clear cached Store data without removing the app itself.
wsreset.exeWhen the reset finishes, the Store should reopen. If it now accepts your sign-in, the issue was likely a broken cache or stale session data.
- Install pending Windows updates and restart.
If Windows has pending updates, install them, restart, and try again. Store sign-in problems can come from system components that only get fixed through Windows Update. If the problem started right after an update, a restart is still worth trying before you move on.
- Check for work, school, family, or region restrictions.
If this is a managed work or school device, ask the device admin whether the Store is allowed and whether the account type is supported. If family settings are in place, check whether the account has restrictions that block Store sign-in or purchases. If you recently changed region settings or moved countries, verify that the account’s region and the device’s region are set the way Microsoft currently expects for your account and Store access.
If the problem only appears with a managed account or a region-specific setting, stop trying random fixes. Those issues usually need the correct admin setting, account change, or Microsoft’s current guidance for that region.
- Repair or reset the Store if the account works everywhere else.
If the Microsoft account signs in on the web, the network is fine, and the clock is correct, but the Store still refuses to sign in, the app may need repair. Try the app’s Repair option first if it is available in Windows app settings. If Repair does not help, use Reset only after you are sure you are okay with clearing the app’s local data.
- Reinstall the Store only if the built-in repair steps fail.
If Repair and Reset do not fix the issue, the Store app itself may be damaged enough that reinstalling is the next step. Use the current Microsoft-supported repair or reinstall path for your Windows version rather than guessing a command from an old guide. If the account, network, and clock all check out but the app still fails, that is the point where reinstalling makes sense.
If you get the same failure after these steps, stop repeating the login attempt. At that point, the most likely remaining causes are an account-level restriction, a device policy, or a Windows component that needs Microsoft’s current support path.
How to tell if it worked
The fix worked if the Store stays signed in after you close and reopen it, your profile name appears normally, and app pages or downloads load without asking you to sign in again. A real fix should survive a restart, not just one open session.
If the Store still refuses sign-in, test the same Microsoft account in a browser one more time. If the browser now asks for a password reset, security code, or account recovery step, complete that first. The Store cannot finish a sign-in that Microsoft has placed behind an account verification check.
If only the Store fails while other Microsoft sign-ins work on the same PC, the app cache or Store component is still the likeliest problem. If Microsoft’s current official help for Store sign-in problems points you to account recovery, device management, or region support, follow that flow instead of continuing to guess.
Conclusion
If the Store still will not sign in after you’ve checked the account, network, clock, and cache, use Microsoft’s current official help or account recovery flow next.
Frequently Asked Questions
Should I reset the Microsoft Store if sign-in fails?
Only after you have confirmed the account works in a browser, checked the network, and synced date and time. Resetting clears local Store data, so it is a later step, not the first one.
Why does the Store accept my password in a browser but not in Windows?
That usually points to a local Windows or Store session problem, such as cached credentials, a bad token, or a clock mismatch.
What if this is a work or school device?
Then the sign-in issue may be policy-related. Your organization can restrict the Store or the account type it accepts, so check with the device admin if the personal fixes do not help.