Microsoft Edge and other Microsoft Store apps might not connect to the Internet after installing the Windows 10 October 2018 update

Anonymous
2018-10-04T21:36:35+00:00

After installing the Windows 10 October 2018 update (version 1809), Microsoft Store apps are no longer able to connect to the Internet.  For example, Microsoft Edge is unable to connect to any websites, displaying the message, “Hmmm...can’t reach this page.”  Apps like Mail, Calendar, and News are not working properly.  And Microsoft Store says to check my connection.

Non-Store apps, such as Internet Explorer, are still able to connect to the Internet.

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2018-10-04T21:41:00+00:00

Microsoft is aware of an issue after installing the Windows 10 October 2018 update (version 1809) that prevents Microsoft Store apps from connecting to the Internet on devices that have disabled IPv6.  Microsoft is working on a solution that is planned to be released in a future Windows update.  In the meantime, you can resolve this problem by enabling IPv6:

  1. Open the Settingsapp and select Networking & Internet > Network and Sharing Center.
  2. Select the network adapter you're using (by clicking the appropriate link next to “Connections”) and select Properties.
  3. On the Networking tab, select the checkbox next to Internet Version 6 (TCP/IPv6).
  4. Select OK to save your changes.

Was this answer helpful?

100+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2018-10-05T19:14:26+00:00

If you still having issues after enabling IPv6, I suggest changing your network profile to Public.  Go to Settings, Network & Internet and click on Change connection properties.  Under Network profile, click on Public.

If that doesn’t work, run Network reset. This will reinstall your network adapters and set other networking components back to their original settings.  You might need to reinstall any VPN software or virtual switches after. Go to Settings, Network & Internet and click on Network reset.  Click on Reset now.

Was this answer helpful?

90+ people found this answer helpful.
0 comments

177 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-11-06T20:53:47+00:00

    And if after doing all of that doesn't help, what should we try next besides switching to Apple?

    Do you have real Local IPv6?  Otherwise you would probably have to try to get one of the tunneling protocols working.  So far W10 doesn't seem to like them as much as earlier versions of Windows did.  Then you might have to upgrade your router.

    https://docs.microsoft.com/en-us/windows/deployment/planning/windows-10-1803-removed-features

    <quote>

    ISATAP has been disabled by default since Windows 10, version 1703 (the Creators Update), and Direct Tunnels has always been disabled by default. Please use native IPv6 support instead.

    </quote>

    FYI

    Robert Aldwinckle

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-11-06T21:05:53+00:00

    And if after doing all of that doesn't help, what should we try next besides switching to Apple?

    Do you have real Local IPv6?  Otherwise you would probably have to try to get one of the tunneling protocols working.  So far W10 doesn't seem to like them as much as earlier versions of Windows did.  Then you might have to upgrade your router.

    https://docs.microsoft.com/en-us/windows/deployment/planning/windows-10-1803-removed-features

    <quote>

    ISATAP has been disabled by default since Windows 10, version 1703 (the Creators Update), and Direct Tunnels has always been disabled by default. Please use native IPv6 support instead.

    </quote>

    FYI

    Robert Aldwinckle

    Thank you for the information Robert and while this is not a dig at you in any way, that is a ridiculous requirement that MS is putting on businesses without proper prior warning.  It says this was supposed to have been disabled since 1703, then MS needs to explain why 1703, 1709, and 1803 were not effected by this change but now all of a sudden doesnt work in 1809.

    A lot of businesses don't want to mess with IPv6 until they have to.  My company is not going to go out of its way to setup an IPv6 internal network that will just confuse old hardware when DNS sends back the v6 address instead of the v4.

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more