Server 2022 Unable to install updates errors with 0x80073701

[Ascendingfog]

Good Afternoon,
DISM command ran successfully.

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.1487

[==========================100.0%==========================] The restore operation completed successfully.

 

[Maxstar]

Great, please attempt to update again. If it fails attach a new copy of the CBS logs.

 

[Ascendingfog]

It did fail again, Find the CBS logs attached.

 

[Maxstar]

Hi,

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

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

• 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.

 

[Ascendingfog]

Good Morning,
Here is the Fixlog.txt

 

[Maxstar]

Good morning too!

You have posted an older result of SFCFix instead of the result of FRST.

 

[Ascendingfog]

Sorry, I must not be awake yet. Lets try again. Please find the correct file attached.

 

[Maxstar]

Me either, because I made a typo in the commands...

Please run FRST again with the attached Fixlist...

 

[Ascendingfog]

Its a Monday morning, I think we can all be forgiven. Here is the next fixlog.

 

[Maxstar]

Here's the next fix.

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

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.

 

[Ascendingfog]

Here are the logs files from that.

 

[Maxstar]

This is the same bug I have seen on other Server 2022 systems, where a large number of RTM components (registry keys, manifest and payload files) were missing. So the quickest way to resolve this is to perform a repair install with ISO file of Windows Server 2022. Just let me know if this is an option to do?

 

[Ascendingfog]

I have the install media still so I can schedule the server for extended downtime to repair the install

 

[Maxstar]

Ok, perfect let me know the result..