Windows 7 doesn't update with Error Code 8007370B

gruenkohl · 10 Feb 2015

Hi,

2 weeks ago my dad reported me a Windows Update problem showing Code 8007370B. He is using Windows 7 Home Professional 32 bit system with SP1. He used the CheckSUR-Software producing the 2 file "checkSUR.log" & "CheckSUR.persist.log" with are attached.
Now I am visiting my parents and of course want to fix this problem.
I started "Sfc /scannow" which produced CBS.log, which I attached in zipped form.
From the checkSUR.log I see that "Package_for_KB2973112~31bf3856ad364e35~x86~~6.1.1.0.cat" is missing. Somewhere I read I have to find that file and put it into "%windir%\Temp\CheckSUR\servicing\packages", right? But I didn't succeed finding the missing file.

Can anyone help?

gk

Legaede · 10 Feb 2015

Hello there,

Please try running the steps below and let me know if you continue to receive the error message while installing Windows Update.

Step 1: Reset the Windows Update Components

Press click the start menu, type cmd, then right-click cmd and select run as administrator. Once command prompt has opened, type each of the below one by one and press enter:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Step 2: Run the Windows Update Troubleshooter

The Windows Update Troubleshooter will check your system for any missing or corrupt files which are required to be able to install updates. As well as that, it will check to make sure the necessary services needed to use Windows Update are started.

Click here to run the Windows Update Troubleshooter.

Thanks,
Legaede

gruenkohl · 10 Feb 2015

Hi Legaede,

thanks for your reply.
I put the commands to the cmd environment as you mentioned in step1.
One problem was to mention: The renaming of catroot2 did not work even as admin. Thus, this point in step 1 I was not able to follow.
Step 2: The troubleshooter did not succeed to fix the update error 8007370B.

Any further idea?

Legaede · 11 Feb 2015

Hi :)

Could you please try running the System Update Readiness Tool

NoelDP · 11 Feb 2015

You have a couple of very different problems - I think we'll start with the more complex one...

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.

NoelDP · 11 Feb 2015

Legaede said:

Hi :)

Could you please try running the System Update Readiness Tool

The OP has already done that - and posted the logs.

gruenkohl · 11 Feb 2015

Hi Legaede,
I run the SUR tool again. It produced the attached new CheckSUR.log and CheckSUR.persist.log files. Looks pretty similar to the old ones, I think.

Hi Noel,
the COMPONENTS in zipped form was small enough to be attached here, too.

NoelDP · 11 Feb 2015

The major problem is bitflips in the registry - which could indicate failing hardware (usually RAM)
You should test the system using MemTest6+ - follow this tutorial.... RAM - Test with Memtest86+

I'll post regarding the COMPONENTS hive later, when I get a chance to investigate it in detail.

gruenkohl · 12 Feb 2015

Hi Noel,

the mainboad of the computer has 4 slots. The 1st ones of them were filled with equal memory sticks (both 2 GB). The memtest86 revealed problems with one of them. I pulled the problematic memory stick out of the slot and run the memtest86 with the other one through the night. The test revealed no errors within 13 runs. For 1st I left the problematic mem stick out of the computer. Next night I plan to put it into a different memory slot and run the memtest86 again.
BTW: Some of the system crashs and system resets in the last time had their cause in a damaged graphics boad, which I exchanged 2 days ago. So this problem should be out of the world.

NoelDP · 12 Feb 2015

Good - at least we've isolated one or two causes now.

I think I've fixed most of the problems with your COMPOENTS hive....

I've uploaded a file - gklaa.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.

Code:

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\gklaa\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.