Error 0x80073701 [ERROR_SXS_ASSEMBLY_MISSING] with installing any cumulative security update [LCU] - Windows 10 Pro 22H2 (Build 19045.2006)

[Wergind]

Hello everyone
There is a problem in the image, namely when installing the cumulative security update. Through the security update center or separately through the .msu or .cab file, in any case there is an error. Removing other updates or standard recovery methods do not help in any way and do not find any broken components in the system. I tried to restore the component store through another .vim image, but it did not help. I locally transferred all components from the WinSxS to image identical to the original build and transferred them from the packages folder, but this also did not help. In the "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" registry, I tried to change the current state values to 0 for the packages from the CBS log, also without results. Now the system image is deployed on a virtual machine, and I am trying to restore it, but so far it does not work, so I ask for help in solving the problem. I will additionally inform you that restoring the system via Media Creation Tool or another image via the installer setup eliminates the problem and the system works and updates fine, but I am interested in how can restore the system without using this method. Below I attach logs with the system after installation and an attempt to update

In CBS.log I find the following error:
2025-05-18 16:03:08, Info CBS Failed to pin deployment while resolving Update: Microsoft-Windows-Holographic-Desktop-Merged-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.5848.7971f592f619803f090bc33ca3248534 from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2025-05-18 16:03:08, Info CBS Failed to bulk stage deployment manifest and pin deployment for package: Package_1_for_KB5011069~31bf3856ad364e35~amd64~~10.0.1.8028 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2

 

[Windows Update Bot]

Hi @Wergind,

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

 

[Maxstar]

Hi and welcome to Sysnative,

I tried to restore the component store through another .vim image, but it did not help. I locally transferred all components from the WinSxS to image identical to the original build and transferred them from the packages folder, but this also did not help. In the "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" registry, I tried to change the current state values to 0 for the packages from the CBS log, also without results. Now the system image is deployed on a virtual machine, and I am trying to restore it, but so far it does not work, so I ask for help in solving the problem.

Do you have a backup before you did all of the above to try to fix the problem?

 

[Wergind]

Hi and welcome to Sysnative,


Do you have a backup before you did all of the above to try to fix the problem?

Yes. I made snapshots on a virtual machine and after changes, if something goes wrong, I roll back. I essentially have the .iso image itself, which I can test endlessly

 

[Maxstar]

Okay, please revert the system to the first snapshot without any fiixes. Then we can start from the beginning tofix this issue.

 

[Wergind]

Okay, please revert the system to the first snapshot without any fiixes. Then we can start from the beginning tofix this issue.

Okay. By the way, the logs I attached were made before all the changes etc., that is, at the stage we are at now (clean system).

 

[Maxstar]

Let's check some things.

Upload a copy of the CBS folder

• Open Windows Explorer and browse to the C:\Windows\Logs folder.
• Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
• Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
• Click on the Yes button here.

• Attach the file CBS.zip to your next reply. If the file is too large to attach, upload the CBS.zip file to www.wetransfer.com and post the link in your next reply.

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.
  

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (*.*).
  
  
  
  
  
• 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.

 

[Wergind]

Here are the attached files:

 

[Maxstar]

The CBS logs shows issues which I cannot find in the HIVE files and both of them are completely out of sync! So this is not a clean build / snapshot when the problem started!

 

[Wergind]

As I said before, I have a problem with this image. The logs I sent are what happened right after installing the system and trying to update and install the LCU. This is a corporate image that is common on most computers. I didn't make it, but I want to figure it out and understand what the problem is and why it can't install LCU updates.

 

[Maxstar]

1. This image is pretty out-dated it's build back into 2022?
2. Why are you still using this image instead of an up-to-date image for build 22H2?