How to Fix sfc /scannow “Windows Resource Protection Found Corrupt Files but Was Unable to Fix Some of Them”

The error message “Windows Resource Protection found corrupt files but was unable to fix some of them” indicates that the System File Checker (sfc /scannow) identified damaged system binaries, drivers, or DLLs, but could not replace them because the local reference copies inside the Windows Component Store (C:\Windows\WinSxS) are also corrupted or locked by running processes. Rather than formatting your PC or reinstalling Windows, you can resolve this issue by running the Deployment Image Servicing and Management (DISM) tool to restore the component store, analyzing the sfcdetails.txt log to pinpoint broken files, and re-executing SFC in Safe Mode or via the Windows Recovery Environment (WinRE).

1. Step 1: Repair the Master Component Store via DISM

Open Command Prompt as Administrator and run the cloud health restoration sequence:

Wait for the progress counter to reach 100%. If DISM reports success, re-run sfc /scannow immediately.

2. Step 2: Extract and Filter Broken Files from CBS.log

The full CBS.log is tens of thousands of lines long. Filter out only the corrupted entries onto your desktop:

Open sfcdetails.txt to identify which specific DLL or font file failed verification.

3. Step 3: Run SFC Scannow in Safe Mode

Third-party shell extensions and antivirus software often hold file locks on system binaries in normal Windows. Boot into Safe Mode with Command Prompt and execute sfc /scannow without background process interference.

4. Step 4: Execute Offline SFC Scan in WinRE

If files remain locked, boot to a Windows installation USB or WinRE, open Command Prompt, and run an offline scan specifying your offline Windows directory:

5. Frequently Asked Questions