Windows updates are failing

[shnabz2]

Hello,

I'm having trouble installing updates on a fresh install of Windows 7 Professional SP1 (x64). Could you please help me fix it?


Step1: System Update Readiness Tool (SURT)

When running the SURT, it asks me if I want to install the following Windows software update?
Hotfix for Windows (KB947821)

It successfully installs the hot-fix.

Step 2: SFC Scan

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>

Step 3: Windows Update Error Codes

KB2976627
Code 800B0100

Internet Explorer 11 for Windows 7 for x64-based Systems
Code 9C59

KB2706045
KB2511455
KB2908783
Code 8024200D

Step 4: Log Collection

The maximum file size for ZIP files is 8MB but my CBS.zip is 66.9MB

 

[NoelDP]

Delete the older CBSPersist logs until the zip file is below the limit - or upload the complete file to a fileshare service (preferably DropBox or OneDrive) and post a link.

 

[shnabz2]

Delete the older CBSPersist logs until the zip file is below the limit - or upload the complete file to a fileshare service (preferably DropBox or OneDrive) and post a link.

Here's the drop box link.

https://www.dropbox.com/s/x1bc2p6uw9cq1cu/CBS.zip

 

[NoelDP]

Here's the summary from a recent CheckSUR (the latest one didn't appear to have completed properly)

 Found 87 errors
  CSI Manifest All Zeros Total count: 67
  CBS MUM Corrupt Total count: 10
  CBS Catalog Corrupt Total count: 10

The SFC scan shows the following errors...

 Line 1708050: 2014-08-22 01:41:17, Info                  CSI    00000d3f [SR] Repairing 2 components
 Line 1708051: 2014-08-22 01:41:17, Info                  CSI    00000d40 [SR] Beginning Verify and Repair transaction
 Line 1708056: 2014-08-22 01:41:17, Info                  CSI    00000d43 [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 1708059: 2014-08-22 01:41:17, Info                  CSI    00000d45 [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 1708062: 2014-08-22 01:41:17, Info                  CSI    00000d47 [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

...and the background errors in the CBS.log are almost all related to the CheckSUR problems.

I'll deal with the CheckSUR results first - when I get time - but it's likely to be tomorrow now.

(here's the list of affected files, for the record, and my ease of finding them again!)

 

[NoelDP]

I've uploaded a file - sh2aa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder sh2aa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[shnabz2]

Thanks for the files, here is the new CheckSUR log.

 

[NoelDP]

I knew I'd missed one!

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.17803_en-us_251461586e43c0e3.manifest

I'll post a fix with that one in a few minutes.

 

[NoelDP]

I've uploaded a file - sh2ab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder sh2ab in the same place.
Open this folder - there should be one folder inside it (Manifests)

Copy the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

Also then run another SFC /SCANNOW and post the new CBS.log file (zipped)

 

[shnabz2]

Here are the logs
View attachment 330528
View attachment 330529

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>

The new CBS.log
https://www.dropbox.com/s/qpqisia94g3ls5j/CBS%2025-08-2014.zip?dl=0

 

[NoelDP]

The manifest replacement worked.
SFC found the following errors that it couldn't fix...

 Line 258544: 2014-08-25 15:05:50, Info                  CSI    000004d9 [SR] Repairing 2 components
 Line 258545: 2014-08-25 15:05:50, Info                  CSI    000004da [SR] Beginning Verify and Repair transaction
 Line 258548: 2014-08-25 15:05:50, Info                  CSI    000004dc [SR] Cannot repair member file [l:32{16}]"WUDFHost.exe.mui" of 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 in the store, hash mismatch
 Line 258551: 2014-08-25 15:05:50, Info                  CSI    000004de [SR] Cannot repair member file [l:40{20}]"wudfplatform.dll.mui" of 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 in the store, hash mismatch
 Line 258554: 2014-08-25 15:05:50, Info                  CSI    000004e0 [SR] Cannot repair member file [l:30{15}]"wudfsvc.dll.mui" of 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 in the store, hash mismatch
 Line 258557: 2014-08-25 15:05:50, Info                  CSI    000004e2 [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 258560: 2014-08-25 15:05:50, Info                  CSI    000004e4 [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 258563: 2014-08-25 15:05:50, Info                  CSI    000004e6 [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

I'll post a fix protocol for these tomorrow, hopefully!

 

[shnabz2]

Thanks!

Quick question, folders are appearing in my secondary drive that have a little padlock on them, for example "5853f982850e116461"
"dd5cdf752537cbe3d6c11cf8b44f"

Inside all three of the folders are the same two files;
checksur
checksurlauncher

Do you think whatever caused my windows update issue is related to this?

 

[NoelDP]

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.

 

[shnabz2]

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.

Should they be appearing in my secondary drive though?

 

[NoelDP]

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.

 

[shnabz2]

Any luck with the fix?

 

[NoelDP]

OMG! Sorry!
back later with the promised fix.

 

[NoelDP]

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

 

[shnabz2]

I don't seem to have a "repair my computer" option. I booted into a linux distro and copied the folder into the winsxs directory. Then booted back into windows and ran sfc.

Here is the log;

 

[NoelDP]

Hmmm-

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.

 

[NoelDP]

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