Microsoft Store errors deserve a playbook, not a single trick, because the codes look unrelated but cluster into a few families: cache and registration problems, network and account problems, service problems, and profile problems. Match your symptom to the family, apply that family’s fix, and you’ll resolve the error in minutes instead of cycling through random suggestions.

Keep this principle in mind throughout: the Store is a replaceable app package sitting on top of shared Windows infrastructure (BITS, Windows Update, app registration). When the infrastructure is healthy, Store problems are shallow. When the infrastructure is broken, Store errors are just the visible symptom. The playbook below works both layers, shallow first. For the error-code reference with screenshots-style detail, see our Store error codes guide ; for the “won’t open at all” variant, Store not opening in 24H2 and the 24H2 Store error guide . A word on expectations: most Store errors resolve in under fifteen minutes once you match the code to the right family, and the order below puts the fastest, safest fixes first. What does not help is reinstalling the Store repeatedly or running random registry scripts from forums — those create new problems while the original cause sits untouched. Work the playbook top to bottom, and note which step fixed it for next time.

Why this happens

  • Corrupt Store cache: Stale or damaged cache data producing error codes and blank pages.
  • Broken app registration: The Store’s package registration damaged by updates.
  • Network interference: VPNs, proxies, and firewalls blocking Store endpoints.
  • Wrong time, region, or account state: Authentication and licensing failures from mismatched settings.
  • Stopped dependent services: BITS, Windows Update, or Store Install Service disabled.
  • Corrupt user profile: Profile-specific app data breaking the Store for one user only.
  • Broken Windows Update state: Shared infrastructure failures surfacing as Store errors.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Clear the cache and read the error code

Start with the universal first step, and actually read what the code says.

  1. Press Win + R, type wsreset.exe, press Enter, and wait for the Store to reopen by itself.
  2. Reproduce the error and write down the full code: 0x80070005 = permissions/cache, 0x80131500 = network/account, 0x80072EE7 = DNS/proxy, 0x80073CF9 = package registration.
  3. Match the code to the family and jump to the relevant fix below — but still work in order, since early fixes resolve multiple families.
  4. If there’s no code (blank page, instant close), treat it as a registration problem and prioritize Fixes 3 and 5.

Fix 2: Fix the network and account layer

For 0x80131500, 0x80072EE7, and sign-in failures.

  1. Disconnect VPNs and disable proxy servers (Settings > Network & internet > Proxy).
  2. Settings > Time & language > Date & time: enable automatic time and zone, then Sync now.
  3. Confirm Language & region country matches your location and your Microsoft account region.
  4. In the Store, click your profile icon > Sign out, then sign back in to refresh authentication tokens. Retry the failing action.

Fix 3: Repair, then reset the Store app

The built-in repair ladder — use both rungs.

  1. Settings > Apps > Installed apps > Microsoft Store > … > Advanced options.
  2. Click Repair and test. This fixes component issues without touching your data.
  3. If the error persists, click Reset, confirm, and sign back into the Store.
  4. Reset resolves 0x80070005 more often than any other single step — don’t skip it because Repair didn’t work. After resetting, open the Store’s Library and click Get updates before retrying your download — the reset sometimes leaves pending updates needing one manual nudge.

Fix 4: Restart the dependent services

For stuck downloads and “pending” queues.

  1. Win + R > services.msc > Enter.
  2. Set Background Intelligent Transfer Service, Windows Update, and Microsoft Store Install Service to Automatic and start each.
  3. In the Store, open Library > Get updates to flush stalled queues.
  4. Pause and resume any download stuck on Pending — with healthy services, the queue clears.

Fix 5: Re-register the Store package with PowerShell

For 0x80073CF9, instant-close, and post-update breakage.

  1. Open PowerShell (Admin).
  2. Run: Get-AppXPackage -AllUsers -Name Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  3. Ignore red “already registered” messages — they’re harmless.
  4. Restart the laptop and test. If the Store now launches cleanly, registration was the fault.

Fix 6: Isolate profile corruption with a new account

Five minutes to answer “is it my profile or my system?”

  1. Settings > Accounts > Other users > Add account — create a local test account.
  2. Sign in as the new user and reproduce the Store error.
  3. Works in the new account = your profile’s app data is corrupt. Migrate files to the new account; fighting the old profile wastes time.
  4. Fails in the new account too = system-wide. Continue to Fix 7.

Fix 7: Repair shared infrastructure — updates and system files

When the Store is the symptom, not the disease.

  1. Settings > Windows Update: install everything pending and restart. If an update fails, check Microsoft’s support site for that update’s known issues.
  2. Terminal (Admin): sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, then restart.
  3. Retest the Store. If it works now, the broken piece was shared infrastructure all along.
  4. Final option: in-place upgrade repair with the Windows 11 ISO (setup > Keep personal files and apps) — proportionate, file-safe, and resolves the stubborn remainder.

Closing

The playbook works because Store errors aren’t mysterious — they’re cache, registration, network, services, profile, or infrastructure, and each family has a decisive test. The most common mistake is trying fixes from multiple families at random and never knowing what worked; work the list in order, note which step fixed it, and if it ever recurs you’ll know exactly where to start. Bookmark this page — Store errors recur across Windows updates, and the second time through takes five minutes when you know your fix.

Frequently asked questions

What is the most common Microsoft Store error code?
Code 0x80070005 (access denied) and 0x80131500 (server/region issue) are the two most reported. 0x80070005 usually yields to a Store reset, while 0x80131500 usually yields to network, VPN, time, or region fixes. Code 0x80072EE7 points at name resolution — check DNS and proxy settings. The playbook below maps each code to its fix.
Why do Microsoft Store errors keep returning after I fix them?
Recurring errors usually mean the root cause wasn’t addressed: a VPN that reconnects on boot, a proxy pushed by group policy, a user profile that’s still corrupt, or Windows Update stuck in a broken state. Fix the persistent condition — not just the symptom — or the error returns with the next Store launch.
Does resetting the Microsoft Store delete my installed apps?
No. Resetting the Store app (Settings > Apps > Microsoft Store > Advanced options > Reset) only clears the Store’s own cache, data, and sign-in — your installed apps, games, and their data are untouched. It’s one of the safest troubleshooting steps in Windows and a good early move for most Store errors.
When should I give up and reinstall Windows for Store errors?
Almost never for a Store problem alone. Work the full playbook first: cache clear, troubleshooter, repair/reset, services, re-registration, new user account, updates, SFC/DISM. If the Store fails in a brand-new user account after all of that, an in-place upgrade repair (keeping files and apps) is the proportionate last step — not a clean install.