[SOLVED] Unable to install Windows Server 2019 update KB5013888

S

sysanalyst001

Well-known member
Joined
Mar 16, 2022
Posts
92
Hi, I'm trying to install the June 2022 .NET Framework 3.5 and 4.8 cumulative update (KB5013888) on a Server 2019 machine but the installation is failing with error 0x80073712. Manually downloading and installing the update file from Microsoft Update Catalog gives the same result. Running dism /online /cleanup-image /checkhealth gives the message 'No component store corruption detected' but the output from this command changes to 'The component store is repairable' after attempting to install KB5013888.

The equivalent .NET Framework update for May 2022 (KB5013641) has the same issue but the 'main' Windows cumulative updates (e.g. KB5014692) install successfully - if it helps, the server in question is the same as the one in this thread.

I've attached the CBS logs, the ComponentBasedServicing hive file and uploaded the COMPONENTS file here. Any help on this would be appreciated.
 

Attachments

Hello @sysanalyst001 :-) ,

I've had a look at your CBS log and also the COMPONENTS hive and I can see that you have a corrupt deployment key. Indeed the error suggests this:

Code: 
2022-06-15 14:23:11, Error                 CSI    00000007@2022/6/15:13:23:11.807 (F) Attempting to mark store corrupt with category [l:22 ml:23]'CorruptDeploymentValue'[gle=0x80004005]
2022-06-15 14:23:11, Error                 CSI    00000008@2022/6/15:13:23:11.807 (F) onecore\base\wcp\componentstore\storelayout.cpp(4001): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function ComponentStore::CRawStoreLayout::QueryTlcDataIdentity expression: (null)
[gle=0x80004005]

2022-06-15 14:23:14, Error                 CSI    00000009 (F) HRESULT_FROM_WIN32(14098) #107312# 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-06-15 14:23:14, Info                  CBS    Failed to EnumerateComponentDeployment, component: amd64_wcf-system.servicemodel_b03f5f7f11d50a3a_10.0.17763.17010_none_8a94e050c1d4add6 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-06-15 14:23:14, Info                  CBS    Failed to load component owners on component: amd64_wcf-system.servicemodel_b03f5f7f11d50a3a_10.0.0.0_none_69f79ae9859f0507, version: 10.0.17763.17010 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-06-15 14:23:14, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-06-15 14:23:14, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Please follow the instructions below to correct this. I am hoping this will be sufficient to get you working again even though I have not been able to get all the deployments rebuilt for you. Unfortunately they were completely missing from your COMPONENTS hive.

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. Attach this file into your next post for me to check please.
 

Attachments

Last edited:
Please run DISM and see if there are any further errors to fix. You will need to provide the new CBS log for me to check if there are errors.
 
Please also run SFC /scannow and provide the new CBS logs
 
I suspect the problems are due to the fact that I was not able to find all the missing deployment keys as mentioned in my first post. This is the reason these particular errors are so difficult to fix. I will try and search for the remaining ones.
 
Let's see if we can trace the problem another way:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.
j8MhY5V.png

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
 
Ah, OK, that's great news! I should have asked you to check that sooner :-)
 
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