Solved Cannot Update Windows 7 x64 SP1 - Error 0x8007370B

[Borkum]

For quite some timenow, I have been unable to successfully run windows updates on my computer. Iam running Windows 7Home 64bit SP1. Running the update troubleshooter yieldsthe error code 0x8007370B. I have searched the Internet, ran the MS Update Fix Ittool, gone thru the Windows Trouble Shooter, booted into Safe mode, and ranDisk Cleanup, but none have made a difference.



In an effort tocollect the information needed for a submission to this forum, I did thefollowing:



Downloaded and ranSURT. It ran for a little over 8 hours and then returned the following message:



Do you want toinstall the following Windows Software Update?



Hotfix for WindowsKB947821.



I did, and it tookabout 20 min. I then decided to reboot before running SFC and when I did, ittook almost 1 hour to restart (I don't know if it actually went BSOD.) Windowsrestarted with the warning:



Windows hasrecovered from an unexpected shutdown



The following werethe problem details:



Problem signature:

Problem EventName: BlueScreen

OSVersion: 6.1.7601.2.1.0.768.3

LocaleID: 1033



Additional information about the problem:

BCCode: 9f

BCP1: 0000000000000003

BCP2: FFFFFA800B76CA00

BCP3: FFFFF80000B9A4D8

BCP4: FFFFFA8012AE0A60

OSVersion: 6_1_7601

ServicePack: 1_0

Product: 768_1



Files that help describe the problem:

C:\Windows\Minidump\092615-22417-01.dmp

C:\Users\Dan\AppData\Local\Temp\WER-124941-0.sysdata.xml



The xml file doesnot exist. The minidump file is included in the submission.



I then ran SFC andit immediately terminated with an error:



Windows Resource Protection could not perform therequested operation.



I don't receive anyerrors from Windows Update, since it just sits there and spins. I did get thefollowing messages after running the "Update Troubleshooter":



Windows Update Error0x8007370B(2015-09-26-T-11_07_06A) - Not fixed

Service registration is missing or corrupt - Fixed

Problem installing recent updates - Fixed

The CBS.log and Minidump files are attached.
View attachment 372438

Any and all help is welcome. Thank you!

 

[NoelDP]

Here's the errors from your CheckSUR log...

Checking Component Store
(f)	CSI Payload File Missing	0x00000000	dao360.dll	x86_microsoft-windows-m..s-components-jetdao_31bf3856ad364e35_6.1.7600.16385_none_7b8c1dc4ef873d90	
(f)	CSI Corrupt Identity	0xC000000D	Microsoft-Windows-K%rnelBase, Culture=neutral, Version=6.1.7601.17932, PublicKeyToken=31bf3856ad364e35, Pro#essorArchitecture=wow64, versio&Scope=NonSxS	wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.17932_noneG8f658f40ffa656a6	Bad identity
(f)	CSI Manifest Missing	0x00000002	wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.17932_noneG8f658f40ffa656a6.manifest	wow64_microsoft-windows-kernelbase_31bf3856ad364e35_6.1.7601.17932_noneG8f658f40ffa656a6

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

 

[Borkum]

NoelDP,

I don't have a components file in that location. I do have a 2 year old version in my Registry backup folder which is here: https://www.dropbox.com/s/99d6rexzhevkk8r/components.zip?dl=0 .

I don't know why, but maybe that can help.

 

[NoelDP]

The file certainly should be there - if not, you have a MAJOR problem, and CheckSUR is also lying

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

DIR C:\Windows\System32\config\COMPONENTS*.*
DIR C:\Windows\System32\config\COMPONENTS /ah


Post the results

 

[Borkum]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>DIR C:\Windows\System32\config\COMPONENTS*.*
Volume in drive C is Win7Boot
Volume Serial Number is 8E02-6C40
Directory of C:\Windows\System32\config
09/27/2015 11:32 AM 46,399,488 components
1 File(s) 46,399,488 bytes
0 Dir(s) 71,460,642,816 bytes free
C:\Windows\system32>DIR C:\Windows\System32\config\COMPONENTS /ah
Volume in drive C is Win7Boot
Volume Serial Number is 8E02-6C40
Directory of C:\Windows\System32\config
File Not Found
C:\Windows\system32>

 

[NoelDP]

Ah - so there is a COMPONENTS file

09/27/2015 11:32 AM 46,399,488 components

please compress it and upload the compressed file to a fileshare site - post a link.

 

[Borkum]

Don't know why I couldn't find it but here it is: https://www.dropbox.com/s/99d6rexzhevkk8r/components.zip?dl=0
Sorry about that.

 

[Borkum]

NoelDP, did you get the components file?

 

[NoelDP]

I did - I'm just having problems finding the time to work on it

back when I can!

 

[Borkum]

Thanks, No problem.

 

[Borkum]

NoelDP, any idea when you might be able to get back to this? If not could you turn it over to another admin?

 

[NoelDP]

OMG _ it dropped off my ToDo list!
I'll try and get back to it this evening.

 

[NoelDP]

I've uploaded a file - brkaa.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, and save 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\brkaa\COMPONENTS" C:\Windows\System32\config
 
.

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

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

 

[Borkum]

NoelDP, It ran fine. Here is the link to the files: https://www.dropbox.com/s/0n4mbppoppqsdsh/CBS-10-20-2015.zip?dl=0

 

[NoelDP]

great - the only error that CheckSUR found this time was the expected...

Checking Component Store
(f)	CSI Payload File Missing	0x00000000	dao360.dll	x86_microsoft-windows-m..s-components-jetdao_31bf3856ad364e35_6.1.7600.16385_none_7b8c1dc4ef873d90

Please run another SFC /SCANNOW and post the new CBS.log - that way I can fix any other missing files as well.

 

[Borkum]

NoelDP, here is the link to the CBS log files you requested SFC /scannow. Thanks again
https://www.dropbox.com/s/x553xa0ci8ge2op/CBS-10-21-2015.zip?dl=0

 

[NoelDP]

Here's the important bits from the SFC scan...

	Line 520718: 2015-10-21 19:15:42, Info                  CSI    0000058b [SR] Repairing 4 components
	Line 520719: 2015-10-21 19:15:42, Info                  CSI    0000058c [SR] Beginning Verify and Repair transaction
	Line 520724: 2015-10-21 19:15:42, Info                  CSI    0000058f [SR] Cannot verify component files for Microsoft-Windows-Font-TrueType-MongolianBaiti, 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 520727: 2015-10-21 19:15:42, Info                  CSI    00000591 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 520730: 2015-10-21 19:15:42, Info                  CSI    00000593 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 520735: 2015-10-21 19:15:42, Info                  CSI    00000596 [SR] Cannot verify component files for Microsoft.Windows.Hardware.Devices.ClassInstaller.MULTIPORTSERIAL-DriverClass, 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 520736: 2015-10-21 19:15:42, Info                  CSI    00000597 [SR] Cannot repair member file [l:20{10}]"dao360.dll" of Microsoft-Windows-Microsoft-Data-Access-Components-JetDAO, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
	Line 520741: 2015-10-21 19:15:42, Info                  CSI    0000059a [SR] Recovered manifest from backup for Microsoft-Windows-Font-TrueType-MongolianBaiti, 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

I'll post a fix protocol later for everything (hopefully!)

 

[Borkum]

NoelDP, any luck with finishing this up?

 

[NoelDP]

Sorry - not a good weekend

Anyhow - here we go...
I've uploaded a file - brkab.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:\brkab
hit the enter key - if you get a 'Not Found' error try
DIR D:\brkab
or
DIR E:\brkab

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

XCOPY <drive>:\brkab <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

 

[Borkum]

NoelDP, here is the log file: https://www.dropbox.com/s/yzt3h1bhjz9ts2t/CBS-10-28-2015.zip?dl=0
Thanks.