[SOLVED] Server 2022 standard, cumulative update (KB5058385) failing with error 0x80073701

J

Jon3045

Member
Joined
May 26, 2025
Posts
17
This is a new Dell Poweredge server running windows 2022 standard. I installed the April 2025 cumulative updates with no problems a few weeks ago (first updates done on this server). I tried to install the May cumulative update (KB5058385) and the installation keeps failing with error 0X80073701. The CBL log seems to be showing an issue with a missing SXS assembly (Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~11.0.20348.380.Internet-Explorer-Optional-amd64), but those assemblies do seem to exist in the WinSXS folder.

Any help you can provide is greatly appreciated. I am not very familiar with debugging windows update issues like this. I have attached the componentsscanner log, and here is a link to the compressed CBS folder.

CBS.zip

Thanks!
John
 

Attachments

Hi @Jon3045,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
I know you guys are busy and I appreciate all you do here to help people...so this post isn't to try to rush anyone :) Just want to make sure my thread stays active because I am still stuck with this issue. Thanks!
 
Hi and weclsome 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.

Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Hi,

Download
67139f7e69a58-SFCFix-ico.PNG
SFCFix and save it to your desktop.

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.
67139f52b3c1e-SFCFix-Zip-Eng.gif

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

Attachments

After running SFCFix, the attempt to apply the update failed. I have attached SFCFix.txt and a link to new CBS log folder. Thanks!

CBS-2.zip
 

Attachments

Hi,

Follow these instructions to remove an update.
  • Open the Start menu of Windows and type the command CMD
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
  • When command prompt opens, copy and paste the following command into it, then press enter.
Code: 
wusa /uninstall /KB:5021656
  • Let me know if it says it was successful or you get the message: The update KB5021656 is not installed on this computer.
 
After running the command you provided, the output was "The update KB5021656 is not installed on this computer."
 
Hi,

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Open the startmenu and type the command cmd.
  • After you find the Command Prompt, right click on it and select Run as Administrator.
  • Copy and paste the following into the Command Prompt and press enter.
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Registry button.
Code: 
KB5021656
  • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
  • Post the logfile SearchReg.txt as attachment in your next reply.
 
Hi,

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

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

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

Attachments

instructions completed successfully
Farbar did not request a restart when it ran.
fixlog.txt is attached
attempted the update again and it was not successful.
Here is a link to new copy of CBS: CBS-3.zip
 

Attachments

Hi,

Step 1. Try to uninstall the following update:
Code: 
wusa /uninstall /KB:5030216
When you get the message: The update KB******* is not installed on this computer, then perform step 2.

Step 2.
1. Open a elevated command prompt and run the following command (to be sure that the COMPONENTS hive is loaded).
Code: 
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
2. Open FRST64.exe as administrator and perform a registry search for:
Code: 
KB5030216
3. Attach SearchReg.txt in your next reply.
 
Hi,

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

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

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

Attachments

performed instructions as requested.
Windows Defender popped up a threat detected message it seems just as FRST64 was completing the fix, but a fixlog was created and it seems as if it completed (attached)
no restart was required by FRST64
Attempted to install the update again, but it failed.
Link to new CBS log: CBS-4.zip
 

Attachments

Do you have recent backups of this server before the problem started?
 
Yes, I should - let me give you a brief timeline on this issue and what backups I have:

5/1/2025 - Server initially powered on, basic configuration tasks were performed, April cumulative windows updates were installed - installed without error
5/2/2025 1am - first windows server backup was run
5/2/2025 - 5/9/2025 - server in various stages of being built out, windows server backup each morning at 1am. No attempts to install any updates, and no issues building out server to that point.
5/10/2025 - 5/25/2025 - server was powered off intentionally
5/26/2025 - about 1:18 PM server was powered back on. windows server backup kicked off automatically at that same time (backup is dated at 1:22pm), the windows update KB5058385 was downloading and installing at about this same time. That install failed (I wonder if this is where the problem began, but not sure) and I made this forum post that evening.
5/27/2025 - today - windows server backups each morning at 1am. Nothing else has been done to the server during this time other than the steps we have been taking in this thread to attempt to resolve this issue.

Also, as I was looking thru the event log to get these dates correct, I noticed this entry which I had not found before, not sure if it sheds any light:

Code: 
Log Name:      System
Source:        Microsoft-Windows-Kernel-General
Date:          5/26/2025 1:19:38 PM
Event ID:      15
Task Category: (10)
Level:         Information
Keywords:    
User:          SYSTEM
Computer:      MSM6
Description:
Hive \??\C:\Windows\System32\config\COMPONENTS was reorganized with a starting size of 148942848 bytes and an ending size of 144678912 bytes.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-General" Guid="{a68ca8b7-004f-d7b6-a698-07e2de0f1f5d}" />
    <EventID>15</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>10</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2025-05-26T18:19:38.9229110Z" />
    <EventRecordID>6145</EventRecordID>
    <Correlation />
    <Execution ProcessID="6696" ThreadID="6724" />
    <Channel>System</Channel>
    <Computer>MSM6</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="HiveNameLength">41</Data>
    <Data Name="HiveName">\??\C:\Windows\System32\config\COMPONENTS</Data>
    <Data Name="OriginalSize">148942848</Data>
    <Data Name="NewSize">144678912</Data>
  </EventData>
</Event>

Let me know what you think...
 
Hi,
Jon3045 said:
(I wonder if this is where the problem began, but not sure)
Click to expand...
I think so, and what you can try is to load the backup of 5/9/2025 in a virtual testing environment to see how runs and/or Windows Update is working.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top