Microsoft preparing a “clean-up script” for failed Windows 10 version 14393.222 installs (updated)

As you may recall, over this weekend, a select group of Windows 10 users reported that Windows 10 Build 1493.222 left their computers in an infinite installing update loop. Now a few days after, Microsoft has finally broken their silence on the issue, and has said it is preparing a “clean-up script” for failed Windows 10 version 14393.222 installs (via Neowin.)

Official word on an incoming fix was first spread on this Microsoft Support Forms page, where a Microsoft forum moderator named Jason posted that patience is required during research and subsequent work while the fix is being made. He writes:

“Hello Insiders!

We’ve been working diligently on this issue and are finalizing a clean-up script that will fix the underlying issue preventing the install of  KB3194496 (Cumulative Update 14393.222) for affected users.  Your patience during our research and subsequent work is greatly appreciated.
Thank you as always and stay tuned!”

Several other Windows Insiders on the same forum, however, have posted workarounds for the issue, all of which are risky and involve altering the system registry and deleting certain folders. So, if you’re experiencing the infinite installing update issue, you might want to try the workarounds seen in the forum (at your own risk!) until the official fix has been released by Microsoft. As always, let us know what you think of this latest set of news, and your other thoughts by dropping us a comment below.

Update: Microsoft has since issued a clarification, reiterating that a solution is forthcoming, and that the issue affected a small number of Windows Insiders:

“We are aware of an issue with the recent Windows 10 cumulative update that impacted a small number of customers in the Windows Insider Program that were running a previous build of the OS. We expect to have a solution in place for these customers soon, and will be communicating with Insiders via the Feedback Hub.”

We’ll keep you posted on a fix.

Share This
Further reading: , ,