[SOLVED] DISM Cannot Repair Component Store (last successful cumulative update is expired and no longer available on Windows Update Catalog - Server 2019)

networkperf

Contributor
Joined
Dec 2, 2022
Posts
10
Hello, I have 2019 server (Build 17763.1697) that I appear to be missing the original files to do a repair on the component store. The KB4598230 appears to be the last cumulative update applied to the system and has a few files included in it needed to complete the component store repair. The KB is expired and no longer available for download from Microsoft. I cannot update at all, nor can I repair system options (Microsoft Print to PDF), or add server roles and features, change product key, etc.. I have attempted the repair with multiple sources and searched my other 2019 servers for the files and used their directories as the source and continue to get the source not available error.

I am attaching the required files, thank you.
 

Attachments

Hi and welcome to Sysnative,

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 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

Worked like a champ!!!! I'll be donating!!

C:\Windows\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2183

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
 
Spoke too soon, still cannot update windows. Error code: (0x80073712). Going to dig a little deeper...
 
Hi,

Please provide the latest CBS log(s) in your next reply.
 
Rich (BB code):
2022-12-06 18:01:10, Error                 CSI    00000009 (F) HRESULT_FROM_WIN32(14098) #285247# 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-12-06 18:01:10, Info                  CBS    Failed to EnumerateComponentDeployment, component: amd64_microsoft-windows-s..rdenrollmentstation_31bf3856ad364e35_10.0.17763.1697_none_cb0d4b108b841297 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-12-06 18:01:10, Info                  CBS    Failed to load component owners on component: amd64_microsoft-windows-s..rdenrollmentstation_31bf3856ad364e35_0.0.0.0_none_fd90e556ba2af513, version: 10.0.17763.1697 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-12-06 18:01:10, Info                  CBS    Failed to load current component state [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-12-06 18:01:10, Info                  CBS    Failed to find or add the component family [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

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.
 
Hi,

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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log.
 

Attachments

Install made it through the initial setup, but rolled back the queued update and files during the reboot process ( failed with error - 0x80070003)
 

Attachments

  • Open Windows Explorer and browse to the C:\Windows\INF folder.
  • Right-click on the file setupapi.dev.log 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 setupapi.dev.zip in your next reply.
 
Rich (BB code):
>>>  [Install Driver Updates]
>>>  Section start 2022/12/08 07:20:42.815
      cmd: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.3641_none_56cfe33d992f2729\TiWorker.exe -Embedding
     sto: Image State        = Specialized
     sto: Image Architecture = amd64
     sto: Transaction        = CbsDriversAndPrimitives
     sto: Driver Updates     = 84
!    inf: Unable to load INF: 'C:\Windows\System32\DriverStore\FileRepository\wstorvsc.inf_amd64_2c0c5ca97b120485\wstorvsc.inf'(00000003)
!    inf: Error 3: The system cannot find the path specified.
!!!  inf: Invalid INF 'C:\Windows\System32\DriverStore\FileRepository\wstorvsc.inf_amd64_2c0c5ca97b120485\wstorvsc.inf', parsing error on line 0. Code = 1002
!!!  sto: Failed to get version info for driver update 'C:\Windows\System32\DriverStore\FileRepository\wstorvsc.inf_amd64_2c0c5ca97b120485\wstorvsc.inf'. Error = 0x00000003
<<<  Section end 2022/12/08 07:20:42.956
<<<  [Exit status: FAILURE(0x00000003)]

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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log and the setupapi.dev.log.
 

Attachments

Rich (BB code):
>>>  [Install Driver Updates]
>>>  Section start 2022/12/09 07:10:35.268
      cmd: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.3641_none_56cfe33d992f2729\TiWorker.exe -Embedding
     sto: Image State        = Specialized
     sto: Image Architecture = amd64
     sto: Transaction        = CbsDriversAndPrimitives
     sto: Driver Updates     = 84
!    inf: Unable to load INF: 'C:\Windows\System32\DriverStore\FileRepository\tsgenericusbdriver.inf_amd64_d011bdda17fe2622\tsgenericusbdriver.inf'(00000003)
!    inf: Error 3: The system cannot find the path specified.
!!!  inf: Invalid INF 'C:\Windows\System32\DriverStore\FileRepository\tsgenericusbdriver.inf_amd64_d011bdda17fe2622\tsgenericusbdriver.inf', parsing error on line 0. Code = 1002
!!!  sto: Failed to get version info for driver update 'C:\Windows\System32\DriverStore\FileRepository\tsgenericusbdriver.inf_amd64_d011bdda17fe2622\tsgenericusbdriver.inf'. Error = 0x00000003
<<<  Section end 2022/12/09 07:10:35.752
<<<  [Exit status: FAILURE(0x00000003)]

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.

Afterwards, reboot the server and attempt to update. If it fails attach a new copy of the CBS log and the setupapi.dev.log.
 

Attachments

That appears to have been the final hurdle. Updates are running as they should, and I was able to reinstall the Microsoft PDF printer again. Thank you for all the help, just dropped a donation.
 
Hi,

You're welcome and thanks for your donation to Sysnative!
Glad to hear everything is up and running now. I'll mark this thread as solved.
 

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

Back
Top