KB3194496 causing problems on Windows 10 PCs

Sep 30, 2016 07:57 GMT  ·  By

KB3194496 was officially released to retail users earlier today even after insiders complained of installation issues, so it’s no surprise that many more PCs are hit with the same problems.

Users who rushed to install this cumulative update are now reporting the same bugs as with the previous releases, explaining that, on some PCs, it fails to install successfully with an error saying just “Undoing changes.”

“Fails to install for me, tried 3 times. Every time I get an 'undoing changes...' screen during the reboot. I'll just wait if there'll be another update to fix that,” one user explains on Reddit.

“I keep getting Undoing changes, couldn't install updates. I have tried troubleshooting windows update. I get the following error is event viewer: 0x800F0922 and a few AppReadiness errors,” another one added.

No workaround available

For the moment, there is no workaround available, but what’s important to know is that the number of complaints coming from users who installed it is substantially smaller than for previous cumulative updates.

Most likely, Microsoft is already looking into these reports and, if a fix is necessary, it could be released in the coming weeks. A new cumulative update should land on October 11 when Microsoft rolls out Patch Tuesday updates, but it remains to be seen if a different one could arrive in the meantime.

What’s also critical to know is that there were users who claimed that KB3194496 got stuck at 45 percent during the downloading process, a bug that was already experienced by some people with previous cumulative updates.

This time, however, patience is really a virtue, and if you wait long enough, the process should complete successfully and, luckily, the update would install smoothly too. There are only a few reports pointing to this bug, so it’s probably just a minor issue that should be resolved in the next cumulative updates.

We’ll keep an eye on more reports pointing to problems with cumulative update KB3194496 and will let you know should a workaround be discovered.