Windows Server 2019 - Installation of KB5015811 fails with 0x80073712

[LarryK]

Second WS2019 with this problem, which now prevents other (August) updates from being installed.

Atttached are the latest CBS and DISM logs.
Again, more than willing to contribute to get this solved.
Thanks, in advance, for your help - again.

Larry

 

[x BlueRobot]

Could you please provide all the available CBS logs?

 

[LarryK]

Here you go...

 

[x BlueRobot]

There doesn't appear to be anything useful in them at the moment, could you please run DISM again and then attach the latest CBS log?

 

[LarryK]

Here you go

 

[x BlueRobot]

Thanks, let's get a Process Monitor log to try and find out what is happening:

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 square icon 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 WeTransfer.

 

[LarryK]

My apologies for the long delay.
The NOC team from my RMM vendor implemented some changes and advised me after the fact, so I thought this situation was resolved.
With this month's update, I find it was not. Same error - different patch: Package KB5017315 failed to be changed to the Installed state. Status: 0x80073712.

My RMM installs the updates on a schedule and my client only allows the updates to take place on Saturday with a reboot on Sunday morning.
I'll have to see if ProcMon can be run via script. If so, I could start it just before the Saturday installation and see what happens.

Please let me know what my next steps should be.
Sorry again for the inadvertent pause.

 

[x BlueRobot]

For now, could you please provide the latest CBS log(s)? It does look like Process Monitor can be run from a script since it does support a number of command-line arguments.

 

[LarryK]

Here's the folder for your review.

 

[x BlueRobot]

Hmm, nothing is getting written to the CBS log, the best option is to run Process Monitor at the next available opportunity and then provide the log file.

 

[LarryK]

That looks like it will be this coming weekend.
I hope that I can manage to get this done correctly.

 

[x BlueRobot]

Okay, no problem