Windows Resource Protection found corrupt files but was unable to fix some of them

We have already seen how the System File Checker allows users to scan for and restore corrupt Windows system files. We have also seen how to run System File Checker and more, earlier. But what if at the end of the run you see the following message?

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log.

Windows Resource Protection found corrupt files

What this message says is that although the System File Checker completed the scan and found corrupted system files, it was unable to proceed and replace them with good system files.

The Windows Resource Protection protects registry keys and folders as well as critical system files. If any changes are detected to a protected system file, the modified file is restored from a cached copy located in the Windows folder itself.

Windows Resource Protection found corrupt files but was unable to fix some of them

If you receive this message and the System File Checker is not able to do its job when you run it, here are a few things you can try.

1] Boot into Safe Mode. Open an elevated command prompt windows, type sfc/scannow and hit Enter. More on this here. Just make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp. This may help if some start-up programs are creating a problem.

2] If you wish to or need to, you may run System File Checker at Boot Time. This is one option which may help you as it will run System File Checker before Windows loads. Go here to learn how to run sfc /scannow at Boot Time in Windows 8. See if this helps.

3] Use DISM. Open an elevated command prompt and run the following command and hit Enter:

Dism /Online /Cleanup-Image /RestoreHealth

This command checks for component store corruption, records the corruption and FIXES the corruption. It may take a while though! Useful if System File Checker is not working.

4] On Windows 8, carry out a Refresh or a Reset operation. Automatic Repair is also an option you may want to consider, if you think it applies in your situation.  On Windows 7, carry out a Startup Repair or Repair Install or an In-place Upgrade as you think may best suit your situation.

To perform an In-place upgrade in Windows 7 or Windows Vista, back up your documents, close all open applications and then insert the Windows DVD in the DVD drive. In the Setup window, click Install Now. Click Go online to obtain the latest updates for installation (recommended). Type the CD key if you are prompted to do this. Next, select the operating system in Install Windows page you want to Upgrade or In-place and click Yes to accept the Microsoft Software License Terms. Next click Upgrade when asked Which type of installation do you want. Once the process is completed, restart your PC.

5] You may also want to consider this option. Open the CBS.log file and view details of the corrupted files and replace the corrupted file with a known good copy manually. Navigate to C:\Windows\Logs\CBS you will be able to see and open the SBS.log file.

sfc-failed-log

Check if it shows some errors or a message. That may give you a direction to proceed. You can get more details on how to do this manually, here at KB929833.

Hope something helps you.

These links may interest some of you:

  1. System File Checker SFC cannot repair corrupted member file
  2. System File Checker not working, will not run or could not repair
  3. Windows Resource Protection could not start the repair service
Posted by on , in Category Windows with Tags
Anand Khanse is the Admin of TheWindowsClub.com, an end-user Windows enthusiast, & a 10-year Microsoft MVP Awardee in Windows for the period 2006-16. Please read the entire post & the comments first, create a System Restore Point before making any changes to your system & be careful about any 3rd-party offers while installing freeware.