Small Business Server 2011 Windows Update Error 80073701

del08202020

Well-known member
Joined
Oct 1, 2018
Posts
80
Hi Guys,

I came to your forum via Google and hope, maybe I can get some help.
I am using a Windows Small Business 2011 Server.
Last updated about 3-4 month ago.

Today I tried to install the newest Windows Updates but got stuck in an error, that the Component Store is corrupted.
Neither sfc /scannow nor System Update Readiness Tool were working.

I checked a few files and saw, that the COMPONENT file only has 256kb and the system was unable to read the file.
Unfortunately the only backup with a "working" COMPONENT file is dated back to 2016.
But I restored the file with a partial success:

System Update Readiness Tool (checksur log) and sfc /scannow are telling me there is no problem with the system.
I also tried SFCFix and also got the message there is no problem with the system.

But Windows Update fails with the code 80073701 and the CBS.log is getting bigger and bigger.
So, there is the situation I am not able to help myself, because I have no clue what I can do.

My components file is uploaded to Onedrive:
https://1drv.ms/u/s!Al7wGM9mw0ZBkI8k4sQRZurI5ICn_g

Thank you in advance! :wave:
 
Just an information:

I tried again to install updates.

Some updates were successful. (1 .net Update and Windows malicious software removal tool)
Some had Error 80073701 (Normal Windows Updates)
Some had Error 80073712 (Monthly Rollup)

And the TrustedInstaller Service takes 100% CPU
 
KB4072650 - Update for Windows Server 2008 R2 x64 Edition (Error 80073701)
KB4457918 - 2018-09 Rollup for .NET Framework (Error 80073712)
KB4458611 - 2018-09 Rollup Preview for .NET Framework (Error 80073712)
KB4343205 - Cumulative Update for Internet Explorer 11 (Error 80073712)
KB4457139 - 2018-09 Rollup Preview for Windows Server 2008 R2 (Error 80073712)
KB4457144 - 2018-09 Rollup for Windows Server 2008 R2 (Error 80073712)
 
What do you mean exactly?
Just disabling the running services or moving the OS to a real machine.
Currently it is a VM in a HyperV Host
 
Aha, I see. Let's try something else then:

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.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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
 
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.
 
I would prefer an updated one, but I have created a fix based on the old one which should be no different, so let's see.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top