[SOLVED] SFCfix crashes

[kimenemark]

Hi gurus,

...I guess the title says a lot about the condition of my system...

Windows Server 2019 Terminal Server (VM) running on VMWare host, for which I have no control or knowledge what so ever.
Have never had any issues with Windows Update until about a week ago.
SFC has had issues for several months, but admin of host didn't give me access to original install ISO until last night. I have solved similar issues with Hyper-V VM servers and standalone servers using DISM in the past (using ISO).
I tried to solve SFC issue with DISM during the following months (whenever I had access and opportunity) but failed when running following commands (was however always able to install Windows updates):
DISM /Online /Cleanup-Image /CheckHealth ended with status ok.
DISM /Online /Cleanup-Image /ScanHealth ended with status ok and component store could be repaired.
DISM /Online /Cleanup-Image /RestoreHealth failed!
A little over 1 week ago the server crashed in the middle of installing KB5023702 (We don't run automatic update, but check and install in 14 day cycles).
Simply lost connection, was still able to ping but unable to connect using TeamViewer and RDP.
Admin of host got it running again the next morning.
Crashed again as Windows tried to reinstall update.
We decided to restore backup from before I installed the updates.
I executed the following tonight (after server had been running all day):
DISM /Online /Cleanup-Image /CheckHealth ended with status ok.
DISM /Online /Cleanup-Image /ScanHealth failed with Error 2 after 4.5% ... which indicates that the update above might not have anything to do with my current DISM issues.
I found your site and your success rate in the forums convinced me I was in the right place so I downloaded and executed SFCfix but it crashed.
I rebooted the server, paused ESET, reset SFCfix and tried running it again but it still crashed at 37%.
Must admit, I'm quite far out of my comfort zone with this issue and need a helping hand.
I have stored the information you require from tonight's session but I'm not comfortable sharing it in a public forum...
Also I can only work on the server at specific intervals... any help would be much appreciated (I'm willing to compensate/donate)?

Regards
Kim

 

[Maxstar]

Hi and welcome to Sysnative,

The requested logfiles does not contain sensitive data, except your username in the ComponentsScanner log, but you can change that with some asterisks.

 

[kimenemark]

Thanks for your reply and sorry for my ignorance
Files attached...

 

[Maxstar]

Hi,

We decided to restore backup from before I installed the updates.

Do you have previous backups too, this because the number of corruptions and the badly damaged Components hive.

Please post a copy of the (current) Components hive to look at.

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.

 

[kimenemark]

Do you have previous backups too, this because the number of corruptions and the badly damaged Components hive.

I don't manage backup as I have no control over the host... I would have to get in touch with host admin... not sure how available he is at the moment

 

[Maxstar]

I would definitely contact the admin host to ask which backups are available. I tried to repair some keys manually using regedit and another editor but it failed. And repairing this hive with an HEX editor is going to be a very tough job.

 

[kimenemark]

Sorry to have wasted your time but thanks for your help so far... will try to get an earlier backup restored.

 

[Maxstar]

You're welcome and there is no need to say sorry! I would suggest to ask if the admin host also can provide the COMPONENTS hive from different backups to check.

 

[kimenemark]

No earlier backup available
We tried to use COMPONENTS from a similar server and DISM repair stopped past 94% so some improvement but still not good.
SFCfix still crash... could you take a look now?

 

[kimenemark]

COMPONENTS too large...

COMPONENTS.ZIP

 

[Maxstar]

Hi,

Let's see if we can fix the remaining issues, here's the first fix with replacement files.

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 SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip 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. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[kimenemark]

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[===========================95.2%======================= ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

 

[Maxstar]

Here's the next batch with replacement files.

Step 1.
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.

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

DISM /online /cleanup-image /RestoreHealth

 

[kimenemark]

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[===========================95.9%======================= ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

 

[Maxstar]

And the next batch, but is too large So I've uploaded this one to WeTransfer: SFCFix.zip

Step 1.
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.

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

DISM /online /cleanup-image /RestoreHealth

 

[kimenemark]

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[===========================95.9%======================= ]
Error: 0x800f081f

The source files could not be found.

 

[Maxstar]

And the next fix: SFCFix.zip

Step 1.
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.

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

DISM /online /cleanup-image /RestoreHealth

 

[kimenemark]

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[===========================95.9%======================= ]
Error: 0x800f081f

The source files could not be found.

 

[Maxstar]

And the next fix...

Step 1.
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.

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

DISM /online /cleanup-image /RestoreHealth

 

[kimenemark]

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.3887

[===========================95.9%======================= ]
Error: 0x800f081f

The source files could not be found.