[SOLVED] Unable to Run SFC Scan/DISM RestoreHealth - Windows Server 2022

[JamesDean]

Hi Everyone,

I'd appreciate any help you guys might be able to provide. I've got a Windows Server 2022 VM that has been failing updates for a bit. I went to attempt to fix this and dug into what appears to be a corrupt or missing component. SFC/DISM are both uncooperative.

I'd tried to rebuild the component store/dism using the a number of helpful guides I found online however just about all of them fail with the component store has been corrupted.



I also attempted to use the original ISO as source material:



In looking at the dism.log, it always seems to come back to this error:

024-06-26 13:43:22, Info CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.20348.2522_none_b1c04a98f9919dff\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2024-06-26 13:43:22, Info CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.20348.2522_none_b1c04a98f9919dff\wcp.dll' : got STATUS_SUCCESS

In the meantime, I am going to try borrowing the SxS and Servicing folder from a healthy server and doing the restore health command as outlined here.

https://www.reddit.com/r/sysadmin/comments/9znpac/sxs_component_store_corrupt

Appreciate any pointers or help you guys can provide. This site has been and is an outstanding resource for all these fun problems!

--Kris

 

[Maxstar]

Hi and welcome to Sysnative,

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.

 

[JamesDean]

Hi Maxstar! Thanks! Here is the file.

 

[Maxstar]

Hi,

Step 1. Download

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.

• 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. Reboot the server and download

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.

 

[JamesDean]

Thank you kindly! Here are the results.

 

[Maxstar]

Please run the following DISM command again and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[JamesDean]

Thanks Maxstar! That fixed it.

So it boiled down to a bad component store and entry in the registry? The fix was replace the entry in the registry and then issue the restore health command? If I am following everything.

Thanks Again!

 

[Maxstar]

Hi,

Yes, that was the main issue. But are there any remaining issues or is everything okay now?

 

[JamesDean]

Yes everything is working great now. Just wanted to make sure I had some understanding! Appreciate your time and assistance!

 

[Maxstar]

Hi,

You're welcome. Glad to hear the issue has been resolved...