Server 2016 - Windows Update Error Code 0x8007371

leoleo · Dec 13, 2019

Hi,
I have three identical servers in a failover cluster configuration with Windows server 2016.
One of them no longer updates by returning the error 0x80073712
I have tried both SFC, DISM, Troubleshooter and Sconfig but both fail

Do you have any suggestions for me?

CBS folder attached.
Thanks in advance

Leo

Sysnative Windows Update · Dec 13, 2019

Hello and welcome!

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.

leoleo · Dec 13, 2019

Hi,
Thanks for the reply.

Fixlog.txt attached

Sysnative Windows Update · Dec 13, 2019

Thank you. Please retry the update and attach CBS.log if it fails.

leoleo · Dec 13, 2019

I rebooted the server and tried again but unfortunately the update fails

Sysnative Windows Update · Dec 13, 2019

Yes, we need to dig deeper:

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.

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.

leoleo · Dec 13, 2019

here are the files
Download multiple files from Sendspace.com - send big files the easy way

Sysnative Windows Update · Dec 13, 2019

Thank you.

You mentioned that you have additional Servers. May I get a copy of the COMPONENTS hive from one of them, so I can try and source the missing registry information?

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.

leoleo · Dec 13, 2019

thank you for your concern.
Here is the COMPONENTS file of another server in the cluster
COMPONENTS.zip (33.28MB) - SendSpace.com

Sysnative Windows Update · Dec 13, 2019

Excellent!

I managed to find the key.

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.

leoleo · Dec 13, 2019

there he is

Sysnative Windows Update · Dec 13, 2019

Oops, the fix was unsuccessful due to my error in the script. Nothing was imported.

Please use this fixlist.

leoleo · Dec 13, 2019

here is the new log

Sysnative Windows Update · Dec 13, 2019

That was successful. Please retry updates and attach CBS.log if any fail. No need for ProcMon for now.

leoleo · Dec 13, 2019

Here are the 5 a.m.
I launch the update (which lasts a long time) and go to sleep.
I'll give you news in a few hours
Thanks for everything !

Sysnative Windows Update · Dec 13, 2019

No problem.

Have a good night!

leoleo · Dec 14, 2019

update fails
CBS.log attached

Sysnative Windows Update · Dec 14, 2019

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.

leoleo · Dec 14, 2019

there he is

Sysnative Windows Update · Dec 14, 2019

Thanks. Retry updates and attach CBS.log if any fail.

Server 2016 - Windows Update Error Code 0x8007371

Contributor

Attachments

Inactive

Attachments

Contributor

Attachments

Inactive

Contributor

Attachments

Inactive

Contributor

Inactive

Contributor

Inactive

Attachments

Contributor

Attachments

Inactive

Attachments

Contributor

Attachments

Inactive

Contributor

Inactive

Contributor

Attachments

Inactive

Attachments

Contributor

Attachments

Inactive