Windows 7 Pro 64-bit update error code 8007370B

[NoelDP]

Hmmm - please run both SFC and CheckSUR, and post the logs together with the C:\windows\windowsupdate.log file ( I really wasn'texpecting any positive results at this stage!)

 

[n2jlc]

Here are the CBS and Windows Update logs all in one folder.

 

[NoelDP]

We have progress
CheckSUR ran OK, and fixed a few of the payload file errors - There's still a C Mark error outstanding...

(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5df488a7d948b37d amd64_microsoft-windows-a..orecodecs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_a0117050dc6b1274

I'll try and sort that one out today.

SFC found the following errors (and finished successfully)

 Line 4375: 2014-11-09 15:04:37, Info                  CSI    00000348 [SR] Repairing 5 components
 Line 4376: 2014-11-09 15:04:37, Info                  CSI    00000349 [SR] Beginning Verify and Repair transaction
 Line 4381: 2014-11-09 15:04:37, Info                  CSI    0000034c [SR] Cannot verify component files for Microsoft-Windows-ALG.Resources, Version = 6.1.7600.16385, 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 4384: 2014-11-09 15:04:37, Info                  CSI    0000034e [SR] Cannot repair member file [l:16{8}]"apps.inf" of Microsoft-Windows-shell32, Version = 6.1.7601.18517, 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 4387: 2014-11-09 15:04:37, Info                  CSI    00000350 [SR] Cannot repair member file [l:20{10}]"WsmRes.dll" of Microsoft-Windows-Web-Services-for-Management-Core, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 4392: 2014-11-09 15:04:37, Info                  CSI    00000353 [SR] Cannot verify component files for Microsoft-Windows-Security-Credential-Manager-Command-Line-User-Interface.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), 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 4395: 2014-11-09 15:04:37, Info                  CSI    00000355 [SR] Cannot repair member file [l:32{16}]"AuthFWSnapin.dll" of Networking-MPSSVC-Admin, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll put up a fix protocol for that later.

 

[n2jlc]

YEA! I'm off to work. Will check as soon as I return this evening before I go off to study. I re-certify my CCNA on Thursday. Thanks again.

 

[NoelDP]

Found a couple more bitflips that we need to address before we start replacing files...


I've uploaded a file - n2caf.zip - to my OneDrive at Noel's OneDrive

Please download and save it to your desktop.

Right-click on the file and select Extract All, andsave to the default destination (which should be a folder on the desktop)



Create a new System Restore point



Open an Elevated Command Prompt, and run the followingcommands.

IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1
REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
COPY "%userprofile%\desktop\n2caf\COMPONENTS" C:\Windows\System32\config
  
.

If you get an error with either command, STOP THERE -do not reboot! - post for instructions.



Assuming both commands go OK, reboot, and run anotherCheckSUR scan - post the new CheckSUR.log file.

 

[n2jlc]

Alright, here are today's CBS logs.

 

[NoelDP]

Checking Component Store
(f) CSI Payload File Missing 0x00000000 mscorlib.dll amd64_mscorlib_b77a5c561934e089_6.1.7601.18299_none_546d3d32697be903 
(w) CSI S256H Incorrect 0x00000000 S256H amd64_microsoft-windows-alg.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b09e0ee225f9b48e Invalid Length: 31
(w) CSI S256H Incorrect 0x00000000 S256H x86_microsoft-windows-s..interface.resources_31bf3856ad364e35_6.1.7600.16385_en-us_66462316273e5577 Invalid Length: 31
(f) CSI Payload File Missing 0x00000000 webengine.dll x86_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7601.22515_none_f42de1c60e368b6c 
(f) CSI Missing C Mark 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7601.17514_60259c6fd6373717 amd64_microsoft-windows-a..orecodecs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_a0117050dc6b1274 Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7601.17514_60259c6fd6373717 successfully added to amd64_microsoft-windows-a..orecodecs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_a0117050dc6b1274
(f) CSI C Mark Deployment Missing 0x00000000 c!microsoft-w..anguagepack_31bf3856ad364e35_6.1.7600.16385_5df488a7d948b37d amd64_microsoft-windows-a..orecodecs.resources_31bf3856ad364e35_6.1.7600.16385_en-us_a0117050dc6b1274

... Now that's interesting!
The two SHA256 errors found here are actually ones that I repaired in yesterday's upload - I'll have to think about what this implies.

I'll post again after work.

 

[n2jlc]

OK on the why the 2 SHA256 errors didn't stay fixed. Also, for your information, when I shut down the PC last night, it did two updates: The .NET 3.5.1 (KB2937610) that it did not do on Sunday and some other kind of generic Win 7 update (KB2970228).

 

[NoelDP]

OK -it was my fault

I've uploaded a file - n2caf.zip - to my OneDrive at Noel's OneDrive

Please download and save it to your desktop.

Right-click on the file and select Extract All, andsave to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

IF EXIST C:\Windows\System32\config\COMPONENTS.OLD1 DEL C:\Windows\System32\config\COMPONENTS.OLD1 
REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1 
COPY "%userprofile%\desktop\n2caf\COMPONENTS" C:\Windows\System32\config 
  .

If you get an error with either command, STOP THERE -do not reboot! - post for instructions.

Assuming both commands go OK, reboot, and run anotherCheckSUR scan - post the new CheckSUR.log file.

 

[n2jlc]

OK here are the CBS logs from today.

 

[NoelDP]

The CheckSUR scan crashed again
I suspect that we're on a losing wicket here

I think that possibly your best way forward is a repair install - there could well be errors elsewhere in the registry that are giving false results and impeding things.

See the instructions here... http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R

 

[n2jlc]

Bummer. :-( OK I will do the repair install, but will not have the time until this weekend. I will do it then and then post the results.

Thanks so much for all of your help.

 

[NoelDP]

I hate doing things like that - especially with such a willing partner! - but I think it's the shortest route to a fully-repaired installation (assuming it works), because of the probability of errors elsewhere in the system.

Good luck with it!

 

[n2jlc]

Hello. I spent most of the day making sure everything was backed up (just in case). Found I could not do a Microsoft backup. It gave the same error as what I was getting with the updates. So I just had to do a copy/paste backup. I also found I could not get to the user folder under the account I was logged in with even though it was an administrator account. The error said i did not have permissions. (????)

So I tried the repair installation. It "blew up" when it went to step 2 and tried to gather information.

I created a second account with administrator privileges and found i could then access the user folders under documents and settings. So tried the installation upgrade and it failed again.

Does this mean we will have to do a clean install?

 

[NoelDP]

It certainly sounds like it to me
You have two options potentially:
1) use whatever Recovery software came with the machine
2) a clean install using MS media. - see the instructions here... http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html?ltr=C

 

[n2jlc]

Bummer. OK, I will probably wait until we are off for our Thanksgiving break next weekend to do that. But I will post the results. Thanks again for all of your help.

 

[NoelDP]

Good luck with it!