Cumulative updates once again causing headaches

Mar 23, 2018 07:36 GMT  ·  By

Microsoft released a bunch of out-of-band cumulative updates for Windows 10 a few hours ago, and now we’re already seeing the first reports of issues and failed installs.

While this has become a common thing for Windows 10 cumulative updates, it’s important to note that at this point, these bug reports don’t seem to be too widespread, though it remains to be seen how many systems are affected as more are being offered the patch.

This time, the one causing headaches is KB4089848, which was specifically aimed at systems running the Fall Creators Update (version 1709).

First, we have one user complaining on Microsoft’s Community forums of a failed install that looks a lot like the issues previously experienced with other cumulative updates as well.

“I started the update today and it seemed to be running fine. It then restarted my Surface and only loaded as far as the surface loading screen with an error message advising windows could not complete the installation. To install Windows on this computer, restart the installation. Every time I try to restart it returns me to the error message,” the poster explains.

Failed installs and possible BSODs

Then, there are several complaints published on reddit, where several users said that KB4089848 takes a lot of time to install. Despite the update seemingly getting stuck during deployment, it eventually completed fine, though waiting for more than an hour to install an update isn’t the expected behavior.

User FxKaKaLis says the update failed with error 0x8024200d no less than six times before eventually installing fine after the seventh attempt, while another poster claims that KB4089848 broke down the Start menu, Action Center, Volume, Edge, and the Calendar.

Finally, user dinosaur_friend reveals that this update could cause a BSOD on your system, but it appears that the install went fine in their case.

Microsoft hasn’t yet acknowledged these issues with its new cumulative updates, but we’ll continue to monitor these reports and see if more users complain of similar problems.