Release Preview: 14393.222 CU Available (and possible issue installing)

There is a new update for Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3194496).

This brings you to build 14393.222. This is only available if you are an insider that has release preview.

Update October 6, 2016: Official Fix

Microsoft has issued an official script here that will fix this problem.  The previous workarounds are still listed below.

Previous Workaround Solutions

If it cannot install the update and rolls back (you'll see "undoing changes..." followed by another reboot), here are verified solutions:

  1. Bypass Windows Update by installing the latest version directly [Simple]
    Solution posted by Sean8102 on October 1st (page 16)
    Go to the Get Windows 10 webpage and click download tool now.  When you run the tool, select "Upgrade This PC Now" and choose to keep everything (files, apps, and settings).  This will apply the update directly without impacting any of your installed programs at all.  You can also use the tool to create a bootable USB stick and install from that, but no USB stick is necessary if you use the "Upgrade This PC Now" option.


  2. Remove Tasks and Registry for Tasks that that Block The Update [Advanced]
    Solution posted by TomislavRex on October 3rd (page 23 with additional details on page 29)
    Deleted all references to task  \Microsoft\XblGameSave\XblGameSaveTask in the System32 folder, AND all traces of them from the registry (in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache tree.  Noted that deleting some of these involved changing ownership of the keys. The tasks have been recreated during the installation of the update.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Ed Bott in a new article today says that Microsoft in an e-mailed statement claims that the failed update was largely an issue for Insiders who left the program for a production version of the 1607 Anniversary update.

http://www.zdnet.com/article/microsoft-releases-fix-for-windows-10-cumulative-update-issues/

As a Windows Phone user and a Microsoft Band 1 user (has totally fallen apart) and a DOS/Windows user since 1983, it does seem to me that Microsoft's general direction in the consumer market is downhill and the imbroglio we're discussing is not one that makes and keeps happy customers. 

Still failing for me.  Tried every version of the fix I've found online.

I questioned John Wink MSFT about the fix and this is the answer.

@johnwinkmsft If we already have 14393.222 do we or should we apply this fix? Or are we good for the next CU?

@CrazyCatsGot2 Did you use one of the workarounds to get .222 on your machine? If you disabled but didn't delete the tasks, I'd run this too

***********
*********

Please mark my posts as answers or helpful if they are.
Those are completely different issues to the ones we are having

My question is simple.

Do those of us that got the update finally installed

have to run this script fix?

I did not use the XblSave fix.

I tweeted Jason this question, so hoping for an answer tomorrow.

Probably should run the fix still, thats what i did. From what ive read here it looks like the problem can still persist even after the media creation tool is run, otherwise it may come back to haunt you later. 

My question is simple.

Do those of us that got the update finally installed

have to run this script fix?

I did not use the XblSave fix.

I tweeted Jason this question, so hoping for an answer tomorrow.

Probably should run the fix still, thats what i did. From what ive read here it looks like the problem can still persist even after the media creation tool is run, otherwise it may come back to haunt you later. 

I already posted the answer from John and I 

have also applied the script fix.

***********
*********

Please mark my posts as answers or helpful if they are.
Actually, Microsoft, if it has any brains, will make sure that the next update addresses any vestigial effects of imperfect .222 updates,  What if we had a "completely successful" update to .222?  Does that mean our computers have no residual crud related to the  .222 update that still needs to be fixed?  Amazing that Microsoft just e-mails and tweets folks about this as opposed to issuing clear statements to the general public explaining stuff.

I tried everything.

The automatically update doesn't work.

After a few minutes and a reboot, the counter counts to 99% and then I got the info, that the update can't be installed and the files, which was installed will be removed. Then the system will be rebooted. There is no boot-loop.

That happens with KB3189866 and KB3193494.

Then I try the script yesterday, after that I run update (without reboot), the system tried to install KB3193494, same as above. Same try with reboot after the script, same result as above.

Today then I saw the new update KB3194496. I downloaded it. I've started the script before. Then I start the update. It installs on Windows. Then the System ask to reboot. In the reboot then the same as above!

I didn't have any ideas, but it's frustration...

I tried everything.

The automatically update doesn't work.

After a few minutes and a reboot, the counter counts to 99% and then I got the info, that the update can't be installed and the files, which was installed will be removed. Then the system will be rebooted. There is no boot-loop.

That happens with KB3189866 and KB3193494.

Then I try the script yesterday, after that I run update (without reboot), the system tried to install KB3193494, same as above. Same try with reboot after the script, same result as above.

Today then I saw the new update KB3194496. I downloaded it. I've started the script before. Then I start the update. It installs on Windows. Then the System ask to reboot. In the reboot then the same as above!

I didn't have any ideas, but it's frustration...

I fixed this issue on 2 PCs (Home and Pro) by using the Media Creation Tool to install 14393 again which took these  PCs to 14393.222.  I used an Enterprise 14393 ISO to take that PC to 14393.222.  My Pro and Enterprise have now gone to 14393.223 using the Microsoft installer.

I have a separate thread on the update to 14393.223.

Mel

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Discussion Info


Last updated September 9, 2020 Views 54,544 Applies to: