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

Crizal · 09 Jan 2019

smalltown said:

I just (amateur here) thought that maybe it's a problem with specific router manufacturers not the IP address ?
I looked, and no one shows what router they have including myself under the "my computer" drop down menu.

Excellent catch! I updated system specs.

jimbo45 · 09 Jan 2019

Hi there
Check if you are using IPV6 only, IPV4 and IPV6 or IPV4 only. Should be in router settings.

I´m not a network guru so to me any time networking actually works on Windows I think it´s probably some type of middle ages alchemy or even plain simple magic.

Linux networking always seems to work straight OOB so why Ms have so much problem with this stuff I have no idea - just seems after any major windows update / upgrade something in networking just gets broken. Windows networking has been dodgy ever since Windows 3.11 (Windows for workgroups) - not that most people would remember that far back or were even alive then !!.

I invariably get one computer that fails to see rest of network or stuff like that -- I usually just re-set everything (power off -- including phones --yes under 25's there is actually a power off switch on phones believe it or not) , have a glass of Scotch / Beer (or two) and then re-boot everything in order one at a time. That usually fixes it.

Cheers
jimbo

EdTittel · 09 Jan 2019

Woke up this morning and all 1809 machines upgraded successfully. No effort needed. I like it when things work that way.
--Ed--

sgage · 09 Jan 2019

smalltown said:

I just (amateur here) thought that maybe it's a problem with specific router manufacturers not the IP address ?
I looked, and no one shows what router they have including myself under the "my computer" drop down menu.

My router is also at 192.168.0.1, and Edge will not connect to it.

Berton · 09 Jan 2019

sgage said:

My router is also at 192.168.0.1, and Edge will not connect to it.

Same for me. WDC N750

Reldel · 09 Jan 2019

I believe the Edge problem that does not allow access to router login page has been going on since at least the December update. I was never able to access my Netgear router with Edge in December but did not realize what caused it.

Bree · 09 Jan 2019

This Edge 'can't see router admin page' problem also exists in 1803.
Neither the 1803 or 1809 Edge can open my router admin page, either by url http://bthub.home or IP address 192.168.1.254. IE and any other browser still can.

Bree · 09 Jan 2019

Reldel said:

I believe the Edge problem that does not allow access to router login page has been going on since at least the December update. I was never able to access my Netgear router with Edge in December but did not realize what caused it.

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.

Faith · 09 Jan 2019

What does this update break exactly? A specific website? I didn't understand it.

Bree · 09 Jan 2019

Faith said:

What does this update break exactly? A specific website? I didn't understand it.

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