[SOLVED] Updates fail to install with error 0x80073701 on Windows 2016 Standard x64

[lg_spam]

I have a Windows 2016 Standard server that has component corruption, but I've gone as far as I can with repairing it.

Initially the CBS log stated it was missing files from a previous cumulative rollup, so I used the DISM repair command with the files from the CU as the source and it repaired; now there are no errors in the logs that I can make sense of but the updates are still failing to install with error 0x80073701; in the Event Viewer setup log 0x800f0816 is referenced but SFC, DISM, ComponentScanner and SFCFix are not reporting any errors.

The Windows update log is corrupt - running 'Get-WindowsUpdateLog' returns many lines all looking like the following:

1600/12/31 19:00:00.0000000 540 12188 Unknown( 11): GUID=638e22b1-a858-3f40-8a43-af2c2ff651a4 (No Format Information found).
1600/12/31 19:00:00.0000000 540 12188 Unknown( 50): GUID=6ffec797-f4d0-3bda-288a-dbf55dc91e0b (No Format Information found).
1600/12/31 19:00:00.0000000 540 12188 Unknown( 23): GUID=3887d6ef-c209-31dc-4931-1b8d628e7f0e (No Format Information found).

Copying the ETL files to a working Windows 2016 Server and running GetWindowsUpdateLog -ETLPath results in the same log being created, even though when checking it's own ETL files a readable log is created.

I've uploaded the Component Scanner, SFCFix, Update Logs and CBS files - would certainly appreciate any assistance in how to proceed!

Thanks!

 

[Maxstar]

Hi and welcome to Sysnative,

Follow these instructions to install an update with DISM.

• Open the Start menu of Windows and type CMD.
• When you see Command Prompt on the list, select the option Run as administrator.
• Copy and paste the following command into it, and press enter. (Leave the CMD window open!)

MD C:\WUTemp

• Now, download the following update (KB5039214) to: C:\WUTemp - Or copy this file from the download directory to C:\WUTemp. (Important!)
  Downloadlink: KB5039214

• Copy and paste the following commands one at a time into the command prompt and press enter after each.

CD C:\WUTemp
EXPAND.exe windows10.0-kb5039214-x64_fbf5714e1a5885bad5f5646372740238859de2f4.msu -f:* C:\WUTemp
DISM.exe /Online /Add-Package /PackagePath:C:\WUtemp\Windows10.0-KB5039214-x64.cab

• Let me know if it says it was successful or if there are any errors. Or take a screenshot of the command prompt window and paste it into your next reply.

 

[lg_spam]

This worked perfectly on a VM I restored from backup - no errors, and I was fully able to patch the server. I'll be running it on the production server tonight after hours. Thank you so much!

How did you determine it needed KB5039214? I couldn't find any reference to that in the logs, so I'm curious what the indicator was. If I can get enough posts, I'd like to apply to take the training course in order to help other people with this type of issue as well.

 

[Maxstar]

Hi,

You're welcome and let me know the result of production server!

The ComponentsScanner log showed "Windows Server 2016 Standard x64 (10.0.14393.7070)" this build is KB5039214, and the CBS log showed the following issue:

2024-09-17 10:54:09, Info                  CBS    Failed to pin deployment while resolving Update: Package_72_for_KB5039214~31bf3856ad364e35~amd64~~10.0.1.9.5039214-114_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

So it seems this update was not correcty installed for some reason?!

 

[lg_spam]

Morning, it worked perfectly on the production server as well. Ah, I see that in the log now when searching for that phrase. I've downloaded CMTrace which should help if I run into something like this again.

The server has apparently been failing updates for months now - I recently joined my current company, and September was the first patching rotation I was brought into.

 

[Maxstar]

Good morning too, although it's mid-afternoon here

CMTrace is absolutely a useful tool and it will highlight such lines automatically, but most of the times I'm using Notepad, Notepad++ or Klogg for the larger logs.

Since this server is up-to-date now, we can mark this thread as solved...

 

[lg_spam]

Indeed, thanks again!

 

[Maxstar]

You're welcome. Glad I could help to resolve this issue..