Here’s another cumulative update causing trouble for users

Apr 12, 2017 06:47 GMT  ·  By
Here's what YouTube ends up looking like after installing this cumulative update
   Here's what YouTube ends up looking like after installing this cumulative update

Even though everything seemed to work smoothly at first, it now looks like Windows 10 cumulative update KB4015217 is hitting some issues as well on a number of Anniversary Update systems.

First and foremost, some background. KB4015217 is this month’s cumulative update for computers running the Windows 10 Anniversary Update (version 1607), and it includes not only fixes and performance improvements but also security patches, as it lands on Patch Tuesday.

Just like its predecessors, KB4015217 seems to be affected by problems during the install, but also after deployment, though it’s not yet clear at the moment how widespread these issues actually are.

KB4015217 issues

One of the common complaints of users running the Anniversary Update and being offered this cumulative update in April is that the installation process freezes at a certain percentage level.

What’s important to know is that although the process appears to get stuck all of a sudden, the install continues in the background, so just give it some time and it should complete successfully.

On the other hand, there are users complaining about bigger problems, including black screens that appear to be caused by this cumulative update. Here’s how one reddit user explains the problem:

“I got it installed, and now I have nothing but black screens. It goes to the the welcome screen and shows my picture and a pretty picture in the background and then it goes to a black screen I have a cursor and it responds to krys from the keyboard at least control alt delete but I can do nothing except shut down, the computer is completely ruined.”

A quick Google search confirms there are more users hitting problems with this cumulative update and many of them are complaining of the same black screen issue.

Microsoft is yet to acknowledge these problems, so it remains to be seen if a fix will ever be released or users need to search for a resolution on their own.