Forum Discussion
Windows 10 1809 Edge not loading pages
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.
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
BrianI 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.
- I have not solved this issue yet, but another few odd things I've found...
1. Microsoft Store opens, but does not load any page.
2. If I manually set the DNS on my machine to an external DNS server rather than use our local DNS, Edge and the MS Store work fine. I even set my machines DNS to use the same forwarders as our local DNS does. Edge and MS Store work fine.
Seems to me like there is an issue with this build of Windows and how certain apps handle DNS. At least Edge and MS Store.
To all,
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.
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:-
https://community.sophos.com/kb/en-us/132874
Chris,
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.
Enabling IP6 worked for my Desktop with 1809.
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!
Change your network connection to "public" and it should then work
- This fixed my problem moving to public. Hopefully they develop a fix for this one quickly.
.png){kind=link}