Windows 10 Cumulative Update KB4480116 Causes Browsing Issues

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 instances, Windows 10 cumulative update KB4480116 could cause the page loading to fail or the browser being unresponsive whenever a local IP address is being used in Microsoft Edge.

“After installing KB4480116, quite a few users are convinced that they can’t load a website in Microsoft Edge utilizing a local IP address. Browsing fails or even the webpage may become unresponsive,” Microsoft says.

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

“New update coming in late January”

Quite simply, Microsoft will include an area 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 brand new cumulative update to be published by no more the month.

Microsoft shows that a new cumulative update is indeed coming to devices running version 1809 in late January. Inside a different bug acknowledgment that concerns issues with authenticating hotspots, Microsoft says an answer “will be available at the end of January.”

The following Patch Tuesday cycle happens last month 12, and cumulative updates with both security and non-security fixes could be shipped to any or all Windows 10 versions.

As with every cumulative update that causes issues, removing KB4480116 indeed resolves the Microsoft Edge bug, though users are suggested to stay using the workaround supplied by the organization. KB4480116 includes security fixes, so removing it leaves the doorway open to exploits aimed at patched vulnerabilities.

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

Leave a Reply

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