What's new

Windows update error Code 8007370D

docpel

Active member
Joined
Nov 21, 2018
Messages
31
Greetings Humans,

I have been struggling with this error for a year now. I have tried many fixes all to no avail. Open to any suggestions.

Windows 7 professional 32 bit.

Dr. P
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Hello and welcome!

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service and just provide the link here.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

docpel

Active member
Joined
Nov 21, 2018
Messages
31
Code:
 SFCFix version 3.0.0.0 by niemiro.Start time: 2018-11-26 08:29:44.085
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\DrBob\Desktop\SFCFixScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36b758890f2cc03ad4c1f7b69ba4b785_31bf3856ad364e35_none_c80d6dcae40f2d50.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36f311adc393d329d510560302c348dd_b77a5c561934e089_none_ea25feb490e7f632\v!6.1.7601.22733.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36b758890f2cc03ad4c1f7b69ba4b785_31bf3856ad364e35_none_c80d6dcae40f2d50.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36b758890f2cc03ad4c1f7b69ba4b785_31bf3856ad364e35_none_c80d6dcae40f2d50\v!6.1.7601.18015.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36f311adc393d329d510560302c348dd_b77a5c561934e089_none_ea25feb490e7f632.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36f311adc393d329d510560302c348dd_b77a5c561934e089_none_ea25feb490e7f632\v!6.1.7601.22733.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36f311adc393d329d510560302c348dd_b77a5c561934e089_none_ea25feb490e7f632\v!6.1.7601.22733.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36b758890f2cc03ad4c1f7b69ba4b785_31bf3856ad364e35_none_c80d6dcae40f2d50.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36b758890f2cc03ad4c1f7b69ba4b785_31bf3856ad364e35_none_c80d6dcae40f2d50\v!6.1.7601.18015.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36b758890f2cc03ad4c1f7b69ba4b785_31bf3856ad364e35_none_c80d6dcae40f2d50.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36f311adc393d329d510560302c348dd_b77a5c561934e089_none_ea25feb490e7f632.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_36f311adc393d329d510560302c348dd_b77a5c561934e089_none_ea25feb490e7f632\v!6.1.7601.22733.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2018-11-26 08:29:44.705
Script hash: g14txE521a5M6mDOpw5c/ebYxFGzTy6lzcV2oU/H15E=
----------------------EOF-----------------------
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
Thank you! That helped. I just need another piece of info:

Step#1 - Export registry as hive



  • Click on the Start button and in the search box, type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to SendSpace and just provide the link here.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
I see you have removed the ProcMon.log I need it for my analysis.
 

softwaremaniac

Moderator, BSOD Kernel Dump Expert, Windows Update Instructor
Staff member
Joined
Oct 9, 2014
Messages
18,437
Location
Croatia
FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 32-bit Version so please ensure you download that one.
6. Run FRST by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste
6.1.7601.22705;6.1.7601.22733;11.2.9600.17728;6.1.7601.21955;6.1.7601.21890 into the Search box and click the Search Registry button.
8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
9. You may close any remaining open windows now.
 
Top