Microsoft Fixes Borked Windows 10 Update

Posted on October 6, 2016 by Paul Thurrott in Windows 10 with 24 Comments

Microsoft Fixes Borked Windows 10 Update

Microsoft has issued a script that fixes a borked cumulative update for Windows 10 that gets stuck in endless loop of failed installed attempts. We also have some clarity, finally, on which users are impacted by this bug.

As you may recall, Brad reported last week that KB3194496 was causing problems for some Windows 10 users. The issue? It wouldn’t install but would install get stuck in an endless loop of failed install attempts.

“The update, when it does fail, is causing some machines to restart, often multiple times, as Windows 10 attempts to remove the failed update,” he explained. “Worse, after a restart, the file will attempt to install again resulting in the loop of failed install, reboot, re-install and failure again.”

The biggest mystery was that this issue only impacted some users. Many were able to successfully install KB3194496, as with most other cumulative updates.

Well, today we know the reason. And, better, we have a fix.

According to Microsoft, an issue KB3194496 only impacted “a small number of customers in the Windows Insider Program that were running a previous build of the OS.” In other words, this bug impacted people who had previously installed a Windows 10 Insider Preview build but then later reverted to the shipping version of Windows 10 version 1607 on that PC.

The fix is available in the form of a new update, KB3197794, which you can download from the Microsoft web site. Obviously, if you’re up to date and everything is working properly, there’s no need to install this update. But if you’re stuck in that endless borked install loop, this should do the trick.

Microsoft first provided information about this fix to ZDNet. For some reason. Hey, guys: Next time you fix something, tell the world. Just a thought.


Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (24)

24 responses to “Microsoft Fixes Borked Windows 10 Update”

  1. 5610

    "only impacted “a small number of customers in the Windows Insider Program that were running a previous build of the OS.”

    Well thats not at all true, i had more than a few customers that were certainly not insiders, experiencing this issue.


  2. 4690

    hmmm. Insider track? I ran into this problem on a machine that never had an insider install on it. 

  3. 442

    I already had a good fix:

    Fix KB3194496 Installation Failure

    To fix the installation problem, you will have to delete a folder in the C drive and an entry in the Windows registry. You must have Admin rights in order to do this.

    Step 1: Open Windows Explorer and go to C:\Windows\System32\Tasks\Microsoft\XblGameSave. Delete the folder ‘XblGameSave’

    Step 2: Open the Windows Registry editor and go to:


    Delete the XblGameSave key.

    Step 3: Restart your PC and run the update again. It should install without further problems.

    Works like a charm

  4. 6087

    Well, on the two computers I have that ran into the AU problem (but were fixed with reboots), they never had an Windows 10 Installer Preview build previously installed and then later reverted to the shipping version of Windows 10 1607. Mmmmmmm.

  5. 1485

    Several day's ago someone posted the complete fix. It was deleting a folder and in the registry 1 key. Then it would install.
    But I am disappointed that Microsoft could not detect that failed update and tryed to reinstall it anyway instead of marking it as failed and waited for a new update or a fix.

    Also it took several day's to create a small script to do it?
    Come on Microsoft. You can do better.

    • 180

      In reply to Rob Jansen:

      To a degree, this is good news though. If this affected users who were Insiders, it ought to have only affected those with the technical chops to work through it, rather than the average user.

  6. 5577

    If they're going to software as a service then they need to get a lot better at the "service" side of things.

  7. 5566

    I'm on the slow ring and KB3194496 failed 3 times.

  8. 5637

    I had this issue on a laptop previously enrolled in the insider program. Worked like a charm. 

  9. 5504

    After my daughters laptop was updated a few days ago (not insider build) her PIN was no longer recognized. Now the option to set a PIN is no longer in settings. There's supposed to be a work-around that involves deleting a system file, but I'm not really interested in going down that rabbit-hole.

  10. 6163

    I have no earlier Insider Preview Build. My machine just installed th ed updates that Microsoft forced on us. The computer boots in an endless loop of Login, Desktop, then reboot. Safe Mode doesn't even help because I can't get any Internet access, nor does Windows Explorer work anymore either. Everything worked fin until the Anniversary Update! I read in some other posts that it might affect my machine because I have Windows running from an SD drive and a second drive for storage of data.

  11. 5234

    This doesn't explain the same constant rebooting that people with the Chinese IME are facing with this same update.  Someone should be fired over the quality of this update, or just AU in general.

    Get Linus after them!

  12. 5394

    Why can't both Premium and Non-Premium Comments be combined? Makes it easier to read.

    How will those stuck on the endless loops ever install the fix? I suppose that's why there's a problem.



    • 1044

      In reply to glenn8878:

      Personally, I would prefer not to have them combined.  This way it's easier to filter out all the trolls who typically won't bother to pay for the premium membership.  I only have to venture into that cesspool if I'm feeling especially masochistic.

    • 1777

      In reply to glenn8878:

      I also agree the comments should be combined.

  13. 5400

    Not sure why we can't click on the non premium comments, unless they are all testimonials for making thousands of dollars at home by surfing the internet.

  14. 351

    My Surface Pro 3 has this problem, but I'm still on the Insider Preview.  I'm on the Slow Ring, but I think I switched it to that after my first evening of this update failing multiple times, hoping that it was an update associated with the Fast Ring.  Anyway, there explanation doesn't make sense since I'm an Insider Preview user with this problem.