WINDOWS UPDATE ERROR CODE 8007371B - CANNOT UPDATE WINDOWS 7.

Question

Hello,

For the past few weeks I have not been able to update Windows and I keep getting the same Error Code ; 0x8007371B. The updates will download but the installation process seems to be blocked. I have run an SFC/Scan which was clear and have also run virus/malware checks which were also clear. I have downloaded and installed the SURT which installed KB947821 but the problem with installing updates persists.

I have also tried renaming the Software Distribution Folder via CMD but get the message 'Access is denied'. I have three CAB folders on my system - CAB, CAB2 and CAB.old. I suspect there may be a corrupted file somewhere but I really don't know what to do to keep my system up to date. My computer is working fine otherwise so I would rather not have to undertake a clean Windows installation. If anyone could offer some suggestions as to how to fix this then I would be SO grateful.

Thanks in advance for any assistance. I am attaching my zipped CBS folder following the SURT scan.  My system is running Windows 7 SP1 x64.

Thanks again,

Euan

PS ; I've just realised that I can't attach a file so I'm going to paste the results of the scan below. Sorry but it's quite a long list and it would appear that I have some missing files but it wouldn't let me paste all the info as the file was too long. 

=================================

Checking System Update Readiness.

Binary Version 6.1.7601.22471

Package Version 26.0

2018-06-07 17:52

Summary:

Seconds executed: 18548

 Found 690 errors

 Fixed 5 errors

  CBS MUM Missing Total count: 690

  Fixed: CBS MUM Missing.  Total count: 5

  Fixed: CBS Paired File.  Total count: 5

Answer 1

Even more confusing is I can find no trace of KB3210131 or KB4014565 in the Microsoft Update Catalog so am unable to download them for the files to be fixed. The other packages have been downloaded and added to the temp directory but for some reason the SURT  doesn't extract the necessary files from the relevant msu's. 

Whenever I try to install updates I now get three error codes ;

Code 2

80073701

8007371B

Adding to the confusion is that KB2952664 which Windows Update shows as being an important update, and continues to download and fail to install, is already installed on my system. When I try to install KB2978120 and KB3122648 manually it tells me that this update is "not applicable to my computer" - so why is Windows Update showing it an an important update?

I have tried everything including renaming the Software Distribution folder but nothing seems to work.

Any suggestions would be welcome.

Many Thanks,

Euan

Answer 2

Hi Jay Jap,

Thanks for your reply. I have run the SURT which found over 6oo missing files. I then downloaded the various updates for which the files were missing and ran the SURT again. It found and fixed the majority of the missing files but there are 31 missing files that for some reason it cannot fix even when the updates are available. Here is the current list ;

Summary:

Seconds executed: 6059

 Found 31 errors

  CBS MUM Missing Total count: 31

Unavailable repair files:

    servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.11.mum

    servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.2.mum

    servicing\packages\Package_1_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_1_for_KB3122648~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_1_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_1_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum

    servicing\packages\Package_2_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_2_for_KB3122648~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_2_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_2_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum

    servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.11.mum

    servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.2.mum

    servicing\packages\Package_3_for_KB3122648~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_3_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_3_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum

    servicing\packages\Package_4_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_4_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_4_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum

    servicing\packages\Package_5_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum

    servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.23.11.mum

    servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.23.2.mum

    servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.11.mum

    servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.2.mum

    servicing\packages\Package_for_KB2978120_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_for_KB3122648_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_for_KB3122648~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_for_KB3210131_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.mum

    servicing\packages\Package_for_KB4014565_SP1~31bf3856ad364e35~amd64~~6.1.1.2.mum

    servicing\packages\Package_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.mum

    servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.11.cat

    servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.2.cat

    servicing\packages\Package_1_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_1_for_KB3122648~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_1_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_1_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat

    servicing\packages\Package_2_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_2_for_KB3122648~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_2_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_2_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat

    servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.11.cat

    servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.2.cat

    servicing\packages\Package_3_for_KB3122648~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_3_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_3_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat

    servicing\packages\Package_4_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_4_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_4_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat

    servicing\packages\Package_5_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat

    servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.23.11.cat

    servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.23.2.cat

    servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.11.cat

    servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.23.2.cat

    servicing\packages\Package_for_KB2978120_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_for_KB2978120~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_for_KB3122648_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_for_KB3122648~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_for_KB3210131_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_for_KB3210131~31bf3856ad364e35~amd64~~6.1.1.0.cat

    servicing\packages\Package_for_KB4014565_SP1~31bf3856ad364e35~amd64~~6.1.1.2.cat

    servicing\packages\Package_for_KB4014565~31bf3856ad364e35~amd64~~6.1.1.2.cat

To be continued...

Answer 3

Thank you for the information. Since the issue still persists even after using the System Update Readiness Tool (SURT), our best options is to fix the error manually. You can refer to this link and look for How to fix errors that are found in the CheckSUR.log.

Keep us updated.

Answer 4

Hello Jay Jap,

Thanks for your reply. I have tried installing updates manually but the problem I'm having is that something seems to be preventing all or any Windows Updates from installing so they fail to install even as stand alone installations. I also downloaded each of the updates where there were missing MUM files and copied them over to a temp directory (%WinDir%TempCheckSUR) and copied the mus files into a packages folder within the directory. I then ran the SURT again. My understanding is that the tool would extract the missing files whilst running and that is what appeared to happen but ultimately that didn't work either and the CBS log just detailed the missing repair files again.

I have run the Windows Update Troubleshooter and get the same error (Windows Update Error 0x80070057) which I think is something to do with resetting the Windows Update data store or perhaps renaming the Software Distribution Folder which I haven't tried yet as I'm not too sure as to how go about it.

Any help you can give would be much appreciated.

Many Thanks,

Euan

Answer 5

Hello EuanMurray,

Based on the information that you have provided, it seems that you have done most of the steps needed to isolate the issue. Since the System Update Readiness Tool did not work, I suggest that you download and the Windows update troubleshooter. Once done, disable your antivirus before running another update.

The other option is to download and install the update manually. All you have to do is to take note the specific KB number that you are trying to install. Here's how:

1. Press the Start button on your keyboard, and click-on Control Panel.
2. Go to System and Security.
3. Click the Windows Update option.
4. Click View update history.

Once you have the KB number, visit the Microsoft Update Catalog website, and search of the said KB number that you wish to download and install.

Let us know how it goes.

Regards.