[SOLVED] DISM errors and problems patching my system

Remy

Well-known member
Joined
May 5, 2022
Posts
108
Goodmorning Sysnative,

I have some problems with updating my system. I see there are some DISM errors.
Can you please help me fix the errors and patching my system again?

See the attachment with the latest CSB log.

Kind regards,
Remy
 

Attachments

Hi,

  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.
 
Hi and good morning,

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.


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.
 
This files contains the CBS folder instead of the zipped Component Based Servicing hive.
 
Rich (BB code):
2023-02-07 09:39:46, Error                 CSI    00000009 (F) HRESULT_FROM_WIN32(14098) #2104712# 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]
2023-02-07 09:39:46, Info                  CBS    Failed to EnumerateComponentDeployment, component: wow64_microsoft-windows-com-base-qfe-ole32_31bf3856ad364e35_10.0.17763.2989_none_03c5ace0f8ac5854 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2023-02-07 09:39:46, Info                  CBS    Failed to load component owners on component: wow64_microsoft-windows-com-base-qfe-ole32_31bf3856ad364e35_0.0.0.0_none_366ae2df2739cfeb, version: 10.0.17763.2989 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

No problem at all.

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 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. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

See the attachment. Dism restore command is finished. I try to update the machine now.
I'l let you know the results.
 

Attachments

Sadly the Windows updates failed again with error 0x80073712.
I uploaded the CSB logs in the attachment again.
 

Attachments

Unfortunately, the script for SFCFix failed, please perform the following steps.

Step 1. Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.


Step 2. Download
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner and save it to your desktop.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 

Attachments

Could you please provide a new copy of the COMPONENTS hive.

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.
 
Strange, in post #12 ComponentsScanner reported an corrupted key, but the upload Components hive looks good.
So I would suggest to attempt to update again and see what happens this time.
 
Windows updates are installed succesfully. So thats good!
If i run DISM checkhealth, i still get an "the component store is repairable" message.

I uploaded the latest CSB logs in the attachment.
 

Attachments

Let's run the following DISM command again and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 
The restore operation is completed succesfully. The system is healthy again.
Thanks for helping me!
 

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

Back
Top