Windows 7 Professional 64bit Update Error Code 8007370B

[Spewdog989]

Okay haha, Here's the goods:

CBS (2).zip | SockShare

 

[NoelDP]

Here's the relevant lines from the SFC scan....

 Line 76481: 2013-07-27 08:10:21, Info                  CSI    00000411 [SR] Repairing 6 components
 Line 76482: 2013-07-27 08:10:21, Info                  CSI    00000412 [SR] Beginning Verify and Repair transaction
 Line 76487: 2013-07-27 08:10:21, Info                  CSI    00000415 [SR] Cannot verify component files for Microsoft-Windows-Sysprep-Instrumentation, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 76492: 2013-07-27 08:10:21, Info                  CSI    00000418 [SR] Cannot verify component files for Microsoft-Windows-TextServicesFramework-CHxReadingStringIME, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 76497: 2013-07-27 08:10:21, Info                  CSI    0000041b [SR] Cannot verify component files for NetFx-ASPNET_WEBADMIN_USERS, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 76502: 2013-07-27 08:10:21, Info                  CSI    0000041e [SR] Cannot verify component files for Microsoft-Windows-International-Keyboard-0001041f, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 76503: 2013-07-27 08:10:21, Info                  CSI    0000041f [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:32{16}]"PeerDist.dll.mui" from store
 Line 76504: 2013-07-27 08:10:21, Info                  CSI    00000420 [SR] Repairing corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:38{19}]"PeerDistSvc.dll.mui" from store
 Line 76505: 2013-07-27 08:10:21, Info                  CSI    00000421 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"PeerDist.dll" from store
 Line 76506: 2013-07-27 08:10:21, Info                  CSI    00000422 [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:42{21}]"PeerDistHttpTrans.dll" from store
 Line 76519: 2013-07-27 08:10:22, Info                  CSI    00000424 [SR] Repair complete

As you can see, it's fixed the ordinary file mismatches - and confirmed the problem with the manifest files.

The files themselves are in the proper place for replacing, and as far as I can tell the Hash values in the registry are fine.

maybe we should try simply replacing the manifest files the same way as the others?

 

[Spewdog989]

Whatever you think is best. I am in way over my head already!

 

[NoelDP]

Hehe

OK - here we go....

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:\sd9ab
hit the enter key - if you get a 'Not Found' error try
DIR D:\sd9ab
or
DIR E:\sd9ab

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

XCOPY <drive>:\windows\temp\CheckSUR\Winsxs\Manifests <drive>:\windows\Winsxs\Manifests /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 SkyDrive Public folder, and post a new link

 

[Spewdog989]

Same thing as last time?

 

[Spewdog989]

Oh i see the difference, nevermind, sorry! I'll be back in a few minutes

 

[Spewdog989]

CBS4.zip | SockShare

 

[NoelDP]

At last - found the problem with the hashes!

I'll post what I hope will be an easy fix for them a little later.

 

[Spewdog989]

Awesome! look forward to it!

 

[NoelDP]

I've uploaded a file - hashfix.zip - to my SkyDrive at https://skydrive.live.com/?cid=936736bb8fceb92f#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21796
Please download and save it to your desktop.
Right-click on the saved file and select Extract all...
Save it to the default location
This should create a file hashfix.reg

right-click on the file, and select Merge
Accept the warnings, - you should then get a 'Success' message.
Close all windows, and reboot.

Then run another CheckSUR scan and we'll see if it's worked

 

[Spewdog989]

Tried, and got this error:

 

[NoelDP]

OK - try this....
Open an Elevated Command Prompt, and run the following command

REG LOAD HKLM\COMPONENTS C:\Windows\system32\config\COMPONENTS


then try the right-click/merge of the file.

 

[Spewdog989]

K that worked! Here's the cbs files again.

CBS5.zip | SockShare

 

[NoelDP]

Great! I can see the wood through the trees, now

Here's the only remaining errors...

Checking Package Watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385 Package registry presence failed, possibly an orphaned package on package watchlist
 
 
Checking Component Store
(f) CSI C Mark Deployment Missing 0x00000000 c!windoRsfoundaPion_31bf3856ad364e35_6.1.7600.16385_5f2ecc1aaa4ac3b2 x86_microsoft-windows-wdc-events_31bf3856ad364e35_6.1.7600.16385_none_d3d56c8ea90213c5 
(f) CSI C Mark Deployment Missing 0x00000000 c!ef3fce3e3ed..ceaf8a4e0cc_31bf2856ad364e35_6.1.7600.20524_5e1c12fbd0af6655 amd64_ef3fce3e3ed0eb6a2dbe0ceaf8a4e5cc_31bf3856ad364e35_6.1.7600.20524_none_5e1c12fbd0af6655 
(f) CSI C Mark Deployment Missing 0x00000000 c!ef3fca3e3ed..geaf8a4e5cc_31bf3856ad364e35_6.1.7600.20524_5e1c12fbd0af6655 amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7600.20524_none_d9715c699529a5b3

I'm trying to find them all in the existing COMPONENTS file you sent so I can work out how to fix them...
but a couple don't appear to exist

I'm going to need a new copy of the COMPONENTS file, please.

 

[Spewdog989]

Nice! here we go:

 

[NoelDP]

This should have cured the three Component Store errors.


I've uploaded a file - SD9components3.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
delete the old COMPONENTS.OLD file, and rename the current COMPONENTS file to COMPONENTS.OLD
Right-click on the saved file and select Extract all...
accept the default location, then copy the created COMPONENTS file to the C:\Windows\System32\Config folder

reboot, and run another CheckSUR - post the results.

 

[NoelDP]

For the last error, I need a little more information.

Please run the following command, and post the results.....

REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf3856ad364e35~amd64~~0.0.0.0"

(It should all be on one line, but will wrap)

Here are some instructions to make life easier
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

 

[Spewdog989]

Here's the checksur logs

 

[Spewdog989]

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

C:\Windows\system32>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Co
mponent Based Servicing\PackageDetect\Microsoft-Windows-TerminalServices-RemoteA
pplications-Client-Package~31bf3856ad364e35~amd64~~0.0.0.0"

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\PackageDetect\Microsoft-Windows-TerminalServices-RemoteApplications-Clien
t-Package~31bf3856ad364e35~amd64~~0.0.0.0
Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf385
6ad364e35~amd64~en-US~6.1.7600.16385 REG_DWORD 0x2


C:\Windows\system32>

 

[NoelDP]

Just the one error remaining now

Checking Package Watchlist
(f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385 Package registry presence failed, possibly an orphaned package on package watchlist

That registry data looks OK to me -

Please run this command and post the results...

REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TerminalServices-RemoteApplications-Client-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385" /S