Windows 10 1709 (Fall Creators Update) failed update

Nov 25, 2017: update to my last posting....

After some discussions with MS Support, and the manufacture of my computer (withholding name at the moment), I have found out the following information and solutions that worked for me:

The issue:  The feature update, called Fall Creators Update 1709, will continue to Download-Install-Fail then repeat, thus tying up CPU and disk resources and slowing down the computer. The Fall Creators Update 1709 does have issues and is being addressed for a later update release. 

2. For Windows 10 Pro users, there is a workaround to delay "Feature Updates", like the Fall Creators Update 1709, yet allow other essential updates (i.e. security updates) to pass through. This workaround ONLY delays the update for a few weeks (I thought they said 60 days).

WORKAROUND: 

Go to Settings/Update and Security/Windows Update/Advanced Options, move the the Defer Options switch to the ON position, then reboot. To verify this workaround did work, pull up the Task Manager and look to see if the CPU and Disk resource percentage drop considerably from 100%. After reboot, allow about three to four minutes before looking at the disk resource percentage (reboot might take a few minutes to complete before providing a true reading). If you do not have Windows 10 Pro, you can get an update from the Microsoft store for $99.99. 

3. For Windows 10 Home users, there is a workaround to stop all updates indefinitely.  As a warning, this is the least desirable solution because I was informed that ALL updates are blocked, including Security Updates. As for me, I'm willing to take that risk, at least until Windows 10 stabilizes a little more, especially with the forced feature update installations (like 1709). I was informed that merely setting the System Services "BIT" and "Window Update" settings to the Disabled state, then rebooting, would affect other Windows 10 functions, so that IS NOT considered a good option. Instead, the workaround below, made to the registry, should be implemented instead:

WORKAROUND: 

a. Press the Windows key + R and type Regedit followed by Return. 

b. Select HKEY_LOCK_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES.

c. Make a copy of the WAUSERV file (located just above the Wudfpf file) and save a copy (I saved a copy to the Documents folder). Make sure you add the .reg extension when you save. You will need this file later for re-installation.

d. Delete the WAUSERV file from the registery then reboot the computer.

e. To verify this workaround did work, pull up the Task Manager and look to see if the CPU and Disk resource percentage drop considerably from 100%. After reboot, allow about three to four minutes before looking at the disk resource percentage (reboot might take a few minutes to complete before providing a true reading).

NOTE: At some later date, when Windows 10 feature updates have stabilized, the save registry file needs to be placed back followed by a reboot.

I have experimented both of the above solutions and they both worked for me. Let me know if these workarounds worked for you.

Don A.

My worry about delaying the fall update is that I may miss some important security updates....

The other option being thrown around is rebuild your windows 10 from scratch..  (this is very time consuming and no real guarantees)

Given Microsoft see the problem... are there any ways to track down the cause and fix it?  Most of the logs that people point to either have no useful information or too many errors..  (which seem to happen on my other systems that made it through the 1709 update....)

This is a very frustrating problem...  I have lost over 40 hours working on possible solutions....  

Any hope Microsoft will fix this soon???

Hi,

Based on the details provided on this thread, we recommend that your submit a feedback regarding this matter. In order to submit a new feedback, kindly follow these steps:

1. On a Windows 10 device, search for "Feedback Hub"in Cortana search, and then launch the app.
2. Navigate to Feedbackin the left menu, and then press + Add new feedback.
3. Select the Problem, and share any details you think are relevant, and then choose an appropriate category and subcategory.
4. Important: If possible, reproduce the problem(s) after clicking Begin monitoring(or Start capture) near the end of the form; Stop monitoringwhen you're done.
5. Once you've completed the form and monitoring, click Submit.
6. Click Continue using Feedback Hub.
7. Click My Feedbackat the top, and then find the item you submitted (it may take a while to appear).
8. Open the item you submitted, and then click Share.
9. Click Copy link, and then paste the link in your response (it will look like https://aka.ms/<uniquelink>).

For more information, kindly refer to the link.

Let us know if you have further queries.

Regards.

Don, thanks for the info.  I have not tried it yet but a lot of people are going to want to shut off ALL updates after this fiasco.  Changing the registry is always dangerous but it might confuse people when the names are incorrect. 

LOCK should be LOCAL

wauserv should be wuauserv

Now I hope I didn't make any mistakes. :)