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

Bree · 09 Jan 2019

Dirk Ele said:

Yes, it is on 1809.

Ah, I meant that I have one machine still on 1803, that too stopped seeing my router in Edge after the Jan. 8 cumulative update.

ddelo · 09 Jan 2019

Bree said:

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.

Bree, ZTE ZXHN H 168N, in the list too...from a physical machine running 1809 17763.253.
I didn't have the problem in 17763.195

To test it I have reset the network adapter, toggled IPv6 off/on...no dice. Edge does not open it.

slicendice · 09 Jan 2019

Bree said:

Ah, I meant that I have one machine still on 1803, that too stopped seeing my router in Edge after the Jan. 8 cumulative update.

Add Inteno DG200AL to your list of non compatible routers. I haven't been able to connect using the domain name for ages, both on 1803 and 1809. Using the known IP adress however still works.

Using Edge on Android has no issues connecting using either method.

Bree · 09 Jan 2019

slicendice said:

Add Inteno DG200AL to your list of non compatible routers. I haven't been able to connect using the domain name for ages, both on 1803 and 1809. Using the known IP adress however still works.

That's a partial fail then, interesting. For my router neither the name or the IP address work.

slicendice · 09 Jan 2019

Bree said:

That's a partial fail then, interesting. For my router neither the name or the IP address work.

IOpSys and the JUCI interface is odd enough on Inteno routers. It's very unreliable in my opinion. So it's difficult to tell if it's Edge rendering engine or the router software that makes crazy things...

DooGie · 09 Jan 2019

Edge won't find my router either, if I type the IP in manually one of the numbers changes when I hit return. It works fine using Firefox.
Whether it has happened on previous Windows builds I don't know as I've never tried to get into the router settings using Edge before.

Bree · 09 Jan 2019

DooGie said:

Whether it has happened on previous Windows builds I don't know as I've never tried to get into the router settings using Edge before.

I restored some Macrium images just to test this. Edge worked with my router up to and including 17763.195. It only broke with this update to 17763.253.

IronZorg89 · 09 Jan 2019

I have just tried to both "Repair" and "Reset" Microsoft Edge on my other machine and rebooted. Still no dice, when I tried to reach my router page in Edge again. It seems that the cause of the issue is more profound than most of us think or know.

DooGie · 09 Jan 2019

Just looked at my Event Viewer and noticed a new entry in it.

The program MicrosoftEdgeCP.exe version 11.0.17763.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 2e10
Start Time: 01d4a83fb9fd3523
Termination Time: 4
Application Path: C:\Windows\System32\MicrosoftEdgeCP.exe
Report Id: 56ef79bc-b3ac-4ffe-881d-919683a01f4e
Faulting package full name: Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe
Faulting package-relative application ID: MicrosoftEdge
Hang type: Cross-process

stormy13 · 09 Jan 2019

Normally use Firefox, but just tested this on my router (Asus RT-AC66U_B1) and modem (SmartRG 515AC in bridge mode) and can get to the modem GUI no problem in Edge (192.168.1.1), but can't access the router using the IP (192.168.50.1 (Asus default, I didn't set it to that)). I can access the router in Edge no problem http://router.asus.com/Main_Login.asp though.