Site icon Winhelponline

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

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 0x80072EE7”
Check your connection

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

Code 0x80072EFD
Microsoft Store error code: 0x80072efd
Try that again

Page could not be loaded. Please try again later.

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.

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) Change the Country/Region to “United States” and update the Store app.

If you’re a non-US user, open Settings and change your country to “United States” (temporarily). Then, access the Store app, click “Library”, and update all available apps, mainly the Store app itself.

If you have just clean installed Windows 10 or 11, then your system might have an outdated version of the Store app. And installing it again using PowerShell reissues the stock version only.

The latest version of the Microsoft Store app is Version 22207.1401.1.0 (Windows 10/11 v21H2 are the latest builds as of this post). Updating the Store app resolves the error 0x80131500 for some users.

Once the issue is resolved, revert to the original Country/Region setting.

If the above doesn’t help, then download the latest Store app .appxpackage installer file and run it.

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

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

Note: If Google DNS doesn’t work, switch to Cloudflare DNS addresses and This has helped some users.

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

3) 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.

4) Enable TLS in Internet Options

  1. Right-click Start, and 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
  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.
  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.

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.

5) 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.

6) Disconnect your VPN

Disconnecting your VPN can help in many cases.

Mr. Courtney (from the Comments section below) says: “As soon as the Pulse Secure (VPN) was disabled, Microsoft Store worked again.”

If you’re able to access the Store with VPN disconnected, then you may use one of the following workarounds (Windows 10/11 Pro and Higher) so that you can continue using your VPN to access the Store app.

Option 1: Set TAP Adapter to “Always connected”

  1. Open Device Manager, and expand Network Adapters.
  2. Right-click the TAP network device for your VPN.
  3. Click Properties, and click Configure.
  4. Select the Advanced tab
  5. Select “Media Status”
  6. Change Value to “Always connected”
  7. Click OK.

And then:

  1. Open Control Panel\Network and Internet\Network Connections.
  2. Right-click the TAP network device for your VPN again.
  3. Click Properties.
  4. Click “Internet Services Version 4 (TCP/IPv4)”
  5. Click Properties.
  6. Click Advanced.
  7. Tick the “Automatic Metric” box and click OK.
  8. Click OK, and then click Close.

Your Windows 10/11 Store apps should now be able to connect successfully through the VPN. If not, try the next method.

Option 2: Enable Split-Tunneling in your VPN Client

Alternatively, you can enable split-tunneling in the VPN client (especially Home users) and add Microsoft Store to the exclusions. Here’s a screenshot from Norton VPN.

Similarly, other VPN clients like ExpressVPN and ProtonVPN also have the split-tunneling feature in their respective programs.

Option 3: Configure Private Network Range for Apps (Group Policy Editor)

  1. Open the Local Group Policy Editor snap-in (gpedit.msc)
  2. From the Group Policy Management Editor, go to:
    Computer Configuration > Policies > Administrative Templates > Network.
  3. Click Network Isolation.
  4. In the right pane, double-click Private network ranges for apps.
  5. In the Private network ranges for apps dialog box, click Enabled.
  6. In the Private subnets text box, enter the IP address range assigned by your VPN (e.g., Pulse Connect Secure device). For example, If your VPN adapter IPs are in the 172.x.x.x range, add in the text box.
  7. Double-click Subnet definitions are authoritative.
  8. Click Enabled.

If connected to a domain, configure the Domain policy as below:

  1. Open the Group Policy Management snap-in (gpmc.msc), and create, or open a Group Policy for editing.
  2. From the Group Policy Management Editor, expand Computer Configuration > Policies > Administrative Templates > Network, and then select Network Isolation.
  3. In the right pane, double-click Private network ranges for apps.
  4. In the Private network ranges for apps dialog box, select Enabled.
  5. In the Private subnets text box, type the IP range of your VPN adapter, and then select OK.
  6. Double-click Subnet definitions are authoritative, select Enabled, and then select OK.
  7. Restart the client to make sure that the GPO takes effect.

After the Group Policy is applied, the added IP range is the only private network range that’s available for network isolation. Windows will now create a firewall rule that allows the traffic, and will override the previous outbound block rule with the new rule.


7) 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

  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.

8) 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.

Exit mobile version