[SOLVED] Error 80073712 when trying to install updates Server 2012 R2

[aschaef]

I was able to run through some windows updates and am getting an error 80073712 when trying to install the 3 remaining .net updates which are available. I ran through the following steps:

1) sfc /scannow which reported no component corruption
2) dism /online /cleanup-image /restorehealth - completed successfully and reported that the component store corruption was repaired
3) ran SFCFix.exe which reported no issues. Here is the output from the log file:

SFCFix version 3.0.0.0 by niemiro.Start time: 2018-09-22 22:46:20.867
Microsoft Windows Server 2012 R2 Update 3 - amd64
Not using a script file.








AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-09-22 22:57:15.362
----------------------EOF-----------------------

Link to the CBS.zip file is here: CBS.zip - Google Drive

Thank you very much for your assistance!

 

[Sysnative Windows Update]

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 and just provide the link here.

 

[aschaef]

COMPONENTS.zip link COMPONENTS.zip - Google Drive

 

[Sysnative Windows Update]

SFCFix Script

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.

Afterwards, try updates again and attach CBS.log if any fail.

 

[aschaef]

Does this require a reboot?

 

[Sysnative Windows Update]

The fix should not require a reboot, but the updates might.

 

[aschaef]

Results from running the fix script.

SFCFix version 3.0.0.0 by niemiro.Start time: 2018-09-24 14:01:14.290
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\x\Desktop\SFCFixScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5475a63f284d0ccf00e3656e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_none_43925dcee75e383d.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5475a63f284..56e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_43925dcee75e383d.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.3.0.0_none_c7e8faadf5dfa825.


Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5475a63f284d0ccf00e3656e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_none_43925dcee75e383d.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5475a63f284..56e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_43925dcee75e383d.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.3.0.0_none_c7e8faadf5dfa825.


Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.3.0.0_none_c7e8faadf5dfa825.


Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_5475a63f284d0ccf00e3656e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_none_43925dcee75e383d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5475a63f284..56e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_43925dcee75e383d.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.3.0.0_none_c7e8faadf5dfa825.
RegistryScript:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2018-09-24 14:01:14.993
Script hash: UJ4j5AB9S3Iv/kXNstI77MQEm5QI2+faJZflLJgxd34=
----------------------EOF-----------------------

I re-ran the 3 pending .NET updates and got the same failure code. New CBS.log file attached.View attachment CBS (2).zip

 

[Sysnative Windows Update]

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past. Make sure to select only one!
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

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 attach the LogFile.PML file as well as your CBS.log

 

[aschaef]

See attached for the procmon output as well as the latest CBS.log file.
View attachment Logfile.zip
View attachment CBS (3).zip

Thanks!

 

[Sysnative Windows Update]

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 and just provide the link here.

 

[aschaef]

Updated COMPONENTS file COMPONENTS (2).zip - Google Drive

 

[aschaef]

Would it interfere with your troubleshooting process if I tried running the following:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:d:\ /LimitAccess or sfc /scannow again?

 

[Sysnative Windows Update]

No, but, there is something going on in your registry and I have to figure out where exactly is the problem.

 

[aschaef]

No, but, there is something going on in your registry and I have to figure out where exactly is the problem.

No problem, thank you for all of your help.

 

[Sysnative Windows Update]

Was there RAM recently added/replaced/tested in the Server?

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 attached file 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.
6. Try updates and if any fail, attach CBS.log.

 

[aschaef]

Results of FRST64

Fix result of Farbar Recovery Scan Tool (x64) Version: 23.09.2018Ran by x (25-09-2018 23:01:43) Run:1
Running from C:\Users\x\Desktop
Loaded Profiles: x (Available Profiles: x)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
[-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5475a63f284..56e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_43925dcee75e383d]
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5475a63f284..56e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_43925dcee75e383d]
"appid"=hex:35,34,37,35,61,36,33,66,32,38,34,64,30,63,63,66,30,30,65,33,36,35,\
  36,65,32,64,33,37,35,33,34,39,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,36,2e,33,2e,39,36,30,30,2e,31,37,32,32,\
  36,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,6b,65,6e,3d,62,30,33,66,35,66,37,\
  66,31,31,64,35,30,61,33,61,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"="009a94944bbb41a97b8897ebbe7282156625f2562b1f2bee244e8240c56efce2"
"p!CBS_package_64_for_kb2966826~31bf3856ad364e35~amd64~~6.3.1.7.296_553d8d939f6307cb"=hex:51,\
  00,00,00,01,00,00,00,50,61,63,6b,61,67,65,5f,36,34,5f,66,6f,72,5f,4b,42,32,\
  39,36,36,38,32,36,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,36,2e,33,2e,31,2e,37,2e,32,39,36,36,38,32,36,2d,31,32,32,\
  38,5f,6e,65,75,74,72,61,6c,5f,47,44,52,32
"s!CBS_package_64_for_kb2966826~31bf3856ad364e35~amd64~~6.3.1.7.296_553d8d939f6307cb"=hex:51,\
  00,00,00,00,00,00,00,50,61,63,6b,61,67,65,5f,36,34,5f,66,6f,72,5f,4b,42,32,\
  39,36,36,38,32,36,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,36,2e,33,2e,31,2e,37,2e,32,39,36,36,38,32,36,2d,31,32,32,\
  38,5f,6e,65,75,74,72,61,6c,5f,47,44,52
EndRegedit:
*****************


Error: (0) Failed to create a restore point.


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


The operation completed successfully.




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


"HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\5475a63f284..56e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_43925dcee75e383d" => removed successfully


====> Registry


==== End of Fixlog 23:01:44 ====

 

[aschaef]

So far so good. The 3 pending .NET updates successfully installed! I'm testing out 2 more available .NET updates and they've both installed successfully. No new RAM installed on the server, it's the same VM that we deployed a while back. I did notice some issues after one update a while ago, but subsequent updates seemed to install successfully, i'm guessing until the next round of .NET updates.

Thanks again for your persistence and helping to figure this one out! I'd really love to read about how you go through the process if you have any tutorials posted.

 

[Sysnative Windows Update]

That is awesome news indeed.

Unfortunately, there are no documents, but I'd be happy to explain if your interested.

Upon inspecting the CBS.log, I have found the following:

2018-09-24 15:57:20, Error                 CSI    0000000c (F) HRESULT_FROM_WIN32(14098) #11107# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::EnumDeploymentReferences(flags = 00000003, tlcid = @0x1ec34eb280, pszSubscription = (null), pszCodebase = (null))
[gle=0x80073712]
2018-09-24 15:57:20, Info                  CBS    Failed to call EnumDeploymentReferences on deployment: [COLOR=#ff0000]amd64_5475a63f284d0ccf00e3656e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_none_43925dcee75e383d[/COLOR] [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2018-09-24 15:57:20, Info                  CBS    Failed to load deployment owners for deployment: amd64_5475a63f284d0ccf00e3656e2d375349_b03f5f7f11d50a3a_6.3.9600.17226_none_43925dcee75e383d. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2018-09-24 15:57:20, Info                  CBS    Failed to load component owners on component: amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.3.0.0_none_c7e8faadf5dfa825, version: 6.3.9600.17226 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2018-09-24 15:57:20, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2018-09-24 15:57:20, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

The key issue was in the key marked red. This means that:

a) The key is missing or b) there is corruption in the key. In your case, it was corruption.

In some cases, the corruption is very easy to spot because you can see for example: amd64_5*75a instead of the number, but in others it is very hard, so what I usually do is, I request the copy of the hive just as a preventive measure if something happens to go wrong, then I trace the missing deployment to an update which I forcibly install on my Server VM and then I delete the key on the user's machine and replace it with a clean copy to see if the error goes away.