New cumulative update, new problems for a number of users

Jun 15, 2016 05:22 GMT  ·  By

Microsoft rolled out Windows 10 cumulative update KB3163018 a few hours ago, and it turns out that just like the previous CUs, this new one is also causing issues on a number of PCs.

Frequent Softpedia readers might recall that we’ve reported installation issues with many other cumulative updates that Microsoft has rolled out for Windows 10 in the previous months. Still, no matter how hard the company has struggled to get this one right, KB3163018 also appears to be suffering from the same problems.

For the moment, however, it’s important to note that these are just isolated reports, and it’s not very clear how widespread the KB3163018 installation issues actually are. But this is exactly how it started in the case of all the other cumulative updates, and the number of complaints is likely to grow as more people install it.

“Undoing changes”

The most common report reveals that KB3163018 fails to install and then the installer undoes changes to get users back to the desktop. Windows Update then re-attempts to install the same update, so PCs are pushed into some kind of update loop that can’t be stopped unless the patch installs successfully or users manually hide KB3163018.

In some cases, users claimed that they were getting BSODs after installing this new cumulative updates while others explained that various Windows 10 features stopped working correctly due to changes brought by the patch.

On the other hand, it looks like a big number of users actually managed to install the cumulative update successfully, so Microsoft is doing a good job of reducing the crash rate of its patches.

As usual, if you’re experiencing any problems installing this cumulative update, you need to make yourself heard because Microsoft engineers are out there to collect data on reported crashes and to provide a workaround should any exist.

We’ll keep an eye out for more reports and determine how widespread these issues actually are and will let you know with updates to this story.

UPDATE, June 16: It apepars that similar issues are being experienced by many more users, but Microsoft is yet to officially acknowledge these issues. For the moment, the only workaround seems to be the traditional patch uninstalling.