As of January 17, 2019, Windows 10 cumulative updates, Microsoft has added a known Issue to the KB articles in Windows 10 updates. There, the company writes that some users report issues after installing KB4480116, some of the local websites cannot be accessed through the local IP address in the Microsoft Edge web browser. So, because of this patch, the Webpage may fail or stop responding.
The relevant KB4480116 release note contributions say that the company is working on a solution and wants to correct them with one of the future updates. Previously, a reader of Howtoconnect already pointed out in the comment section that after installing the Windows 10 update his telecom router was no longer available.
Solution to January 2019 Cumulative Updates Network Issues in Windows 10 by Microsoft itself
For affected users, Microsoft provides a solution of the Network Issues by including the sites in the list of trusted sites. See in simplified steps –
Step1: Open Contro panel.
Step-2: Click on the Internet Options.
Step-3: Navigate to the Security tab, and select the Trusted Sites icon. Then click the Sites button.
Step-4: In the “Trusted sites” dialog box, clear out the check mark “Require server verification (https:) for all sites in this zone”.
Step-5: Enter the URL of the affected local website (eg “http://188.8.131.52”) in the field “Add this website to the zone” and confirms the “Add” button.
Step-6: Finally, in the Trusted Sites dialog box, check the “For this zone requires server verification (https 🙂 required” checkbox.
Step-7: Close the dialog box via the “Close” button and the “Internet Options” properties window using its OK.
After you restart the Microsoft Edge browser, the local web pages must be accessible.
Affected Windows 10 updates and versions with January 2019 Cumulative Updates Network Issues
Once evaluating all KB articles about Windows 10 patches for January 8 and 15 2019, the following updates are affected by the error –
Windows 10 Version 1809 and Server 2019 –
KB4480116 January 8, 2019
With the update KB4480977 arrived on January 17th, 2019 for Windows 10 Version 1607 and Server 2016 the bug is not listed anymore. The same is applicable to patch from January 8, 2019, for Windows 10 Version 1507. There it is not clear whether this is a lack of documentation or the error does not occur there.