10-02-2018 05:49 PM
10-02-2018 05:49 PM
After updating from 1803 to the new 1809 release Edge stopped working (as well as the Feedback hub), while Chrome and Firefox continued to work fine.
After some trial and error the culprit ended up being that the IP6 protocol was disabled on my wireless adapter - I'd turned it off for some other testing and apparently that stops Edge from working entirely.
Just putting this up here for anyone else that runs into this problem. It seems that issues with Edge not working after updating to 1809 have been going on for some time in the pre-release rings so I'm surprised that this hasn't been resolved yet.
10-03-2018 03:03 PM - edited 10-03-2018 03:31 PM
To fix this issue, you will have to change your Wi-Fi settings from private to public.
1. Go to settings
2. Choose Network and Internet
3 Click on Status then click on
4 Change Connection Properties then click on Public
Yes, I have the same problem. I have my IPV6 enabled. What I have noticed is that whenever I put the computer on an open Network (Wi-Fi without password), Edge can browse without any issues.
I have also checked to see if my firewall was blocking Edge. and even turning Windows Firewall off, but it still remains the same. There needs to be an update to patch this flaw.
10-03-2018 04:32 PM - edited 10-03-2018 04:33 PM
Can confirm, after updating to Version 1809 (Windows 10 Enterprise, in my case) that Edge would no longer load pages with IPv6 disabled.
Re-enable IPv6 on the network adapter allowed Edge to once again load web pages correctly.
Not sure why it's necessary, but thanks for the tip!
10-03-2018 07:44 PM
I had the same problem on my 1 year old computer but not on my other older computers. It took me a few minutes to figure out where the IP6 was, as soon as I found where it was I saw it wasn't turned on. I put the check mark in and voila! it started working again. This also fixed the other new problem I had after the update and that was not being able to connect to the Microsft Store.
For those (like me) who don't know where to find it, it is Control Panel>Network and Internet>Network Connections, go to Properties on the General tab and put a check mark in the box beside Internet Protocol Version 6 (TCP/IPv6).
Thanks Gavin for putting me on the right track. I never would have figured that out on my own.
10-03-2018 09:24 PM - edited 10-04-2018 06:39 AM
Hi guys there definitely seems to be a bug with 1809 affecting certain Realtek network cards and Edge.
Realtek RTL8102E/RTL8103E Family PCI-E Fast Ethernet NIC (NDIS 6.2)
I have three computers. Two laptops & a desktop.
DT & one laptop had no problems but the laptop with the Realtek RTL8102E/RTL8103E has the Edge bug.
When I open Edge it doesn't open any webpages
IE works fine
IPV6 on or off doesn't make any difference
Resetting the firewall doesn't help
Resetting Edge doesn't help
Reinstalling the adapter doesn't help
Resetting network doesn't work
My other laptop with Realtek PCIe FE Family Controller had no problem
The only thing that worked was to change my network from Private to Public.
Hoping for a bug fix soon as this problem laptop is my media server so now I can't access the shared folders on it.
10-04-2018 07:02 AM - edited 10-04-2018 07:09 AM
On the last build we had to turn off IPV6 to make file sharing and shared printers work ! Now we have to turn it back on again if we want Edge to work ! This time its on Microsoft as we can all easily just use Chrome or Firefox. Doh Probably going to lose some Edge users on this one :) AGAIN one has to wonder how this did'nt get caught before its release. So at this point we either have no browser OR mess up our file /printer sharing OR set our connection to public. WOW at a loss for words
10-04-2018 09:31 AM - edited 10-04-2018 09:32 AM
Must be hit-and-miss among devices. I'm running a Surface Book 2, and Edge stopped loading pages over both Wi-Fi and Ethernet. Wi-Fi is a Marvell AVASTAR Wireless-AC Network Controller, Ethernet is through a Surface Dock. IPV6 makes no difference, and if I try changing my work network to Public, I won't be able to get any work done.
10-05-2018 12:11 AM
The IPv6 fix is not working for me so I guess I will have to wait for an official fix for my Desktop.
Nice to know this is not an isolated incident!
10-05-2018 06:42 AM
10-05-2018 06:47 AM
10-05-2018 07:08 AM
10-05-2018 07:24 AM
No worries Ron.
Just noticed that my OD4B system tray icon is missing so I going to blame the 1809 Feature update for this one.
Running the OneDriveSetup.exe wizard does not fix it.
Time for a seperate post.....
10-05-2018 10:30 AM - edited 10-05-2018 10:47 AM
This didn't work for me as it was already enabled, but it got me thinking. After looking at all of the adapters I found that my Ethernet adapter needed a driver update. Once I updated the driver and checked the Wi-Fi adapter for updates as well Edge worked once again.
UPDATE: Although my fix seemed to work, it was short lived. I am once again unable to get anywhere with Edge while other browsers continue to work fine.
10-05-2018 03:58 PM
I had the same problem, even Microsoft Store or NetFlix didn´t work. I turn on IPv6 on my Realtek ethernet device and everything go on again.
I guess enable ipv6 don´t cause me others troubles i had in the past.
10-07-2018 01:30 PM
this is grim, I just noticed Edge doesn't work a few days after upgrading my home PC to 1809 (no surprise I don't generally use the horrible little browser). Enabled ipv6 and it works... why tyvfm Microshaft yet again for forcing how I choose to use my home PC.
10-08-2018 05:38 AM
I am still having the issue but I think in part this is due to the fact that some of the fixes may only work in Windows 10 Home and not Windows 10 Pro. When posting can you please list whether you are using one or the other.
10-08-2018 06:07 AM
After hearing Microsoft had pulled the 1809 Feature Update I went back to any earlier version of Windows 10 for the time being.
There seems to be a connection with Sophos AV (which is what I use) though which might be helpful for others:-
10-08-2018 06:39 AM
I saw the same thing about Sophos AV on another blog and tried the fix they suggested. It did not work and after seeing an article about MS putting a hold on the 1809 update I rolled back. A am writing back to you via my Edge browser so I know the rollback worked.
10-09-2018 04:18 PM
I have done a ton of testing on this. The problem was affecting about 100 computers across four different businesses, and therefore four different active directories, and four different networks. First off I have to excoriate Microsoft for even making IPv6 a requirement on Edge because 100% of our ~89 customer networks cannot even use IPv6. Their ISP does not have IPv6 at all and cannot allocate addresses. I called Spectrum today. Not only do they not provide an IPv6 prefix (space) to a customer, but they won't even take it as a feature request. Nope.
So that means you cannot actually even obtain internet routable base for your IPv6 space to configure inside your network.
Then if you consider the fact that most perimeter security appliances won't NAT IPv6 to IPv4 or vice versa, then they will just dump any IPv6 traffic that is headed to the internet. I know this to be true as I tested it. Check this out even after you have an IPv6 address.
http://ipv6-test.com/ disable disabled disabled
So if your ISP won't give you an IPv6 space, and your equipment is going to dump IPv6 traffic anyway, then why how and when will it ever be used? I don't see any purpose or value for IPv6 on the inside of a LAN. We have NAT. I don't want all devices on the LAN to be directly inbound routable from the WAN without going through security inspection at a security appliance. So I see IPv6 where your endpoints have WAN addressable IP addresses as a security risk.
But you say that a private space could be used. https://simpledns.com/private-ipv6
Sure of course. But again, what is the point? The traffic will never leave the network to get to the internet.
So Microsoft loves to turn themselves into a swear word by claiming that IPv4 is deprecated as of 2011 and then forcing this change on us when it is technically impossible to even properly configure IPv6 for most networks.
I'm going to give you a set of commands that may or may not solve your problem if you are having it. First verify you don't have a GPO that is disabling IPv6. If you do, set the GPO to Enable all IPv6 components. Any other option will not work. Reboot computer and verify that HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" /v DisabledComponents is zero.
Then do this:
Get-NetAdapterBinding -ComponentID ms_tcpip6
Look for anything that has a value other than true. If so, do this:
Enable-NetAdapterBinding -Name "*" -ComponentID ms_tcpip6
If you are still not getting IPv6 autoconfiguration address, then do this:
10-09-2018 11:16 PM - edited 10-20-2018 09:31 PM
Once you have configured your IPv6 settings you can easily verify your public IPv6 address including IP location online by typing what is my ip in the google search bar.
If your IPv6 is not detected by above method then your IPv6 is not configured properly.
10-11-2018 02:07 AM
Same problem here :
When connected to the AD domain through Ethernet Adapter > Store Apps and Edge are not connecting to internet.
But it works when i connect to other wifi (not domain related).
I didn't try yet to connect to ethernet network on other domains to check if it also works.
So i guess, for AD/Domain connection we have to work for a fix/KB...
But... It means that MS teams are using IPV6 on local domains, if they never seen this issue ?
11-29-2018 08:19 AM
Same problem with Realtek PCI adapter, trying the switch from private to public network. Please fix Microsoft
11-29-2018 08:28 AM
Microsoft has fixed 1809. Make sure you are getting the latest version of 1809. There are also a couple of add on fixes for 1809 that should come through as well.
11-29-2018 08:39 AM
Windows Update doesn't show anything new, is there some other way to check the version of 1809?
11-29-2018 12:26 PM
Thanks for the link, found out I am running the most current version of 1809.
Problem still exists, seems to be after visiting YouTube.com or other google website that the problem exists and can consistently recreate. Also Edge browser will break after visiting linked pages that msn.com redirects to, such as MSNBC, CNBC, CNET, etc...
Finally got Google Chrome browser to download using IE will use that instead of Edge. Sad that Edge no longer will work for me, after loading 1809 - worked fine with all websites before.
01-09-2019 01:35 AM
Same Problem for me since updating to 1809. Edge hangs/shows a blank panel below the address bar and does not load any webpage. IE/Chrome working fine.
Using most recent Update: Microsoft Windows [Version 10.0.17763.253]
Wifi Adapter: Intel(R) Dual Band Wireless-N 7265
I tried all proposed solutions:
* IPv6 is enabled (tried also to disable and re-enable it)
* Tried with several WiFi Networks and Settings (public, AD and private) - no difference
* Tried to re-register the Edge App Package
* sfc /scannow
* DISM.exe /Online /Cleanup-image /Restorehealth
Any other suggestions?
01-09-2019 05:23 AM
In reply to tschramme86: Assign a static IP address to the IPv6 component of your wireless adapter. This is one way to trick the bindings back into thinking that it actually can use IPv6 even though all your other indications show that it is enabled. I have found this on iDrac to work also.
If you have no idea what to use for IPv6 and you know you should be using an autoconfiguration address, then use this or some flavor of it.
Prefix is 64
01-11-2019 04:17 PM - edited 01-11-2019 04:22 PM
A few days ago one night I scheduled new you update on version 1809 at 11am the next day..so I come home after school, hop on my computer and microsoft edge wont load up, applications take forever to open and once I click on a category in settings it wont load either...these things didnt work. Later that day while trying to restart it, (that never worked) I'll said it will update outside of active hours and I said " a new update already?" Hoping that it will fix the problem and it didnt. I tried shutting it down for a while didnt work, tried restarting multiple times never worked. Please help I don't want to reset my computer, I've done it 3 times already
03-10-2019 03:32 PM
In my case MS Edge does load web pages in Win 10 Pro on my Dell XPS8700 mid tower system, but certain website do not load properly. Amazon.com does not show the TV show or movie watchlist properly. Menu items are listed down the left side of the page and movies are big boxes in the middle of the screen with lots of space causing need for lots of scrolling instead of horizontally in rows across the screen. I just updated to 1809 on my Dell Inspiron Laptop and before the update to 1809 Edge showed the web pages correctly and after the update the same issue of the Dell XPS8700 mid tower began. IVP6 is checked so that is not the problem. In addition some web pages load very slowly. Can anyone help or are we waiting for Microsoft to fix that problem?
05-24-2019 12:21 PM
Just upgraded a couple of systems to 1903 and seeing this issue for the first time. Changing network from Private to Public works when on an outside connection, but these are domain-joined machines on a domain network, so Edge is effectively broken for them
06-06-2019 09:09 AM - edited 06-06-2019 09:10 AM
@Brian Illner Same issue. Just updated to 1903. Domain joined. All updates applied. Doesn't matter if IPv6 is enabled or not (seems like an odd thing to break a browser anyway). Just started digging in to this, but it's got to be a bug.
Edit: Also reset and repaired Edge to no avail.
06-06-2019 03:31 PM
07-22-2019 08:26 AM
Same issue. Domain joined Edge only works for Trusted sites. Public network all works fine. If you want to break IE11 the same way, just Enable 64-bit processes for Enhance Protected Mode and Enable Enhanced Protected Mode in Internet Options. If I could just find out how to disable EPM for Edge, maybe that would fix this issue.
07-22-2019 02:27 PM
@NMSU92 Thanks. Please let me/us know if you figure it out. For me this is not terribly pressing since 1903 hasn't made its way on to the majority of my client machines, it's only Edge and the Windows Store, and I have better things to focus on O.o
07-31-2019 07:46 AM
08-01-2019 12:20 PM
Other reports are out there, this one claims he found a solution through GPO in his particular case.
08-27-2019 05:18 AM
Reset Edge browser Press Windows + X then select settings, Next, under the Apps and features section, search for Microsoft Edge. Now click on the Advanced options link to open the following window. first, select the Repair option if Edge is not working properly.
09-02-2019 06:52 AM
Following worked for me!
I have only 1 user on my pc, that is administrator a/c created by the windows 10 installation. I never bothered to create any other a/c as I did not required.
After the update of 1809, edge browser was unable to show web pages. For pages such as (https://fast.com) it was just showing endless circles..
Solution that worked for me: Created a user a/c. In that a/c, web pages are working fine!