[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 heise.de. 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.
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 http://192.168.0.1 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.
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