Update failure: 0x80073701 Windows Server 2016 Standard

F

FraLue

Member
Joined
Dec 2, 2019
Posts
8
Hallo,

I have a problem with a server updating since may this year. I've tried several times to install the windows updates and it allways fails with error 0x80073701. I've tried to clean the software distribution folder, download the update from the catalog, sfc, dism, nothing worked.
So finally I found this forum and maybe someone here, can help me.

The server is a virtual machine with windows server 2016 standard and exchange 2016 standard, so I really don't want to reinstall it. The hosts and other virtual machines have no problems to install the windows updates.

I've followed the instructions from the post Windows Update Forum Posting Instructions step by step and still got the error.


I uploaded the CBS logs and the SFCFix.txt to CBS.zip and 1 more file.

Maybe someone can find the issue.

Many thanks.
 
Hello and welcome!

Please do the following:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system 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.
i3yiUac.png


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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
Hi and thanks for your fast reply!

The new Logs can be found at CBS.zip and 1 more file

The preparation process for the update go up to 10%, stay there for 20 minutes, jumps up to 100% and failed with the error.
 
Thank you.

Do you happen to have another Server we could use to source some registry keys?

If you do, please do the following on that Server:

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. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
Hi!

Sadly, the hive does not contain the key in question. The issue here is that the system is looking for a key which appears to be a part of a superseded update that is no longer available. Please do the following on the broken Server:

Step#1 - Export CBS 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 Dropbox or OneDrive or SendSpace and just provide the link here.
 
Hi!

Thank you.

I've searched the hives and have been unable to locate the missing key:

The key in question is:

HKLM\COMPONENTS\DerivedData\Components\amd64_919b274a24a3b3fefb0bcc63f5238f09_31bf3856ad364e35_10.0.14393.1914_none_e19112f79dcea53c

If you happen to locate it, export it.

Do bear in mind that the COMPONENTS hive is not loaded by default, you have to load it manually from cmd by using the reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS command.
 
Hey!
I know it took a bit long, but I've found the key on another server.
 

Attachments

HI!


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 the attached fixlist.txt 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.
 

Attachments

You must log in or register to reply here.

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

Back
Top