{"id":8328,"date":"2019-01-18T09:58:42","date_gmt":"2019-01-18T08:58:42","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=8328"},"modified":"2022-10-09T22:18:00","modified_gmt":"2022-10-09T20:18:00","slug":"windows-10-network-bug-in-all-versions-fix-are-planned","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/01\/18\/windows-10-network-bug-in-all-versions-fix-are-planned\/","title":{"rendered":"Windows 10 Network bug in all versions, fix are planned"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/win102.jpg\" width=\"58\" height=\"58\" align=\"left\" \/>[<a href=\"https:\/\/www.borncity.com\/blog\/2019\/01\/18\/windows-10-netzwerkbug-fix-soll-spter-kommen\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]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.<\/p>\n<p><!--more--><\/p>\n<h2>Some error reports<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg04.met.vgwort.de\/na\/f20fb8716fd34c6da57db40fd2bfe6a9\" alt=\"\" width=\"1\" height=\"1\" \/>I confess, I wasn't really aware of this issue, because I didn't notice the real thing, when I first read <a href=\"https:\/\/www.heise.de\/forum\/heise-online\/News-Kommentare\/Windows-7-Updates-KB4480970-und-KB4480960-verursachen-Netzwerkprobleme\/Nicht-nur-7-auch-windows10\/thread-5849978\/\" target=\"_blank\" rel=\"noopener\">this German comment<\/a> on my German article <a href=\"https:\/\/www.heise.de\/meldung\/Windows-7-Updates-KB4480970-und-KB4480960-verursachen-Netzwerkprobleme-4270472.html\" target=\"_blank\" rel=\"noopener\">Windows 7: Updates KB4480970 und KB4480960 verursachen Netzwerkprobleme<\/a> published at German site heise.de. The user reported an 'exotic flaw' (here is my translation):<\/p>\n<blockquote><p>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.<\/p><\/blockquote>\n<p>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 <a href=\"https:\/\/web.archive.org\/web\/20191116212653\/https:\/\/news.softpedia.com\/news\/windows-10-cumulative-update-kb4480116-causes-browsing-issues-524584.shtml\" target=\"_blank\" rel=\"noopener\">here<\/a> and <a href=\"https:\/\/mspoweruser.com\/microsoft-ports-network-bug-to-all-versions-of-windows-10-fix-coming-next-month\/\" target=\"_blank\" rel=\"noopener\">here<\/a> by chance and started to consult Microsoft's kb articles for all Windows 10 updates from January 2019.<\/p>\n<h2>Nearly all Windows 10 builds are affected<\/h2>\n<p>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:<\/p>\n<ul>\n<li>Windows 10 V1809 and Server 2019: <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480116\/windows-10-update-kb4480116\" target=\"_blank\" rel=\"noopener\">KB4480116<\/a> from January 8, 2019<\/li>\n<li>Windows 10 V1803: <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480966\" target=\"_blank\" rel=\"noopener\">KB4480966<\/a> from January 8, 2019 and <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480976\" target=\"_blank\" rel=\"noopener\">KB4480976<\/a> vom 15. Januar 2019<\/li>\n<li>Windows 10 V1709: <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480978\" target=\"_blank\" rel=\"noopener\">KB4480978<\/a> from January 8, 2019 und KB4480967 from January 15, 2019<\/li>\n<li>Windows 10 V1703: <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480973\" target=\"_blank\" rel=\"noopener\">KB4480973<\/a> January 8, 2019 and <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480959\" target=\"_blank\" rel=\"noopener\">KB4480959<\/a> January 15, 2019<\/li>\n<li>Windows 10 V1607 and Server 2016: <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480961\" target=\"_blank\" rel=\"noopener\">KB4480961<\/a> January 8, 2019<\/li>\n<\/ul>\n<p>Update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480977\" target=\"_blank\" rel=\"noopener\">KB4480977<\/a> for Windows 10 V1607 and Windows Server 2016, dated January 17, 2019 doesn't mention the issue. Also update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4480116\/windows-10-update-kb4480116\" target=\"_blank\" rel=\"noopener\">KB4480116<\/a> 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.<\/p>\n<h2>Microsoft confirms the network issue<\/h2>\n<p>Within the kb articles mentioned above, Microsoft added (probably at January 17, 2019) the following 'known issue'.<\/p>\n<blockquote><p>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.<\/p><\/blockquote>\n<p>The above KB number belongs to the article for Windows 10 V1809 update and changes depending on the Windows 10 version.<\/p>\n<h2>Microsoft proposes a workaround<\/h2>\n<p>Microsoft proposes the following steps as a workaround to enable access to local sites in Edge browser.<\/p>\n<p>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 <em>Internet Options<\/em>.<\/p>\n<p>2. On the <em>Security <\/em>tab, select the <em>Trusted Sites<\/em> icon and click the <em>Sites<\/em> button.<\/p>\n<p><img decoding=\"async\" title=\"Vertrauensw\u00fcrdige Sites\" src=\"https:\/\/i.imgur.com\/XoSzB5J.jpg\" alt=\"Vertrauensw\u00fcrdige Sites\" \/><\/p>\n<p>3. Clear the check box for <em>Require server verification (https:) for all sites in this zone<\/em>.<\/p>\n<p>4. In the <em>Add this website to the zone: <\/em>box, type the local IP address that failed to load, such as <em>http:\/\/192.168.0.1 <\/em>and click the <em>Add <\/em>button.<\/p>\n<p>5. Select again the checkbox <em>Require server verification (https:) for all sites in this zone<\/em>, then confirm the <em>Close <\/em>button.<\/p>\n<p>Then click the <em>OK<\/em> 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.<\/p>\n<p><strong>Similar articles:<br \/>\n<\/strong><a href=\"https:\/\/borncity.com\/win\/2019\/01\/09\/patchday-updates-for-windows-7-8-1-server-jan-8-2019\/\">Patchday: Updates for Windows 7\/8.1\/Server Jan. 8, 2019<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2019\/01\/09\/patchday-windows-10-updates-january-8-2019\/\">Patchday Windows 10-Updates (January 8, 2019)<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2019\/01\/09\/netzwerk-issues-with-updates-kb4480970-and-kb4480960\/\">Network issues with updates KB4480970 and KB4480960<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2019\/01\/12\/fix-for-the-windows-7-smb-network-bug-caused-by-update-kb4480970-kb4480960\/\">Fix for the Windows 7 SMB network bug caused by Update KB4480970\/KB4480960<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2019\/01\/14\/januar-2019-patchday-probleme-und-nachlese\/\">January 2019 patchday issues<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/win\/2019\/01\/18\/windows-10-v1607-update-kb4480977-01-17-2019\/\" rel=\"bookmark\">Windows 10 V1607: Update KB4480977 (01\/17\/2019)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[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.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22],"tags":[47,1309,195,76],"class_list":["post-8328","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","tag-issue","tag-network","tag-update","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8328","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=8328"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/8328\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=8328"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=8328"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=8328"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}