[SOLVED] Great 2k12R2 and 0x80073712/0x80070490 :-(

M

minicoop

Well-known member
Joined
Nov 6, 2020
Posts
85
Hello,

i have only one 2k12R2 which makes me so trouble...
Actually it let me dont install the actuall kb5010419 Update.
Searching the log it says ERROR_SXS_COMPONENT_STORE_CORRUPT and
some Packages with the Status 0x80070490 - ERROR_NOT_FOUND
The six Packages seeams all Updates/fixes for dotnet 3.5
Great. DISM with /repair option does not work this time..
componentsscanner does not find any problems,
sfcfix also ok.

I attached the neccessary files in th zip and hope you can help us.

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-03-08 08:10:28, Info                  CBS    Failed to EnumerateComponentDeployment, component: amd64_microsoft-windows-msftedit_31bf3856ad364e35_6.3.9600.17031_none_c6c24b550b02ddda [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 08:10:28, Info                  CBS    Failed to load component owners on component: amd64_microsoft-windows-msftedit_31bf3856ad364e35_0.0.0.0_none_55c98a3737b93a60, version: 6.3.9600.17031 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 08:10:28, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-08 08:10:28, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

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

Hi, logfile is attached.

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-03-22 16:39:34.480
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .txt script file at C:\Users\admin\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a57c4885fd2..b4fcb73025c_31bf3856ad364e35_6.3.9600.17031_8957a428dd99f4b0.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a57c4885fd2..b4fcb73025c_31bf3856ad364e35_6.3.9600.17031_8957a428dd99f4b0.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a57c4885fd2..b4fcb73025c_31bf3856ad364e35_6.3.9600.17031_8957a428dd99f4b0.
RegistryScript:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2022-03-22 16:50:11.386
Script hash: qvMSzHys+Vts3dJrjq9uvw3ZUXuCKHdw2ASz6YnxbbA=
----------------------EOF-----------------------
 
Thank you, could you please run DISM again? If it fails, then please attach the latest CBS log.
 
Rich (BB code): 
2022-03-23 11:07:53, Error                 CSI    00000024 (F) HRESULT_FROM_WIN32(14098) #1127768# 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-03-23 11:07:53, Info                  CBS    Failed to EnumerateComponentDeployment, component: msil_system.windows.forms.resources_b77a5c561934e089_6.3.9600.20708_de-de_ba4d5959b26bad15 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-03-23 11:07:53, Info                  CBS    Failed to load component owners on component: msil_system.windows.forms.resources_b77a5c561934e089_6.3.0.0_de-de_934f027fb02a4359, version: 6.3.9600.20708 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

It's the same error as last time but with a different deployment key. Unfortunately, this key is more corrupt than the first one and therefore I'll need to have a look at your CBS hive. Could you please provide it 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 WeTransfer 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

It looks like there is a different error this time.

Rich (BB code): 
2022-03-25 16:29:07, Info                  CBS    Failed to get applicability on updates [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2022-03-25 16:29:07, Error                 CBS    Failed to call external evaluate applicability on package: Package_3098_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14, Update: 2919355-6533_neutral_GDR [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2022-03-25 16:29:07, Info                  CBS    Failed to evaluate applicability state for XML package: Package_3098_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2022-03-25 16:29:07, Error                 CBS    Failed to check whether package is partially installed, package: Package_for_KB2919355_RTM~31bf3856ad364e35~amd64~~6.3.1.14 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2022-03-25 16:29:07, Info                  CBS    Failed to evaluate external applicability for package update: 2919355-18566_neutral_PACKAGE [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2022-03-25 16:29:07, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2919355~31bf3856ad364e35~amd64~~6.3.1.14, Update: 2919355-18566_neutral_PACKAGE [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2022-03-25 16:29:07, Info                  CBS    Failed to call EvaluateApplicability on internal CBS package. [HRESULT = 0x8007000d]

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.
 
ok, that is strange..
Installation of KB5010419 is running without any errors over the gui.
i have attached the cbs Log File for you.
the process monitor tracefile is in onedrive,
you can find it under
onedrive

thank you.
best regards
 

Attachments

minicoop said:
Installation of KB5010419 is running without any errors over the gui.
Click to expand...
Did DISM/SFC report no problems then? If so, the error show in the CBS log may be a non-fatal error which can be safely ignored. It isn't uncommon to see errors like that in a CBS log.
 
Rich (BB code): 
(w)    CBS Watchlist Package Missing    0x80070490    Microsoft-Windows-DirectoryServices-ADAM-Tools-Package~31bf3856ad364e35~amd64~~0.0.0.0    Package_2207_for_KB5009624~31bf3856ad364e35~amd64~~6.3.1.12    
(w)    CBS Watchlist Package Missing    0x80070490    Microsoft-Windows-DirectoryServices-DomainController-SrvFnd-Package-ds~31bf3856ad364e35~amd64~~0.0.0.0    Package_2207_for_KB5009624~31bf3856ad364e35~amd64~~6.3.1.12    
(w)    CBS Watchlist Package Missing    0x80070490    Microsoft-Windows-DirectoryServices-DomainController-Tools-ClientRSAT-Package~31bf3856ad364e35~amd64~~0.0.0.0    Package_2207_for_KB5009624~31bf3856ad364e35~amd64~~6.3.1.12    
(w)    CBS Watchlist Package Missing    0x80070490    Microsoft-Windows-DirectoryServices-DomainController-Tools-Package-ds~31bf3856ad364e35~amd64~~0.0.0.0    Package_2207_for_KB5009624~31bf3856ad364e35~amd64~~6.3.1.12    
(w)    CBS Watchlist Package Missing    0x80070490    Microsoft-Windows-RSAT-NIS-Package-ds~31bf3856ad364e35~amd64~~0.0.0.0    Package_2207_for_KB5009624~31bf3856ad364e35~amd64~~6.3.1.12    
(w)    CBS Watchlist Component Missing    0x80070490    amd64_microsoft-windows-d..ommandline-repadmin_31bf3856ad364e35_0.0.0.0_none_80bcb82153a31ebd    Package_2207_for_KB5009624~31bf3856ad364e35~amd64~~6.3.1.12

Those are warnings and can be ignored, it just means those values are missing from the subkeys of PackageDetect and ComponentDetect in the CBS hive.

Since seem to be able to install updates with no problems and the latest run of DISM appears to be clear, then I think is safe to say, that this thread can be marked as solved.
 
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