Microsoft acknowledges bug, provides workaround

Jan 17, 2019 06:51 GMT  ·  By

The most recent cumulative update for Windows 10 version 1809 (October 2018 Update) breaks down Microsoft Edge when trying to load a local page.

Microsoft has already acknowledged the bug, saying that in some cases, Windows 10 cumulative update KB4480116 could cause the page loading to fail or the browser to become unresponsive when a local IP address is being used in Microsoft Edge.

“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,” Microsoft says.

The company recommends users to enable server verification for your local websites that fail to work after installing this cumulative update and says that a fix is already in the works and it should go live “in an upcoming release.”

New update coming in late January

In other words, Microsoft will include a patch in the next cumulative updates for Windows 10 October 2018 Update, though no ETA has been provided this time. Windows 10 version 1809 is the only new Windows 10 version that hasn’t received an update in mid-January, and I expect a new cumulative update to be published by the end of the month.

Microsoft suggests that a new cumulative update is indeed on its way to devices running version 1809 in late January. In a different bug acknowledgment that concerns issues with authenticating hotspots, Microsoft says a solution “will be available in late January.”

The next Patch Tuesday cycle takes place on February 12, and cumulative updates with both security and non-security fixes would be shipped to all Windows 10 versions.

As with every cumulative update that causes issues, removing KB4480116 indeed resolves the Microsoft Edge bug, though users are recommended to stick with the workaround provided by the company. KB4480116 also includes security fixes, so removing it leaves the door open to exploits aimed at patched vulnerabilities.

UPDATE: Microsoft has confirmed that the bug also exists in the other cumulative updates that it released in mid-January, as it follows: KB4480976 (version 1803), KB4480967 (version 1709), and KB4480959 (version 1703).