Server 2022 : SFC and DISM unable to fix corrupt files - Need help 1.5.2023

[PhishingSustainably]

I saw that someone else got help with this issue in a previous thread.
[SOLVED] - Server 2022 : SFC and DISM unable to fix corrupt files, the potential cause of Serverwide issue?

I am experiencing the exact same error logs and have tried everything DISM and SFC has to offer, also have tried mounting an ISO of 2022 and setting it as the source still no luck, would someone be able to help me fix this? The VM has been completely unstable and hosts our production ERP software... I have attached the CBS log. I know x-bluerobot was able to help fix this for the last user, hopefully they can help me as well? Thanks in advance to everyone & anyone that can help get this sorted out.

 

[Gary R]

Hi I'm Gary R,

I'm a Security Analyst, and a Windows Update Trainee, and I'd like to help you with your problems.

As a trainee, any instructions I give you must first be checked by a qualified update expert, before I post them. This will by necessity introduce some delay to any of my replies, so please be patient.

DO YOU STILL NEED HELP ?

If so, can you please do the following ....

• 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.
• 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 WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file

 

[PhishingSustainably]

Hi,

I have been banging my head against this issue and read all the forum posts about it, I appreciate any help you can give! :)

I was able to attach the file as it was only like 10MB.

 

[Gary R]

Looking over your logs and your Components file now, back ASAP.

As I said in my intro post I have to have my fixes checked before I can post them, so dependant on how many qualified helpers there are available to check my work, there's no saying exactly what ASAP might mean.

 

[Gary R]

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download SFCFix.exe and save it to your desktop.
• Download the attachment SFCFix.zip and also save it on your desktop.
• Save any work you have open, and close all programs.
• 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
• Open the file, then copy and paste its content in your next reply.

Next ...

• Restart the computer.
• Run the command SFC /SCANNOW in an elevated command prompt and report the result.
• If it fails, attach a zipped C:\Windows\Logs\CBS\CBS.log to your next reply.

 

[PhishingSustainably]

So it looks like it copied everything successfully, here is the SFCFix log file.

 

[Gary R]

Have you run SFC /Scannow yet. If not, please do, and post your new CBS.log if it fails to complete.

If it does complete, then try updating, and if you still can't update then please post your latest CBS.log

 

[Gary R]

It's 3 days since I last posted, DO YOU STILL NEED HELP ?

If I do not hear from you within 48 hours I will presume that you don't, and will close this topic.

 

[Gary R]

Due to lack of activity, THIS TOPIC IS NOW CLOSED.