How to Fix Microsoft Store Error 0x80131500 in Windows 11

What 0x80131500 means and what usually causes it

The code belongs to the CLR exception range (0x8013…), and when the Store throws it, the page only says “Try again later — something happened on our end”. It is a catch-all: a failed download, a page that would not load and an update that refused to install can all produce the same number. Because the code does not name a component, the practical approach is to eliminate the usual suspects in a fixed order. Microsoft-side outages produce exactly this error too, so before changing anything, open the Store on another device or check a service-status tracker to rule that out.

The shortlist below covers nearly all real-world 0x80131500 reports on Windows 11. Each item has a matching step in the next section. None of them requires more than a couple of minutes or a reboot.

• A damaged Store cache — the single most common cause, fixed by wsreset
• A proxy, VPN or custom DNS filtering traffic to Microsoft's servers
• Broken Store app registration after a big cumulative or feature update
• Wrong date, time or region settings breaking the TLS handshake with the Store
• A temporary outage on Microsoft's side — nothing to fix locally
• Third-party antivirus or a firewall blocking the Store's background services

Fixing 0x80131500: the order that works

Start with the cache: press Win+R, type wsreset.exe and press Enter — a blank console appears for about half a minute, then the Store reopens with a clean cache and your installed apps untouched. Next run the built-in troubleshooter: Settings → System → Troubleshoot → Other troubleshooters → Windows Store Apps → Run. Then check the network path: disconnect any VPN, turn off the manual proxy under Settings → Network & internet → Proxy, and run ipconfig /flushdns in an elevated Terminal. Make sure Set time automatically and the correct region are enabled under Settings → Time & language, because a skewed clock breaks the certificate check the Store depends on.

If the error survives that, re-register the Store: open Terminal (Admin) and run Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register ($_.InstallLocation + 'AppXManifest.xml')}, then reboot. Also open services.msc and confirm that Microsoft Store Install Service (InstallService) is not disabled. Re-registering rewires the app's manifest without touching your installed apps or your sign-in.

When nothing helps: Microsoft-side outages and the last resort

If every step fails on one machine while the Store works fine elsewhere, the local Store package itself is damaged. The clean way out is a repair install: download the Windows 11 ISO from Microsoft, mount it by double-clicking, run setup.exe and choose “Keep personal files and apps” — this replaces Windows' system files, Store included, in 30–60 minutes. Creating a new local user account is a quicker test that often reveals whether the damage is machine-wide or profile-wide.

A practical prevention note: recurring Store failures tend to leave gigabytes of dead download leftovers in the temp and delivery-optimization caches. Kleaner PRO can sweep those on a schedule, keeping the Store's working directories clean between failures. If you prefer manual control, emptying %TEMP% after each troubleshooting session achieves the same.

Questions and Answers

Read next

All articles · FAQ