Windows updates are failing

No - they are residual files left over from running CheckSUR, and in theory should have been deleted automatically - you can delete them manually, but you may have to take ownership of them first.

back later.

NoelDP said:

No - they are residual files left over from running CheckSUR, and in theory should have been deleted automatically - you can delete them manually, but you may have to take ownership of them first.

back later.

The normal practice is that WU finds the partition with the most available space. So yes, it's possiby quite normal.

OMG! Sorry!
back later with the promised fix.

I've uploaded a file - sh2ac.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\sh2ac
hit the enter key - if you get a 'Not Found' error try
DIR D:\sh2ac
or
DIR E:\sh2ac



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\sh2ac <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

Hmmm-

Code:

Line 4252: 2014-09-06 13:42:56, Info                  CSI    0000031f [SR] Repairing 2 components
 Line 4253: 2014-09-06 13:42:56, Info                  CSI    00000320 [SR] Beginning Verify and Repair transaction
 Line 4256: 2014-09-06 13:42:56, Info                  CSI    00000322 [SR] Cannot repair member file [l:20{10}]"WUDFRd.sys" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 4259: 2014-09-06 13:42:56, Info                  CSI    00000324 [SR] Cannot repair member file [l:20{10}]"WUDFPf.sys" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 4262: 2014-09-06 13:42:56, Info                  CSI    00000326 [SR] Cannot repair member file [l:80{40}]"MsftWdf_User_01_11_00_Inbox_Critical.Wdf" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 4267: 2014-09-06 13:42:56, Info                  CSI    00000329 [SR] Cannot verify component files for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 4272: 2014-09-06 13:42:56, Info                  CSI    0000032c [SR] Recovered manifest from backup for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

I don't know why the last one failed to 'take' - the hash values are different to the version I uploaded.

I'll post another fix later.

I've uploaded a file - sh2ad.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\sh2ad
hit the enter key - if you get a 'Not Found' error try
DIR D:\sh2ad
or
DIR E:\sh2ad



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\sh2ad <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply