Win10 1607 Feature Update Install Failure via Servicing

[RLC-Andrew]

Created a CB service plan and ran it. It populated the Package and created the Software update group. The contents of the SUG is "Feature update to Windows 10 Enterprise, version 1607, en-us". It shows downloaded and deployed.

 

On the client side, the client sees the update and downloads it. The contents of the ccmcache folder are these two files:

"WindowsUpdateBox.exe" and a rather long filename ending in "CLIENTENTERPRISE_VOL_x64fre_en-us.esd"

 

Client is current on Win10 Build 10240.

 

When in software center, it begins to install but will fail almost immediately. The software change returned error code "0x8000FFFF" (which seems to be a catastrophic failure).

 

The WUAHandler.log shows this:

 

Going to search using WSUS update source.
Synchronous searching started using filter: 'UpdateID = 'af57b397-b222-494e-ab73-17ddddd6e44e' AND DeploymentAction = *'...
Successfully completed synchronous searching of updates.
1. Update: af57b397-b222-494e-ab73-17ddddd6e44e, 200 BundledUpdates: 1
Update: 08b35ebf-a5f1-416f-8785-ae2ed3feb8e7, 200 BundledUpdates: 0
1. Update (Missing): Feature update to Windows 10 Enterprise, version 1607, en-us (af57b397-b222-494e-ab73-17ddddd6e44e, 200)
Async installation of updates started. WUAHandler 8/29/2016 8:18:04 AM 1700 (0x06A4)
Update 1 (af57b397-b222-494e-ab73-17ddddd6e44e) finished installing (0x8000ffff), Reboot Required? No
Async install completed.
Upgrade installation result indicates that commit cannot be done.
Installation job encountered some failures. Error = 0x80240022. Commit Result = 0x00000001.
Installation of updates completed.

 

Things I have tried:

Removed the update group, package and Service Plan and then re-created them and re-downloaded the Win10 feature update.

Edited August 29, 2016 by RLC-Andrew

[anyweb]

did you do this and the manual steps involved ?

 

https://blogs.technet.microsoft.com/enterprisemobility/2016/08/05/update-your-configmgr-1606-sup-servers-to-deploy-the-windows-10-anniversary-update/

 

if so, try deleting the 1607 updates in WSUS console, and then resync your sup and try servicing again

[RLC-Andrew]

I did have the referenced update installed. I installed it back on 8/19 and did the manual instructions. But just in case, I followed the instructions https://blogs.technet.microsoft.com/wsus/2016/01/29/how-to-delete-upgrades-in-wsus/ (had to change the version/build from the article to reflect the 1607 release) I manually verified the update content was removed, and then re-synced.

 

Unfortunately, the results are the same. Error code 0x8000FFFF.

 

Anymore ideas or logs that could help that I might be missing?

 

It appears that if you did the sync before the update, the error code would be different or more specific (0x8007007E), at least from one user on the internet.

[am845385]

I have also similar issue. Please advise.