> How to > Partition Manager > [Fixed] Sfc/scannow Found Corrupt Files But Was Unable to Fix

[Fixed] Sfc/scannow Found Corrupt Files But Was Unable to Fix

2017-03-20 15:12:34 Posted by Jean to Partition Manager

Summary:
Go to fix sfc/scannow error 'Windows Resource Protection found corrupt files but was unable to fix some of them' in Windows 10, 8, 7.

Error

"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. For example
C:\Windows\Logs\CBS\CBS.log"

While running System File Checker tool (sfc) and using sfc/scannow command to repair missing or corrupted system files, the error 'Windows Resource Protection found corrupt files but was unable to fix some of them' is one of the mostly received error that indicates sfc/scannow failed, and you might need to repair the corrupted files manually.

sfc/scannow found corrupt files but was unable to fix some of them

About System File Checker (sfc.exe) & sfc/scannow

In Windows operating system, System File Check (sfc.exe) is integrated with Windows Resource Protection, which protects registry keys and folders as well as critical system files. Sfc utility can be invoked via Windows Command Prompt. And, the command sfc/scannow is used to scan all protected system files, if it finds a problem, it will attempt to replace the problematic files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache. 

Troubleshooting

Ideally, running sfc/scannow command would automatically fix corrupted system files for us, not in the situation when the file is not in the dll cache or it got corrupted. At this moment, sfc/scannow will send error 'Windows Resource Protection found corrupt files but was unable to fix some of them'.

Don't be afraid. When you're caught in troubles like we mentioned, go to fix it by yourself. Here are some general troubleshooting methods that will help resolve the case promptly.

How to Fix 'Windows Resource Protection found corrupt files but was unable to fix some of them' error?

Method 1. Repair bad sectors with EaseUS Partition Master

You should know that files were corrupted largely because of the bad sectors on hard disk. When sfc/scannow was unable to fix corrupted files on bad sectors, try some other alternative methods that are more powerful.

EaseUS Partition Master is an online free partition manager that comes with a function called check partition. It enables users to check and repair hard disk partition for file system errors that perhaps result in corruption problems.

Step 1. Launch EaseUS Partition Master. Right-click the drive partition you want to check errors and select "Check partition".

select check partition to fix sfc/scannow found corrupted files but was unable to fix

Step 2. Tick the checkbox "Call Windows Chkdsk to fix errors" and click "OK".

call windows chkdsk to fix sfc/scannow found corrupted files but was unable to fix

Step 3. Let the software automatically check hard disk partition errors and repair errors for you. Click OK to finish the process.

Method 2. Run chkdsk command

If you don't prefer a third-party repair utility, you can depend on the inbuilt chkdsk command to recover corrupted files and fix them.

Step 1. Boot from Windows installation DVD.
Step 2. Select "Repair Your Computer".
Step 3. Choose your target system.
Step 4. In the recovery tool panel, choose Command Prompt.
Step 5. Run chkdsk x: /f /r (x represents your target drive)

Method 3. Run dism command

If both sfc /scannow and chkdsk x: /f /r don't work, try dism command: 

dism /Online /Cleanup-Image /RestoreHealth

Or this command if you are in repair mode of Windows DVD/USB:

Dism /Image:C:\ /Cleanup-Image /RestoreHealth