[SOLVED] SFC scannow fix

[Choco_de_luxe]

Hello everyone ! I'm posting this because everything I've tried so far didn't work. I've already done : SFC /scannow , SFC /scannow on safe boot, SFC /scannow on repair mode, SFCFix.

Here is my zipped CBS.log and SFCFix.txt

Thanks in advance for your help !

 

[Sysnative Windows Update]

Hello and welcome!

Due to the precise nature of your corruption, you will receive help from a user named writhziden. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.

 

[Choco_de_luxe]

Sure no problem !

 

[writhziden]

Hello, and welcome to Sysnative Forums. Thank you for your patience while we analyzed your files. Below are the recommended steps to begin the process for fixing the corruption found on your system.

Step 1
Run SFCFix with the included SFCFix.zip archive

WARNING! The following fix is specific to the user's system in this thread only and may be harmful to apply to another system. If you came across this thread and have a similar issue, start your own thread by following the Windows Update Forum Posting Instructions

• Download using the link to SFCFix.zip (see the next step for the link) and save it on your desktop.
• LINK -----> SFCFix.zip (Also included as an attachment at the bottom of this post)
• 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. If the file is too large to copy and paste into your reply, upload it with the logs that we request in the next steps.

Step 2
System File Checker

1. Click on the Start button/screen and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator. Allow any User Account Control box that appears.
3. When the command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, and press enter.
   
   sfc /scannow
4. Once the command finishes, if you see "Windows Resource Protection did not find any integrity violations" or "Windows Resource Protection found corrupt files and successfully repaired them" then proceed to Step 4. If you see another message from sfc /scannow, proceed to Step 3 and then Step 4.

Step 3
Export/Upload CBS log file
You only need to do this if sfc /scannow still reported corruption:

Read More:

1. On Windows 8 and Windows 10, press the Windows key, type This PC, and press Enter.
   On Windows Vista and Windows 7, click the Start button then click Computer.
2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
3. Find and double click on the Logs folder.
4. Find and double click on the CBS folder.
5. Right-click on the CBS Text Document file, and select Copy.
6. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS Text Document file appear on your Desktop called CBS.
7. Right-click on this new Text Document file, and navigate through Send to, and select Compressed (zipped) folder.
8. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created on your desktop.
9. Attach the CBS.zip file.
   Note: If your CBS.zip is larger than about 7MB then you will need to upload your file to a hosting service and provide a link instead. See “What to do if your CBS log file is too large to upload” below.

What to do if your CBS log file is too large to upload

Read More:

In some instances you will be unable to upload your CBS log file to our forum because it is too large.
To work around this problem you need to use a file sharing service to upload your attachment and then provide the link that is generated by the hosting service in your post.
Several file sharing options are listed below (they are clickable links), however you are not limited to these:

Microsoft OneDrive
Google Drive
Dropbox
ExpireBox
SendSpace
WeTransfer

Step 4
System Update Readiness Tool (SUR) Windows 7 - 64-Bit

• Download and run the following file if you do not already have Windows6.1-KB947821-v34-x64 downloaded.
• When it asks you if you wish to install, please answer Yes. Note: It could take several hours to run. Please don't cancel it.
• You will get an Installation Complete screen when it's done running.
• Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
  Please Note:: if the file is too big to upload to your next post, please upload via Sendspace and just provide the link here.
• Please do not install any updates until we have a chance to analyze your log files and to provide further instructions.

 

[Choco_de_luxe]

SFC still found corrupted parts he could not repair

 

[writhziden]

Before I tackle the last of the corruption system file checker is reporting, I need a bit more information to address the errors in your CheckSUR log:

Retrieve 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.
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 SendSpace and just provide the link here.

 

[Choco_de_luxe]

This is the COMPONENTS file

components.zip (13.95MB) - SendSpace.com

 

[writhziden]

We are now ready to fix the system file checker corruption detected (Step 1-Step 3). Then some final steps to fix the issues found in the CheckSUR log (Step 4-Step 5).


Step 1
Run SFCFix with the included SFCFix.zip archive

WARNING! The following fix is specific to the user's system in this thread only and may be harmful to apply to another system. If you came across this thread and have a similar issue, start your own thread by following the Windows Update Forum Posting Instructions

• Download using the link to SFCFix.zip (see the next step for the link) and save it on your desktop.
• LINK -----> SFCFix.zip (Also included as an attachment at the bottom of this post)
• 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. If the file is too large to copy and paste into your reply, upload it with the logs that we request in the next steps.

Step 2
System File Checker

1. Click on the Start button/screen and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator. Allow any User Account Control box that appears.
3. When the command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, and press enter.
   
   sfc /scannow
4. Once the command finishes, if you see "Windows Resource Protection did not find any integrity violations" or "Windows Resource Protection found corrupt files and successfully repaired them" then proceed to Step 4. If you see another message from sfc /scannow, proceed to Step 3 and then Step 4.

Step 3
Export/Upload CBS log file
You only need to do this if sfc /scannow still reported corruption:

Read More:

1. On Windows 8 and Windows 10, press the Windows key, type This PC, and press Enter.
   On Windows Vista and Windows 7, click the Start button then click Computer.
2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
3. Find and double click on the Logs folder.
4. Find and double click on the CBS folder.
5. Right-click on the CBS Text Document file, and select Copy.
6. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS Text Document file appear on your Desktop called CBS.
7. Right-click on this new Text Document file, and navigate through Send to, and select Compressed (zipped) folder.
8. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created on your desktop.
9. Attach the CBS.zip file.
   Note: If your CBS.zip is larger than about 7MB then you will need to upload your file to a hosting service and provide a link instead. See “What to do if your CBS log file is too large to upload” below.

What to do if your CBS log file is too large to upload

Read More:

In some instances you will be unable to upload your CBS log file to our forum because it is too large.
To work around this problem you need to use a file sharing service to upload your attachment and then provide the link that is generated by the hosting service in your post.
Several file sharing options are listed below (they are clickable links), however you are not limited to these:

Microsoft OneDrive
Google Drive
Dropbox
ExpireBox
SendSpace
WeTransfer

Step 4
Avast errors in CheckSUR.log

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
   Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attachment fixlist.txt and save it to your desktop.
3. Right-click on FRST64.exe and select "Run as administrator".
4. Press the Fix button.
5. The tool will now process fixlist.txt.
6. 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.
7. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
8. Post the logfile Fixlog.txt as attachment in your next reply.

Step 5
System Update Readiness Tool (SUR) Windows 7 - 64-Bit

• Download and run the following file if you do not already have Windows6.1-KB947821-v34-x64 downloaded.
• When it asks you if you wish to install, please answer Yes. Note: It could take several hours to run. Please don't cancel it.
• You will get an Installation Complete screen when it's done running.
• Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
  Please Note:: if the file is too big to upload to your next post, please upload via Sendspace and just provide the link here.
• Please do not install any updates until we have a chance to analyze your log files and to provide further instructions.

 

[Choco_de_luxe]

sfc /scannow found and repaired succesfully corrupted files !

 

[writhziden]

Great news regarding the system file checker! However, it appears you may have ended Step 5 prematurely. Can you run through the System Update Readiness Tool (SUR) Windows 7 - 64-Bit process again?

 

[Choco_de_luxe]

Yes my bad ! Here it is

 

[writhziden]

Everything appears to be fixed now. You can use your system normally, and if you run into any problems with Windows Update, provide the CBS log. Otherwise, it appears your initial concerns have been addressed and solved.

 

[Choco_de_luxe]

Thanks a lot for your help and your patience !

 

[writhziden]

I am happy we were able to help.