"This page failed to load" error when you run Windows Store apps in Windows 8.1 or Windows RT 8.1

Gilt für: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 R2 Essentials

This article describes an issue that occurs when you run Windows Store apps in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2. An update and a hotfix are available to resolve this issue. Before you install this hotfix, check out the Prerequisites section. Additional steps for configuration are required to enable this hotfix after the installation.


When a virtual private network (VPN) client is connected through forced tunneling mode on a computer, Windows Store apps cannot connect to the Internet, and you receive the following error message:
This page failed to load. There was a problem. Please try again.


This issue occurs because the VPN client sets the gateway to and sets the subnet mask to as the default values. In this scenario, Windows Store app traffic may be blocked by Windows Firewall.


To resolve this issue, we have released an update that is available from Windows Update and a hotfix for Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2.

Additional steps for configuration to enable this hotfix

After you install the hotfix, you have to define the network on domain controller to configure the new private out under the following conditions:
  • For non-proxy configurations, configure a Group Policy Object (GPO) that defines your intranet address space.
  • For proxy based configurations, configure the proxy addresses for the intranet and Internet.

For more information about how to configure the GPO and the proxy addresses, see the Isolating Windows Store Apps on Your Network.

Note After the GPO setting is configured, you can perform a gpupdate /force command on the client computer, and then you can see a registry entry is push to the client computer in the following registry subkey:

Hotfix information

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must have update 2919355 installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


See the terminology that Microsoft uses to describe software updates.