Server 2008 R2 - CheckSUR and SFC can't repair

Shin

Member
Apr 9, 2025
17
Hello,

I'm experiencing serious integrity issues on a Windows Server 2008 R2 machine.

- `CheckSUR` and `sfc /scannow` both fail to repair system files.

There was a problem with the computer I used as a server, so I used various programs and modified the registry, and the problem persisted and I came here.
Some files have been recovered when 'CheckSUR' and 'sfc/scannow' are currently used. However, an error message says that a damaged file exists but cannot be recovered.
System files are damaged, so the site can be operated, but mail systems, schedule systems, and log records cannot be used.
Can I get some help?

I've attached the results of the ComponentScanner for your review.

Please take a look when you have a chance.
Let me know if you need anything else from my side.


Thanks in advance!

**Attached Logs:**
- CheckSUR.log
- CheckSUR.persist.log
- CBS.log / part
- FRST.txt
- Addition.txt
- ComponentsScanner
 

Attachments

Hi @Shin,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hello and welcome,

I'm not sure if this is repairable but we can try anyway.
Please do following.

Step 1:
Provide the Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. 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. Note: If you find that you need to reboot and are unable to because this is a server then try Option#2 below.
3. 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.
4. The file will likely be too large to upload here so please upload to Gofile or WeTransfer and just provide the link here.


Option#2 (only if you are unable to follow the previous instructions)

  • Please download the Freeware RegBak from here: Acelogix Software - Download products
    You will find it at the bottom of the page that the link brings you to.
  • Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
  • Click the New Backup button. Accept the defaults and simply click Start.
  • When it says Finished successfully, click the Close button.
  • This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
  • This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, one of which is named COMPONENTS.
  • Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
  • Now right-click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.
  • Then please upload the zip file (COMPONENTS.zip) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Gofile or WeTransfer and then just provide the link in your reply.
  • You can close any open windows you have as well as the RegBak program now.

Step 2:
Update Java
Open this web page to download the latest version and run it.
Click Install and then Install>.
Warning: You may get a choice to install additional software and/or allow to change your browser settings. Uncheck all that!
If you get a pop-up saying "Out-of-date Java versions detected.", click Uninstall>. This will remove the outdated Java versions.
More information about removing old Java versions can be found here: https://www.java.com/en/download/help/remove_olderversions.html
 
Hello.
Thank you for your reply.
Create and upload the COMPONENTS.zip file as instructed.
The capacity is small, so I think it will go up right here.
I hope there will be good results.

Should I delete the JAVA you instructed in step 2 now?
 

Attachments

Great, the COMPONENTS hive looks better as expected.
Just a question, did you ever used a program called "Windows Update Clean Tool" ?
 
I did SFC scannow and CheckSUR.
Both of them have errors in the system file, but some errors have not been recovered.
 
I didn't asked for a re-run of both SFC and CheckSur.
Please answer the question about "Windows Update Clean Tool".
 
When using the "Windows Update Organizer", the API-ms-win-core-libraryloader-11-2-0.dll file was not available, so I downloaded and ran another "Windows Update Organizer" and cleaned it except for the list below.

Visual Studio Installation Source - 31.37MB
Installer CLR Cache - 210.83MB
History Buffer Update - 427.86 MB
System Installation File Update - 318.29MB

Should I have cleaned the system installation file update as well?
What should I do now?

Since the update files have been cleaned, should I do CheckSUR again?
I'll be waiting for the next announcement.
 
I used "Windows Update Clean Tool" and cleaned up the default check items.

The list of exceptions is four below.

Visual Studio Installation Source - 31.37MB
Installer CLR Cache - 210.83MB
History Buffer Update - 427.86 MB
System Installation File Update - 318.29MB

Should I also check the exceptions and organize them?
 
I would not recommend to use so-called cleanup tools or optimizers. They may cause problems or you have to pay first to perform repairs, if needed in the first place,

Should I also check the exceptions and organize them?
No, please do following first fix only.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

Ok, next fix.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

Step 1:
  • Run the tool
    61f7aba7309a1-ComponentsScanner_Icon.png
    ComponentsScanner again to verify the fixes.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Attach that file to your next reply.

Step 2:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
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
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the file SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the
    myjIXnC.png
    SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.

Step 3:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 
There is no attachment for step 1.
I downloaded and prepared the rest of the files.
Just attach the fixlist.txt file and I can run it.
 

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

Back
Top