[SOLVED] 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT - Server 2016 CU 2019-12

KB What · Jan 7, 2020

My Google searches for "0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT" has lead me here, with many others having similar issues. Thanks to the specialists on this forum many are finding solutions.

I am having some issues installing the December 2019 CU (kb4530689) on one of our Server 2016 (1607) servers.

I have executed the following commands and programs - no corruptions or issues detected:

Code:

sfc /scannow

Dism /Online /Cleanup-Image /RestoreHealth

SFCFix

When attempting to install the update, it fails with 80073712. Looking into the CBS log for a failed install the following is towards the end.

Code:

Failed to call EnumDeploymentReferences on deployment: amd64_1ccde093be57ab08bd7bd2f3b9b017d1_31bf3856ad364e35_10.0.14393.3321_none_32ef441447fe4607 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-01-07 12:52:22, Info                  CBS    Failed to load deployment owners for deployment: amd64_1ccde093be57ab08bd7bd2f3b9b017d1_31bf3856ad364e35_10.0.14393.3321_none_32ef441447fe4607. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-01-07 12:52:22, Info                  CBS    Failed to load component owners on component: wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_0.0.0.0_none_628289ed3985ca25, version: 10.0.14393.3321 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-01-07 12:52:22, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2020-01-07 12:52:22, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

I've been battling for days, any assistance would of course be greatly appreciated.

Sysnative Windows Update · Jan 7, 2020

Hello and welcome!

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.

KB What · Jan 7, 2020

COMPONENTS.zip

Regards.

Sysnative Windows Update · Jan 7, 2020

Thank you.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

KB What · Jan 7, 2020

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 28-12-2019
Ran by user (08-01-2020 08:43:04) Run:1
Running from C:\Users\user\Desktop
Loaded Profiles: user (Available Profiles: user)
Boot Mode: Normal
==============================================

fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_0.0.0.0_none_628289ed3985ca25]
StartRegedit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_0.0.0.0_none_628289ed3985ca25]
"Package_3690_for_KB3213986~31bf3856ad364e35~amd64~~10.0.1.1.3213986-7184_neutral"="10.0.14393.447@2"
"Package_6486_for_KB4480961~31bf3856ad364e35~amd64~~10.0.1.3.4480961-14271_neutral"="10.0.14393.2608@2"
"Package_6510_for_KB4480977~31bf3856ad364e35~amd64~~10.0.1.7.4480977-14330_neutral"="10.0.14393.2758@2"
"Package_6485_for_KB4487026~31bf3856ad364e35~amd64~~10.0.1.6.4487026-14310_neutral"="10.0.14393.2791@2"
"Package_6492_for_KB4489882~31bf3856ad364e35~amd64~~10.0.1.6.4489882-14324_neutral"="10.0.14393.2848@2"
"Package_6503_for_KB4493470~31bf3856ad364e35~amd64~~10.0.1.5.4493470-14366_neutral"="10.0.14393.2879@2"
"Package_5959_for_KB4519979~31bf3856ad364e35~amd64~~10.0.1.7.4519979-11391_neutral"="10.0.14393.3297@2"
"Package_6906_for_KB4530689~31bf3856ad364e35~amd64~~10.0.1.8.4530689-13645_neutral"="10.0.14393.3321@2"
EndRegedit:
*****************

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_0.0.0.0_none_628289ed3985ca25" => removed successfully
Registry ====> ERROR: Error accessing the registry.

==== End of Fixlog 08:43:05 ====

Edit: Thanks a lot, by the way!

Sysnative Windows Update · Jan 7, 2020

Please take ownership of the Component Based Servicing key.

KB What · Jan 7, 2020

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 28-12-2019
Ran by user (08-01-2020 08:58:54) Run:3
Running from c:\Users\user\Desktop
Loaded Profiles: user (Available Profiles: user)
Boot Mode: Normal
==============================================

fixlist content:
*****************
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_0.0.0.0_none_628289ed3985ca25]
StartRegedit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_0.0.0.0_none_628289ed3985ca25]
"Package_3690_for_KB3213986~31bf3856ad364e35~amd64~~10.0.1.1.3213986-7184_neutral"="10.0.14393.447@2"
"Package_6486_for_KB4480961~31bf3856ad364e35~amd64~~10.0.1.3.4480961-14271_neutral"="10.0.14393.2608@2"
"Package_6510_for_KB4480977~31bf3856ad364e35~amd64~~10.0.1.7.4480977-14330_neutral"="10.0.14393.2758@2"
"Package_6485_for_KB4487026~31bf3856ad364e35~amd64~~10.0.1.6.4487026-14310_neutral"="10.0.14393.2791@2"
"Package_6492_for_KB4489882~31bf3856ad364e35~amd64~~10.0.1.6.4489882-14324_neutral"="10.0.14393.2848@2"
"Package_6503_for_KB4493470~31bf3856ad364e35~amd64~~10.0.1.5.4493470-14366_neutral"="10.0.14393.2879@2"
"Package_5959_for_KB4519979~31bf3856ad364e35~amd64~~10.0.1.7.4519979-11391_neutral"="10.0.14393.3297@2"
"Package_6906_for_KB4530689~31bf3856ad364e35~amd64~~10.0.1.8.4530689-13645_neutral"="10.0.14393.3321@2"
EndRegedit:
*****************

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\wow64_microsoft-windows-b..re-memorydiagnostic_31bf3856ad364e35_0.0.0.0_none_628289ed3985ca25 => not found
Registry ====> The operation completed successfully.


==== End of Fixlog 08:58:59 ====

I've had a peek in the registry and they've been created.

Regards

Sysnative Windows Update · Jan 7, 2020

Great!

Retry updates and attach CBS.log if any fail.

KB What · Jan 8, 2020

Sorry for the late reply. Updates failed with similar error. See attached CBS.log

Regards

Sysnative Windows Update · Jan 8, 2020

No worries.

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

KB What · Jan 8, 2020

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 28-12-2019
Ran by user (09-01-2020 12:00:09) Run:2
Running from C:\Users\Administrator\Desktop
Loaded Profiles: user (Available Profiles: user)
Boot Mode: Normal
==============================================

fixlist content:
*****************
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_1ccde093be57ab08bd7bd2f3b9b017d1_31bf3856ad364e35_10.0.14393.3321_none_32ef441447fe4607]
[-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ccde093be5..2f3b9b017d1_31bf3856ad364e35_10.0.14393.3321_32ef441447fe4607]
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_1ccde093be57ab08bd7bd2f3b9b017d1_31bf3856ad364e35_10.0.14393.3321_none_32ef441447fe4607]
"S256H"=hex:c3,9c,c1,17,8d,5c,5e,b2,64,27,d7,26,8c,b0,1f,56,3b,69,3f,05,95,2b,\
  fd,cb,1c,3c,49,88,e1,eb,09,d5
"identity"=hex:31,63,63,64,65,30,39,33,62,65,35,37,61,62,30,38,62,64,37,62,64,\
  32,66,33,62,39,62,30,31,37,64,31,2c,20,43,75,6c,74,75,72,65,3d,6e,65,75,74,\
  72,61,6c,2c,20,56,65,72,73,69,6f,6e,3d,31,30,2e,30,2e,31,34,33,39,33,2e,33,\
  33,32,31,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,\
  38,35,36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,72,63,\
  68,69,74,65,63,74,75,72,65,3d,61,6d,64,36,34,2c,20,76,65,72,73,69,6f,6e,53,\
  63,6f,70,65,3d,4e,6f,6e,53,78,53
"CF"=dword:0000000c
"c!1ccde093be5..2f3b9b017d1_31bf3856ad364e35_10.0.14393.3321_32ef441447fe4607"=hex:

[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ccde093be5..2f3b9b017d1_31bf3856ad364e35_10.0.14393.3321_32ef441447fe4607]
"appid"=hex:31,63,63,64,65,30,39,33,62,65,35,37,61,62,30,38,62,64,37,62,64,32,\
  66,33,62,39,62,30,31,37,64,31,2c,20,43,75,6c,74,75,72,65,3d,6e,65,75,74,72,\
  61,6c,2c,20,56,65,72,73,69,6f,6e,3d,31,30,2e,30,2e,31,34,33,39,33,2e,33,33,\
  32,31,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,\
  35,36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,63,65,73,73,6f,72,41,72,63,68,\
  69,74,65,63,74,75,72,65,3d,61,6d,64,36,34,2c,20,76,65,72,73,69,6f,6e,53,63,\
  6f,70,65,3d,4e,6f,6e,53,78,53
"CatalogThumbprint"="39a372d9a9e052e218583164b70c3347fcf55675a70f7c2b6ebb21838885c62c"
"p!CBS_package_6906_for_kb4530689~31bf3856ad364e35~amd64~~10.0.1.8._8f7277d2f5b0c825"=hex:51,\
  00,00,00,01,00,00,00,50,61,63,6b,61,67,65,5f,36,39,30,36,5f,66,6f,72,5f,4b,\
  42,34,35,33,30,36,38,39,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,\
  7e,61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,38,2e,34,35,33,30,36,38,39,2d,\
  31,33,36,34,35,5f,6e,65,75,74,72,61,6c,32
"s!CBS_package_6906_for_kb4530689~31bf3856ad364e35~amd64~~10.0.1.8._8f7277d2f5b0c825"=hex:51,\
  00,00,00,00,00,00,00,50,61,63,6b,61,67,65,5f,36,39,30,36,5f,66,6f,72,5f,4b,\
  42,34,35,33,30,36,38,39,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,\
  7e,61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,38,2e,34,35,33,30,36,38,39,2d,\
  31,33,36,34,35,5f,6e,65,75,74,72,61,6c
"i!CBS_package_6906_for_kb4530689~31bf3856ad364e35~amd64~~10.0.1.8._8f7277d2f5b0c825"=hex:51,\
  00,00,00,01,00,00,00,50,61,63,6b,61,67,65,5f,36,39,30,36,5f,66,6f,72,5f,4b,\
  42,34,35,33,30,36,38,39,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,\
  7e,61,6d,64,36,34,7e,7e,31,30,2e,30,2e,31,2e,38,2e,34,35,33,30,36,38,39,2d,\
  31,33,36,34,35,5f,6e,65,75,74,72,61,6c,32

EndRegedit:
*****************


========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

The operation completed successfully.


========= End of CMD: =========

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_1ccde093be57ab08bd7bd2f3b9b017d1_31bf3856ad364e35_10.0.14393.3321_none_32ef441447fe4607 => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ccde093be5..2f3b9b017d1_31bf3856ad364e35_10.0.14393.3321_32ef441447fe4607 => removed successfully
Registry ====> The operation completed successfully.


==== End of Fixlog 12:00:10 ====

Thank you very much.

You're a champion, the update installed without issue.

Quick question - which fixlist actually fixed it? or was it a combination of the two? I only ask as I would like to keep the server as clean as possible. I would like to revert and apply only the fix that actually fixed.

Once again thank you very much.

Sysnative Windows Update · Jan 8, 2020

Hi!

That's awesome!

I get what you are saying and that is why there were two fixes.

The first one was to register the missing component for December and fix the issue fully (in case the registry had the necessary information). As that did not work and the same error was reported, I figured that additional registry information was missing, so I provided it to the Server.

Should you remove either of the two fixes, I believe that you would break the Server again.

KB What · Jan 8, 2020

Understood. I will leave as is.

Thanks a lot.

Sysnative Windows Update · Jan 8, 2020

My pleasure!

[SOLVED] 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT - Server 2016 CU 2019-12

KB What

Member

Sysnative Windows Update

Inactive

KB What

Member

Sysnative Windows Update

Inactive

Attachments

KB What

Member

Sysnative Windows Update

Inactive

KB What

Member

Sysnative Windows Update

Inactive

KB What

Member

Attachments

Sysnative Windows Update

Inactive

Attachments

KB What

Member

Sysnative Windows Update

Inactive

KB What

Member

Sysnative Windows Update

Inactive