Errors with Server 2019 2020-10 Cumulative Update for Windows Server 2019 (1809)

Question

Hi

Getting error code 80073712 when trying to install the latest update

Gone through all the Microsoft troubleshooting tools and I am still not getting anywhere

Anyone else had this issue?

Thanks

Answer 1

Hi @Stephen Allen

As error code 80073712 means The component store has been corrupted. So the direct suggestion is to repair component store with command line such as sfc or DISM. I noticed you have reply to DSPatrick about failure on repaire with them. We need to repair it with a specify source.

Try to refer to How to use DISM command tool to repair Windows 10 image, and check Fix problems with DISM using WIM image part.

We could get Windows 10 ISO image from the link below:
https://www.microsoft.com/en-us/software-download/windows10

By the way, I noticed you are using Windows 10 1809, we recommend to upgrade to the latest system version Windows 10 20H2 to experience the latest system and also upgrade will resolve such system issue.

Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

Bests,

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

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

0x80073712, means that a file needed by Windows Update is damaged or missing. I'd try the windows update troubleshooter, also;
sfc /scannow
dism /online /cleanup-image /restorehealth

--please don't forget to Accept as answer if the reply is helpful--

Answer 3

Try resetting manually.
https://learn.microsoft.com/en-us/windows/deployment/update/windows-update-resources#reset-windows-update-components-manually

You can also try a repair install by running setup.exe from the root of the install media.

--please don't forget to Accept as answer if the reply is helpful--

Answer 4

Hi,

No tried that it doesnt seem to want to do anything

Answer 5

You can also go down the rabbit hole of replacing suspect files mentioned in \cbs.log, \dism.log, \windowsupdate.log but time may be better spent standing up a new one, patch fully, migrate roles over and move on.

--please don't forget to Accept as answer if the reply is helpful--