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.
 

Discussion Info


Last updated October 17, 2018 Views 53,199 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Don't be in a rush to get it.

They may have pulled it due to an issue some were having.

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

Please mark my posts as answers or helpful if they are.

Teams have dug into this issue and do believe the cause has been identified.

Looks like this will only be hitting a subset of Insiders.  The correct team is developing a fix/workaround and once we have the full details, we'll be posting that information.  For your affected machines, there's no need to keep attempting the install.  It'll keep failing.

In the mean time, hold tight!  We're all over this and will keep sharing information along the way.

*Note*  I edited the title of this thread to add clarity

Don't be in a rush to get it.

They may have pulled it due to an issue some were having.

No rush just curious why it could not be found? But Jason has answered that, thanks.

Wired & Retired Old Mig15 pilot.
The repeal of net neutrality allows and encourages ISP's to act in their own economic interests.
Well, after 3 days of YAFB (Yet another Failed Build), I tried the ISO via the Media Creation tool and, finally, successfully got to 14393.222.
Why hasn't this update been pulled? Clearly there is an issue. Samsung wasn't this slow.

Why hasn't this update been pulled? Clearly there is an issue. Samsung wasn't this slow.
I do not see why it should have been pulled as it is safe. It either installs successfully or rolls back gracefully. Quite acceptable for a preview phase.

Why hasn't this update been pulled? Clearly there is an issue. Samsung wasn't this slow.

Seriously! Samsung products were causing fires and blowing up.

This update does neither of those, it just won't install.

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

Please mark my posts as answers or helpful if they are.

Same problem here on over a dozen machines.

Now can't switch rings either because failed update prempts newer builds.

Terrible situation...

Talmage D. Holt
Terrible situation, I'll try ISO...
Talmage D. Holt

Same problem here on over a dozen machines.

Now can't switch rings either because failed update prempts newer builds.

Terrible situation...

I was told here on this forums recently there is no way how to cancel a staged build upgrade. Unfortunatelly.

However, it should disappear after that particular staged build is marked as obsolete by Microsoft. Fortunatelly.

Note: I was not told this but it happened to me. The actual reason why it disappeared might have been different than I have presumed.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.