[SOLVED] Server 2016 - Windows updates fail with "Error STATUS_SXS_COMPONENT_STORE_CORRUPT"

W

WindowsBlue

Member
Joined
Apr 2, 2022
Posts
8
Hello,

I'm at a lost and hoping someone can lend some help!

A few days ago Windows updates first started to fail on a Server 2016, I did the usual troubleshooting:
- dism /online /clean-image /scanhealth
- The above command reported corruption and that they are repairable. So I mounted the ISO and did "dism /online /clean-image /restorehealth /source:wim:path-to-wim:4 /limitaccess" (the server is datacenter edition with desktop experience).

The repair was successful - it found 9 instances of corruption and repaired all of them. Rebooted the server and the /scanhealth command as well as "sfc /scannow" all returned clean; yet, updates continued to fail. I then downloaded sfcfix, and again the tool reported no corruptions are detected.

It'll be greatly appreciated if someone can take a look at the attached CBS.log and help me find a way to have this fixed.

Thank you!
 

Attachments

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. 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.
3. 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.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
 
Rich (BB code): 
2022-04-03 11:01:44, Error                 CSI    00000008 (F) HRESULT_FROM_WIN32(14098) #264973# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::EnumComponentsDeployments(flags = (ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_PINNED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_INSTALLED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_ASSEMBLY_NOT_FOUND_RETURNS_NULL), cComponents = 1)
[gle=0x80073712]
2022-04-03 11:01:44, Info                  CBS    Failed to EnumerateComponentDeployment, component: wow64_microsoft-windows-m..ntmanifests-windows_31bf3856ad364e35_10.0.14393.4169_none_8707d5e15a94c6c1 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-03 11:01:44, Info                  CBS    Failed to load component owners on component: wow64_microsoft-windows-m..ntmanifests-windows_31bf3856ad364e35_0.0.0.0_none_913e50a1008cf31a, version: 10.0.14393.4169 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-03 11:01:44, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-03 11:01:44, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Thanks, could you please provide your CBS hive using the following instructions:

Export CBS hive
  • Click on the Start button and in the search box, 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 To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.
 
SFCFixScript.txt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]
 

Attachments

Thank you! Here is what is in the SFCFix.txt (removed the username in the folder path):

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-04-17 18:54:06.618
Microsoft Windows Server 10 Build 14393 - amd64
Using .txt script file at C:\Users\**username**\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\cb08cdca123..b5e1c4a354a_31bf3856ad364e35_10.0.14393.4169_55ea6d1abd03453a.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\cb08cdca123..b5e1c4a354a_31bf3856ad364e35_10.0.14393.4169_55ea6d1abd03453a.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\cb08cdca123..b5e1c4a354a_31bf3856ad364e35_10.0.14393.4169_55ea6d1abd03453a.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2022-04-17 18:54:10.103
Script hash: 1jiY90+wCKGTFT2k95zeryOz8Yu7S0OmaZwk+b92ZcI=
----------------------EOF-----------------------
 
Could you please open an elevated command prompt and then enter the following command:

Rich (BB code): 
DISM /Online /Cleanup-Image /RestoreHealth

Please post your latest CBS log if it fails.
 
Good Morning! Thanks again for the helps :-) The DISM operation completed successfully. Should we try to apply Windows updates again?
 
Rich (BB code): 
2022-04-18 17:42:40, Info                  CBS    Failed to EnumerateComponentDeployment, component: wow64_microsoft-windows-m..elmanifests-windows_31bf3856ad364e35_10.0.14393.4169_none_2175a4028b776669 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-18 17:42:40, Info                  CBS    Failed to load component owners on component: wow64_microsoft-windows-m..elmanifests-windows_31bf3856ad364e35_0.0.0.0_none_2bac1ec2316f92c2, version: 10.0.14393.4169 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-18 17:42:40, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-18 17:42:40, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

It's the same problem as before but with a different deployment key.

SFCFixScript.txt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]

    If it is successful, then please attempt Windows Update again.
 

Attachments

Apologies about the delayed response. I tried to apply a couple of Windows updates today and the error is still persisting. It is a different component this time. Please see attached CBS log.

Edit: this is after successfully applying the above SFCFixScript.txt.
 

Attachments

Rich (BB code): 
2022-04-19 18:05:34, Info                  CBS    Failed to EnumerateComponentDeployment, component: msil_microsoft.identitymodel_31bf3856ad364e35_10.0.14393.4046_none_8fc9892f5f6f8d7a [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-19 18:05:34, Info                  CBS    Failed to load component owners on component: msil_microsoft.identitymodel_31bf3856ad364e35_0.0.0.0_none_99f6f03f056e5555, version: 10.0.14393.4046 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-19 18:05:34, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-19 18:05:34, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Okay, just checked and it appears that you have around 2,107 corrupted deployment keys. I can try and rebuild them using a Windows Server 2016 VM.

Could you please create a backup of your current COMPONENTS hive and then replace it using the version available on my Google Drive. Afterwards, please attempt Windows Update again and then attach your CBS log if it fails.

COMPONENTS - WindowsBlue.zip
 
Good morning and a million thanks!! That finally did it, installed March cumulative update and it didn't error out. Restarted the server, and then successfully applied April cumulative update as well.

I cannot express my gratitude enough, it would have been painful to rebuild the server (by the time the problem was discovered, all the good backups had already been purged). I'm still in shock as to how the server ended up with over 2k corrupted deployment keys ...
 
WindowsBlue said:
I'm still in shock as to how the server ended up with over 2k corrupted deployment keys ...
Click to expand...
It's more common than you think, I'm not sure why exactly it happens, but I've see quite a few server machines with 100s or even 1000s of deployment keys with no information in them. It's a really annoying error too because the CBS log will typically only show one key at a time; sometimes you can get lucky though and it will only be one or two corrupted keys.

I would highly recommend that you create a backup of your server now too. I'm glad everything is up to date now though!
 
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