The Microsoft Store on Windows 11 fails in creative ways: cryptic error codes (0x80072EE7, 0x80131500), endless loading spinners, downloads stuck at 0%, or the app refusing to open at all. Beneath the variety, the causes are a short list — corrupted cache, bad system time, damaged app packages, or account glitches — and the fixes below handle all of them.
Work through these in order, from the 30-second cache clear to full reinstallation. If the Store won’t open on a specific brand, our Store not opening on ASUS guide has model-specific notes. Store failures that come with access-denied style error codes may also relate to error 0x80070005 , which covers permission-related update and Store failures.
Why this happens
- Corrupted Store cache: Stale or damaged cached data breaking page loads and downloads.
- Wrong date/time: The Store’s HTTPS connections fail certificate checks when your clock is off.
- Damaged app package: A Windows update corrupting the Store’s own files.
- Microsoft account sign-in issues: Token or profile glitches blocking the Store backend.
- Disabled background services: The Store needs Background Intelligent Transfer and related services running.
- Corrupted system files: Broader Windows damage manifesting in Store failures.
- VPN/proxy interference: Network middleboxes breaking the Store’s connections.
- Corrupted user profile Store data: Per-user Store caches that survive app resets and only clear with a profile-level fix.
How to fix it
Work through these in order — start with Fix 1 and stop as soon as the Store works.
Fix 1: Clear the Store cache with wsreset.exe
The fastest fix — resolves a huge share of Store errors in under a minute.
- Press Win + R, type
wsreset.exe, and press Enter. - A blank Command Prompt window appears for 10–30 seconds — don’t close it.
- The Microsoft Store opens automatically when the reset finishes.
- Try your download or page again. If it works, you’re done.
Fix 2: Check date, time, and region
Wrong clocks silently break the Store’s secure connections.
- Right-click the taskbar clock > Adjust date and time.
- Enable Set time automatically and Set time zone automatically, then click Sync now.
- Open Settings > Time & language > Language & region and confirm your Country or region is correct — mismatched regions cause licensing and availability errors.
- Restart the Store and retry.
Fix 3: Repair and reset the Store app
Deeper than wsreset — repairs the app package itself.
- Open Settings > Apps > Installed apps.
- Find Microsoft Store, click the … menu > Advanced options.
- Click Repair first and test the Store.
- If it still fails, click Reset (you’ll be signed out; your installed apps are unaffected).
- After resetting, restart the laptop before opening the Store — this ensures the reset fully applies.
- Open the Store, sign back in, and retry.
Fix 4: Run the Store Apps troubleshooter
Automated diagnosis for app-platform issues.
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Click Run next to Windows Store Apps.
- Apply its recommendations and restart the Store.
- If the troubleshooter is missing on your build, skip to Fix 5 — Microsoft has folded some troubleshooters into the Get Help app.
Fix 5: Check required background services
The Store depends on services that “optimizers” love to disable.
- Press Win + R, type
services.msc, press Enter. - Find Background Intelligent Transfer Service — set Startup type to Automatic (or Manual) and Start it.
- Do the same for Windows Update and Microsoft Store Install Service (if present).
- Restart the laptop and test the Store.
Fix 6: Re-register the Store with PowerShell
Reinstalls the Store’s registration without touching your data.
- Open PowerShell as administrator: Win + S, type
powershell, right-click > Run as administrator. - Run:
Get-AppxPackage -AllUsers *WindowsStore* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} - Wait for it to complete (ignore red errors for other packages if you ran the broader version).
- If the Store package itself is missing from the list (deleted by a debloat script), the targeted command can’t find it — in that case run the broader re-registration for all inbox apps, or use the in-place upgrade in Fix 7.
- Restart and open the Store.
Fix 7: Repair system files and check your account
Covers the remaining systemic causes.
- Open an administrator Command Prompt: run
sfc /scannow, thenDISM /Online /Cleanup-Image /RestoreHealth. - Sign out of the Store (profile icon > Sign out), restart, and sign back in — this refreshes stale auth tokens.
- Temporarily disable any VPN or proxy, then retry — if the Store works, add an exception or adjust the VPN’s settings.
- As a test, try the Store in a new local user account; if it works there, your main profile’s Store data is corrupt (Fix 3’s Reset usually resolves it). To create one quickly: Settings > Accounts > Other users > Add account > I don’t have this person’s sign-in information > Add a user without a Microsoft account.
- For persistent corruption, an in-place upgrade from the Windows 11 download page (keep files and apps) reinstalls all inbox apps cleanly.
Closing
Microsoft Store errors look varied but yield to a short, ordered routine: clear the cache with wsreset, fix the clock, repair or reset the app, and re-register it if needed. Most people never get past Fix 3. The two preventive habits that matter: keep your date/time on automatic sync, and don’t run “debloat” scripts that rip out Store components — they’re the top cause of Stores that vanish entirely. And if downloads specifically stall while browsing works, check your VPN and the Background Intelligent Transfer Service before anything else. Store problems are rarely urgent, but they’re worth fixing promptly: an unhealthy Store often signals broader app-platform issues that affect other inbox apps too. Work the list top to bottom and stop at the first fix that holds — most Store issues surrender to the cache clear or the clock check. For general Windows guidance, Microsoft’s Windows support hub documents the current Store error codes.
