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.

Microsoft needs to WITHDRAW this update, fix it, and re-send it. You just DON'T send out something that crashes or stalls computers, esp when the fix is to "reset" the pc wiping out all software. Seriously? I mean...seriously? There's probably nothing

of substance in this "feature" update, anyway.

I've tried to install this feature update about 15 times, and used about 10 suggested solutions. So time-consuming and frustrating. The Help Desk giving me the "solution" of re-installing the operating system and then re-installing all of my work & personal software and applications from scratch for a quarterly feature update is ridiculous! For now, my solution is going to have to be [Settings>Updates & Security>Windows Update>Advanced Options>"A feature update includes new capabilities and improvements. It can be delayed for this many days:"] ... and then I selected 110 days. I will then have access to the next quarterly update which I hope won't want to kill my computer. I just hope I am not wrong about the next feature update. Microsoft needs to WITHDRAW this update, fix it, and re-send it.

I have tried all the advice above and then some...

In addition to the stuff below.. I tried the troubleshooter several times..  Manual Updates....  All go to about the 46% mark .. and then get a problem working with windows system component configuration...

Some of the posts point to log files which have changed in windows 10....

Anyone get this problem solved???

From your description, I understand that Windows Update on Windows 10 1703 indicated that the feature update to 1709 has been downloaded and requires a restart to finishing installing, however, it still requires restart even restarted four times.  If anything is misunderstood, please feel free to let me know.

Before moving on, could you please help me verify the information below?

1.      What is the build number of current Windows 10? Please capture a screenshot of the result when run winver

2.      If we upgrade current machine by clicking “Update now” in the link below, will it update properly?

https://www.microsoft.com/en-us/software-download/windows10

3. If it still cannot update properly, is there any error message occur? If there is any error message, it would be appreciated if you provide a screenshot of it or paste it here.
4. Have you made any system restore points before?

To narrow down this issue, could you please follow the methods below to have a test?

Method 1:

Run Windows Updater troubleshooter:

======================

https://support.microsoft.com/en-sg/help/4027322/windows-windows-update-troubleshooter

Method 2:

1.      Open an elevated command prompt

2.      Type and run the following command:

Sfc /scannow

Dism /online /cleanup-image /restorehealth

3. Then check if the issue still persists

Method 3:

1.      Open an elevated command prompt

2.      Run the following command:

net stop bits

net stop wuauserv

net stop appidsvc

net stop cryptsvc

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

net start bits

net start wuauserv

net start appidsvc

net start cryptsvc

3. Exit command prompt and check if the issue persists

Method 4:

1.      Open registry editor by running regedit.exe

2.      Back up the registry first before making changes to it

3.      Navigate to HKLM\System\CurrentControlSet\Control\Session Manager

4.      Check if PendingFileRenameOperations exists under the Session Manager key

5.      If it exists, please remove it

6.      Restart computer and check if issue persists

If the issue persists,  please follow the steps below and send the CBS log to the e-mail address in private message.

1.      Rename the CBS.log(%systemroot%\Logs\CBS\CBS.log) to CBS.old

2.      Manually update the computer again and restart computer if needed

3.      Send the new generated CBS.log.

If anything is unclear, please feel free to let me know.

Best regards,

Janet Wu

Microsoft Partner Support Community Technical Support Engineer

Microsoft Global Partner Services

This posting is provided "AS IS" with no warranties, and confers no rights.

Please Mark As Answer if this post is helpful to you. Thanks for your cooperation.

Reply

Same here. Update, Restart, old build. Thanks MS for wasting my time