[SOLVED] Windows update error 0x80073712

az9191

Member
Joined
Apr 1, 2022
Posts
7
Hi,

I'm having trouble with a Server 2019 STD 1809 installation where WU fails with error 0x80073712. I have ran the usual

SFC /scannow
dism /online /cleanup-image /restorehealth (+ /source: from another functioning server 2019 source with same version and build)
SFCFix, no errors

running DISM from an alternate source has fixed a few corrupt items within the winsxs folder anr. DISM does not report any corruption anymore when I run it. However, WU is still failing with the same error code 0x80073712. CBS Logs attached.

Code:
2022-04-01 13:46:19, Error                 CSI    0000001c@2022/4/1:11:46:19.965 (F) Attempting to mark store corrupt with category [l:22 ml:23]'CorruptDeploymentValue'[gle=0x80004005]
2022-04-01 13:46:19, Error                 CSI    0000001d@2022/4/1:11:46:19.965 (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-04-01 13:46:19, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2022-04-01 13:46:19, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220401105334.log to WER report.
2022-04-01 13:46:20, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220401092656.log to WER report.
2022-04-01 13:46:20, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220401091734.log to WER report.
2022-04-01 13:46:20, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220401023133.log to WER report.
2022-04-01 13:46:20, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20220326111550.log to WER report.
2022-04-01 13:46:20, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-04-01 13:46:20, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-04-01 13:46:20, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-04-01 13:46:20, Error                 CSI    0000001e (F) HRESULT_FROM_WIN32(14098) #1954360# 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-01 13:46:20, Info                  CBS    Failed to EnumerateComponentDeployment, component: wow64_microsoft-windows-n..orkconnectionbroker_31bf3856ad364e35_10.0.17763.1697_none_b478f16ecb235ab4 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to load component owners on component: wow64_microsoft-windows-n..orkconnectionbroker_31bf3856ad364e35_0.0.0.0_none_e6fc8bb4f9ca3d30, version: 10.0.17763.1697 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    ComponentAnalyzerEvaluateSelfUpdate call failed. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to evaluate self update [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to evaluate non detect parent update [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to evaluate non parent [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    failed to evaluate single applicability [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to evaluate applicability [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to get applicability [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to get applicable state for update. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to populate updates for package: Package_3035_for_KB5005568~31bf3856ad364e35~amd64~~10.0.1.9 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to add child package to the strategy [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to add package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.2183.1.9 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to recall or supersed lower version on package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.2686.1.6 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to process mum servicing on package:Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.2686.1.6 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to add package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.2686.1.6 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    Failed to plan execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-04-01 13:46:20, Info                  CBS    WER: Generating failure report for package: Package_for_ServicingStack_2510~31bf3856ad364e35~amd64~~17763.2510.1.2, status: 0x80073712, failure source: CBS Other, start state: Installed, target state: Installed, client id: WindowsUpdateAgent
2022-04-01 13:46:20, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
 

Attachments

Hi,

I am checking to see if you still need help with this problem. If so, please upload a copy of the COMPONENTS and the CBS hive.

Step 1. 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.


Step 2. 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.
 
Last edited:
Hi,

Please export the Component Based Servicing key as a HIVE file as described in post #2 instead of REG file.
 
Hi,

Step 1. Download
56f31e53c97da-SFCFix.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.
6190d993a26f3-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.


Step 2. Run the System File Checker.
  • Click the Start button and in the search box, type Command Prompt
  • 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, and press enter.
    Code:
    sfc /scannow
  • Take a screenshot of the commandprompt window and paste it into your next reply.
 

Attachments

Here is the screen shot and sfcfix-log. When I first ran sfcfix it ran steps 1-6 (with steps 5a to 5m i think) but crashed and left no logfile. I then ran it again from a different directory and it ran successfully (and much faster) and also produced the logfile below. after that I ran sfc /scannow

I then ran WU again and now there's the same errorcode but looking at the CBS.log there is a different component that now fails..

1650884614269.png
 

Attachments

Hi,

Please attach a new copy of the CBS log and the COMPONENTS hive, see the instructions in post#2.
 
Hi,

Step 1. Run SFCFix again with the attached script.
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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-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.


Step 2. Reboot the system and run Windows Update again. If it fails attach a new copy of the CBS log.
 

Attachments

Fantastic. It works now. Thank you so much.

Is this procedure explained somewhere on this forum? I'm curious how you match the failed component in the CBS log to the corresponding entry in the component hive.. If that's even what you do. I'm just speculating :)
 
Hi,

Your welcome! Glad to here everything is working fine now.
az9191 said:
Is this procedure explained somewhere on this forum? I'm curious how you match the failed component in the CBS log to the corresponding entry in the component hive.. If that's even what you do. I'm just speculating :)
For this kind of corruptions there is no (common) tutorial available, but other tutorials can be found in this subforum.

In short:
There were two Deployments KEY's corrupt in the COMPONENTS hive, with the information from the ComponentDetect KEY in the CBS hive - I rebuild both keys. The names of both keys are in the CBS.log. Additionally, the following file was missing in the WinSxS directory.
Rich (BB code):
C:\Windows\WinSxS\amd64_netfx4-system.windows.controls.ribbon_b03f5f7f11d50a3a_4.0.15744.805_none_a68c2c9aef3eb864\System.Windows.Controls.Ribbon.dll
 

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

Back
Top