[SOLVED] Persistent Server 2016 update error 0x80073712

[Gargomel]

getting error 0x80073712 when trying to run windows update.


sfc /scannow fails to run

DISM Runs but windows update still returns the same error when attempting to run


ComponentScanner runs but doesn't find any corruption or ask for any repairs to be made.

 

[Maxstar]

Hi and welcome to Sysnative,

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• 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.
• 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.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[Gargomel]

Component hive attached, thanks for taking a look!

 

[Maxstar]

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[Gargomel]

FRST ran without any errors or warning. Log attached.

 

[Maxstar]

Great, reboot the server and attempt to update. If it fails attach a new copy of the CBS logs.

 

[Gargomel]

Rebooted and attempting to run windows update now and it was stuck @ downloading updates 0% so I deleted the software distribution folder and restarted the update and it's going but very slowly (10% after 20 plus minutes) but I'll leave it for now and follow up when finished. Thanks.

 

[Gargomel]

Everything is back to normal! thank you so much!

So all it needed was the component share loaded back into the registry?

 

[Maxstar]

Hi,

You're welcome. Glad to hear the issue has been resolved. In this case the StoreDirty value was set in the components hive and causing the issues.