0x80131500 is the Microsoft Store's least helpful message: "Try that again - something went wrong on our end". In practice the problem is almost always on the PC, not on Microsoft's end: the Store cannot establish its secure connection (date, time or TLS settings), its own cache is broken, or the .NET components it runs on are damaged. Each has a quick, safe fix.
Fix it automatically
Outbyte Driver Updater identifies your installed hardware automatically and updates outdated or broken drivers from official sources, with a backup before every change. Useful when you would rather not run the steps below by hand - the scan and diagnosis are free.
Download Driver Updater Downloads Outbyte Driver Updater for Windows 11, 10, 8 and 7. Free 2-day trial, no credit card required.Quick answer
Check that the date, time and time zone are correct (set them to automatic), then press Win+R, type wsreset and press Enter to clear the Store cache. If the error stays, open Internet Options (inetcpl.cpl), the Advanced tab, and make sure TLS 1.2 is ticked. These three cover most 0x80131500 cases.
A wrong clock or disabled TLS 1.2 makes the Store's encrypted connection impossible - certificates look invalid and the Store gives up with 0x80131500.
The Store caches pages and licenses locally. When that cache is damaged, pages fail to load even though the connection itself is fine.
The 0x80131500 family of codes comes from .NET, the framework the Store runs on. Corrupted system files produce exactly this failure.
Leftover proxy settings, a VPN or an exotic DNS server can block the Store's endpoints while normal websites keep working.
wsreset and press Enter.inetcpl.cpl and press Enter, then open the Advanced tab.sfc /scannow.DISM /Online /Cleanup-Image /RestoreHealth, then SFC again, then restart.netsh winhttp reset proxy in the same admin terminal.Do not do this: Do not reinstall Windows over a Store error, and be careful with scripts that "reinstall the Store" via PowerShell from random forums - a wrong package command can break every built-in app. The steps above are reversible and cover the real causes.
The Store talks to Microsoft's servers over encrypted connections that require TLS 1.2. On systems where it was disabled - usually by an old tweak, a corporate image or third-party software - the connection is refused and the Store shows 0x80131500 instead of a clearer network message.
No. The reset clears the Store app's own cache and settings; the apps you installed through it stay in place. You may need to sign in to the Store again afterwards.
Start with the cache reset (wsreset) and check for Windows updates - a single broken page usually means stale cached data rather than a system problem. If every page fails, go through the full list starting with the date, time and TLS checks. For update-related codes, see the 0x80070643 guide.