Cumulative Update KB4480116 Windows 10 v1809 Build 17763.253 - Jan. 8 Win Update

Bree said:

Yes. Specifically you cannot open the web page you use to control your router in Edge.

FWIW, no problem opening my FIOS router in Opera ...

3 PCs updated, don't use Edge however checked router access with it and it isn't working, just get a stupid Bing Search page? I use 192.168.8.1 OK in any other browser.
Other than that no problems.

DJG said:

FWIW, no problem opening my FIOS router in Opera ...

Opera, Firefox, even IE - they all still work. It's just Edge that has this problem.

Hi there

works for me on 1809 build 17763.195 (although I rarely use edge apart from reading / printing PDF files).



I see post was about the later update so I'll try again -- haven't been served that update yet though.

cheers
jimbo

Bree said:

I have just checked on a VM running 17763.194 (KB4471332, Dec. 11). Edge can see my router in that version.

Edit: After upgrading to 17763.195 (KB4483235, Dec.19) Edge could still open the router's web UI page. After upgrading to 17763.253, KB4480116 Edge was still able to access my router.

Curiouser and curiouser, while Edge in the VM was connected to the router, Edge on the host machine could open it too. However, after the VM was shut down Edge could no longer open the router's page.

That is fairly bizarre!

jimbo45 said:

works for me on 1809 build 17763.195 (although I rarely use edge apart from reading / printing PDF files).

Are you running that on a physical machine or a VM? My earlier tests show Edge works fine in a VM, just not on a physical machine (which may explain why MS testing missed this one).

I'n currently repeating the tests on a real machine.....

Hi folks

works perfectly for me in update 253 (on Real physical machine)



Could be if you are running in a Virtual Machine with NAT rather than bridged network there might be a problem with address resolution dpending on the VM type of software you are using. E.G HYPER-V with Internal vs external switches etc.

Cheers
jimbo

jimbo45 said:

Could be if you are running in a Virtual Machine with NAT rather than bridged network there might be a problem with address resolution dpending on the VM type of software you are using. E.G HYPER-V with Internal vs external switches etc.

Actually, it was only the VM that didn't have a problem. None of my physical machines can open my router page in Edge after the Dec. 8 update - that's Edge in the latest build of 1809, 1803, x86 or x64.

It appears that only certain routers are affected. So far we have reports for Edge being unable to use web admin on Verizon FIOS-G1100 (post #50), Netgear (post #65), WDC N750 (post #64) and my BT HomeHub4.