Microsoft Store Errors 0x80131500, 0x80072EE7, 0x80072EFD, 0x80072EFF

When you open the Microsoft Store app, one of the errors 0x80072EFD (“The server stumbled”), 0x80072EE7, 0x80131500 or 0x80072EFF may show up, and you can’t use the Store app. Resetting the Store app by running the wsreset.exe command or reinstalling Store using PowerShell also may not help.

The server stumbled

We all have bad days

The error code is 0x80072EE7, in case you need it.
windows store: the server stumbled
Windows Store: “The server stumbled 0x80072EE7”
Check your connection

The Microsoft Store needs to be online. It looks like you're not.

Code 0x80072EFD
store error check your connection
Microsoft Store error code: 0x80072efd
Try that again

Page could not be loaded. Please try again later.

Code: 0x80131500
Microsoft Store error code 0x80131500
Microsoft Store error code: 0x80131500

You’re asked to check your internet connection, and clicking the Check connection button takes you to the Network Connections page.

check internet connection status

  • If the network connectivity is working in other programs, you need to fix a couple of settings so that Microsoft Store can access the internet. On the other hand, if you’re unable to browse the internet using any application or browser, run the Internet Connection Troubleshooter first. To run the troubleshooter, click Start, Settings, Update & Security, and click Troubleshoot.

All of these errors 0x80072EE7 0x80072EFD 0x80131500 & 0x80072EFF occur if the app (the Store app) is facing connectivity issues. Here’s the explanation of each error code:

0x80072EE7 (12007)
The server name could not be resolved.

0x80072EFD (12029)
The attempt to connect to the server failed.

0x80072EFF (12031)
The connection with the server has been reset.

TlsFailureException:Unknown error (0x80131500)

Since the internet connection works fine from other apps, let’s inspect & fix other settings that are used by the Microsoft Store app.

Fix: Store Errors 0x80072EE7 0x80131500 0x80072EFD 0x80072EFF

1) Switch to Google Public DNS, OpenDNS, or Cloudflare DNS.

  1. Right-click Start, click Run. Type ncpa.cpl and click OK. This opens the network connections page.
  2. Right-click on the ethernet/Wi-Fi connection and click Properties.
  3. Double-click “Internet Protocol Version 4 (TCP/IPv4)” to open the Properties dialog.
  4. Enable the “Use the following DNS server addresses” radio button.
  5. In the Primary DNS server field, input
  6. In the Alternate DNS server field, input
    ipv4 dns server change - google public dns
  7. Click OK, OK to close the dialog boxes.

The above DNS servers are Google Public DNS server addresses.

(For most users, changing the DNS servers will do the trick!)

2) Enable the DNS Client Service

  1. Open Services MMC by running services.msc from the Run dialog.
  2. Double-click DNS Client and ensure that its Startup type is set to Automatic.
  3. Close Services MMC.

If you’re unable to start DNS Client via the Services console (due to grayed-out options), you may need to edit the registry to enable the service.

  1. Start the Registry Editor [regedit.exe] and go to the following branch:
  2. In the right pane, double-click the DWORD value named “Start” and set its data to 2.
  3. Exit the Registry Editor and restart Windows.

3) Enable TLS in Internet Options

  1. Right-click Start, click Run.
  2. Type inetcpl.cpl and click OK. This opens the Internet Options dialog.
  3. Click the Advanced tab, and enable the following options:
    • Use TLS 1.0
    • Use TLS 1.1
    • Use TLS 1.2
      enable tls internet options windows store
  4. Click OK.
  5. Close Microsoft Store and relaunch it.

If that doesn’t help, try this combination:

  1. Deselect “Use SSL 3.0”
  2. Deselect “Use TLS 1.0”
  3. Deselect “Use TLS 1.1”
  4. Select “Use TLS 1.2”
  5. Select “Use TLS 1.3 (experimental)” if the option is listed.
    store app tls settings internet options
  6. Click OK.
  7. Close Microsoft Store and relaunch it.

Is TLS 1.2 blocked via the registry?

If none of the above steps help, you need to check if TLS 1.2 is blocked in the SCHANNEL registry branch. If TLS 1.2 is blocked, the Windows Store app may throw the error 0x80131500. And, you’ll see the following error in Windows Update:

We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet.

windows update error due to TLS 1.2 disabled via SChannel

In Outlook/Word and other Office apps, the following error may occur:

Sorry, we are having some temporary service issues


We are unable to connect right now. Please check your network and try again later.

To unblock TLS 1.1 and TLS 1.2, follow these steps:

  1. Start the Registry Editor (regedit.exe)
  2. Go to the following branch:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client

    (Note: If the above branches don’t exist, it means that TLS 1.1/1.2 are not blocked. Quit the Registry Editor in that case.)

  3. In the right pane, delete the values, namely: “Enabled” and “DisabledByDefault
  4. Exit the Registry Editor.

You’ve now re-enabled TLS 1.1 and 1.2 on your computer. See if you’re able to open Microsoft Store.

4) Disable Proxy Server

  1. In the Internet Options dialog, select the Connections tab.
  2. Click LAN Settings.
  3. Uncheck the “Use a proxy server for your LAN…” option if it’s enabled.

This is to check if your proxy configuration is causing connectivity issues in Microsoft Store. If you’re using third-party DNS Proxy software (i.e., Acrylic DNS Proxy, AnalogX Proxy) for local DNS caching, try disabling them.

5) Fix Network Profiles Registry Permissions

  1. Start the Registry Editor (regedit.exe)
  2. Go to the following location:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles

    fix network profiles permissions inheritance

  3. Right-click on the Profiles key, and click Permissions.
  4. Click Advanced.
  5. Select the “Replace all child object permission entries…” checkbox and click OK.
  6. Click Yes when you see the following prompt:
    This will replace explicitly defined permissions on all descendants of this object with inheritable permissions from Profiles.
    Do you wish to continue?
  7. Close the Permissions window.
  8. Exit the Registry Editor.

6) Fix the Date/Time

Open Settings and check if the Date/Time and Region settings are correct. If the date and time are reset at every boot, you may need to change the CMOS battery. Wrong date and time will affect Windows Updates as well.

I hope one of the above steps remedies the Microsoft Store connectivity errors 0x80072EE7 0x80131500 0x80072EFD 0x80072EFF you were facing.

One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support, my reader. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded in 2005.

1 thought on “Microsoft Store Errors 0x80131500, 0x80072EE7, 0x80072EFD, 0x80072EFF”

  1. This can also occur if you are using a third party dns service such as Acrylic DNS, I found by disabling acrylic and re-enabling DNSCache service and restarting, suddenly windows store began to work; Must investigate further; perhaps store is tied at the hip with dnscache or maybe in Acrylic I had disabled the DNS query type, used by the store, 85 of them can be selectively allowed or blocked.


Leave a Comment