Windows 10 Network bug in all versions, fix are planned

[German]Microsoft's January 2019 updates are causing a network issue in all supported Windows 10 versions. A patch to correct the problem is expected in February 2019 or later. Here is some information about what is going on.


Some error reports

I confess, I wasn't really aware of this issue, because I didn't notice the real thing, when I first read this German comment on my German article Windows 7: Updates KB4480970 und KB4480960 verursachen Netzwerkprobleme published at German site The user reported an 'exotic flaw' (here is my translation):

After the installation of the security updates 2019-01 (KB4480116) the Telekom Router (Speedport 925) could no longer be reached. After deinstallation, the Speedport router could be reached [within the browser] without problems as usual.

Some other German users mentioned DHCP issues within this forum thread. They recommended to assign a fixed IP address as a workaround. I haven't tested this (because I'm not affected, currently my Windows 10 V1809 test machine can't connect to Microsof's update servers). Then I came across the mentions here and here by chance and started to consult Microsoft's kb articles for all Windows 10 updates from January 2019.

Nearly all Windows 10 builds are affected

On January 17, 2019, Microsoft has updated the KB articles that describe the January 8, and January 15, 2019 updates for Windows 10. It affects the following patches:

  • Windows 10 V1809 and Server 2019: KB4480116 from January 8, 2019
  • Windows 10 V1803: KB4480966 from January 8, 2019 and KB4480976 vom 15. Januar 2019
  • Windows 10 V1709: KB4480978 from January 8, 2019 und KB4480967 from January 15, 2019
  • Windows 10 V1703: KB4480973 January 8, 2019 and KB4480959 January 15, 2019
  • Windows 10 V1607 and Server 2016: KB4480961 January 8, 2019

Update KB4480977 for Windows 10 V1607 and Windows Server 2016, dated January 17, 2019 doesn't mention the issue. Also update KB4480116 from January 8, 2019 for Windows 10 V1507 doesn't mention the issue. It's not clear whether it is only a lack of documentation or if the error has been fixed.

Microsoft confirms the network issue

Within the kb articles mentioned above, Microsoft added (probably at January 17, 2019) the following 'known issue'.


After installing KB4480116, some users report that they cannot load a webpage in Microsoft Edge using a local IP address. Browsing fails or the webpage may become unresponsive.

The above KB number belongs to the article for Windows 10 V1809 update and changes depending on the Windows 10 version.

Microsoft proposes a workaround

Microsoft proposes the following steps as a workaround to enable access to local sites in Edge browser.

1. Open the Control Panel (enter control within taskbar's search box, and click the control panel item shown within the start menu) and select Internet Options.

2. On the Security tab, select the Trusted Sites icon and click the Sites button.

Vertrauenswürdige Sites

3. Clear the check box for Require server verification (https:) for all sites in this zone.

4. In the Add this website to the zone: box, type the local IP address that failed to load, such as and click the Add button.

5. Select again the checkbox Require server verification (https:) for all sites in this zone, then confirm the Close button.

Then click the OK button to close the property page and restart Microsoft Edge. Afterward the local websites should be reachable within Microsoft Edge. Microsoft is working on a resolution and will provide an update in an upcoming release.

Similar articles:
Patchday: Updates for Windows 7/8.1/Server Jan. 8, 2019
Patchday Windows 10-Updates (January 8, 2019)
Network issues with updates KB4480970 and KB4480960
Fix for the Windows 7 SMB network bug caused by Update KB4480970/KB4480960
January 2019 patchday issues
Windows 10 V1607: Update KB4480977 (01/17/2019)

Cookies helps to fund this blog: Cookie settings

This entry was posted in issue, Update and tagged , , , . Bookmark the permalink.

3 Responses to Windows 10 Network bug in all versions, fix are planned

  1. guenni says:

    A German blog reader left a comment decribing his tests – he was able to reproduce the Edge local website issue. He ran a lot of tests – here are his findings (I've translated it into English).

    Could reproduce the issue just in the Edge – the web interface of Fritz!box (router) can't be reached, neither by IP nor by No problem in IE.

    But it gets even crazier:
    – local webserver with local domain of the domain controller (ending .lan): works
    – local web server with external domain name (extension .de) resolved to local IP address: works
    – local web server via local IP address: Error
    – Fritz!Box gets a name on the extension of the local domain ( works (even if error page)
    – Access to a web server from private address space (172.16.x.x) from PC (192.168.x.x) with Edge: works
    – Access to a web server on the Internet via IP address: works

    In a nutshell:
    – servers under the DC's top-level domain can be accessed (can be a special case with .lan)
    – known top-level domain with external IP address can be accessed
    – access to known TLD with local IP is possible
    – Unknown TLD with local IP cannot be accessed
    – An IP address in a private address space can be accessed if the address space of the target differs from the address space of the PC.
    – external IP addresses can be accessed

    Almost had a DNS-over-HTTPS failure in mind, but… that doesn't fit with the fact that an internal web server can be addressed via a local "public domain name" and that the local domain can still be addressed under its name. And so it does not match the error of not being able to address web servers in one's own network via IP address.

  2. Aardvark says:

    I had not had any problems with my systems but my 12 year old niece, who rarely talks to me any longer unless she has computer problems at which point she becomes very talkative, called me to complain about her gaming laptop not connecting to the Internet. It had recently updated and she became disconnected. I finally came to the conclusion that assigning a static IP fixed the problem but that is problematic for her in the long run because she takes her laptop over to friends homes. There were also issues with her "Steam" games not working and not being able to upgrade to 1809 as a possible fix. After spending several hours at work with the laptop running virus scans and other checks, I re-installed 1803 and everything started working again including "Steam". That is until the system (Home, I mean Guinea Pig, Edition) insisted on installing patches at which point it stopped working again. I upgraded her to Professional and deferred future updates for several weeks but I still have more work to do. Possibly removing all of the recent patches or biting the bullet and upgrading to 1809 if it lets me.

    Honestly I am getting sick and tired of this patch "carp". I am 56 and have been fixing busted systems for almost 30 years now and it is getting tiring. Even Apple is no longer a safe bet as garbage iOS releases come out (I still run 10.3.3 because too many associates got burned with iOS 11 and every time iOS 12 updates come out there is something potentially bad with it). I wish the software companies would stop issuing releases based on a calendar date and instead focus on releasing a product when it is ready. Throwing a buggy product into the wild because the calendar says so and then letting people like me deal with the consequences is really pi$$ing me off.

  3. Tom Thomas says:

    This fixed one new issue.
    The other is that streaming tv videos will not display.
    This is new in the last couple days.

Leave a Reply

Your email address will not be published. Required fields are marked *