How to Fix ‘Windows Resource Protection Found Corrupt Files but Was Unable to Fix Some of Them’

Running the System File Checker command sfc /scannow in Windows 11 to repair system crashes or sluggish performance only to receive the terminal verdict: “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” leaves users stranded. The System File Checker operates by comparing system binaries against cached, pristine copies located in the Windows Component Store (the WinSxS folder). When the local Component Store itself suffers from corrupted hard links, missing manifest hashes, or disk sector degradation, SFC has no healthy source files from which to restore damaged system libraries. This guide provides structured, field-tested procedures using DISM, Safe Mode, and CBS log parsing to restore system integrity on Windows 11.

Why Does SFC Fail to Repair Corrupted System Files?

Windows Resource Protection (WRP) protects essential system files, folders, and registry keys. When SFC reports that it cannot repair detected corruption, it is typically due to:

  • Component Store (WinSxS) Corruption: The local repository of backup components has become corrupted, preventing SFC from retrieving clean replacement binaries.
  • Active System File Locks: The corrupted files are currently loaded into memory and locked by running background third-party services or antivirus daemons.
  • Failed Windows Updates: Incomplete cumulative updates leaving pending file transactions in an uncommitted state.
  • Hard Drive or SSD File System Errors: Bad sectors or NTFS metadata inconsistencies corrupting system file payloads during write operations.

Method 1: Repair the Component Store Using DISM RestoreHealth

The Deployment Image Servicing and Management (DISM) tool downloads fresh, unmodified component packages directly from Microsoft Windows Update servers, repairing the WinSxS store so that SFC can complete its repairs.

  1. Press the Windows Key, type cmd, right-click Command Prompt, and select Run as administrator.
  2. Ensure your computer has an active, stable internet connection.
  3. Execute the following command to repair the local Component Store:
    DISM /Online /Cleanup-Image /RestoreHealth
  4. Wait patiently for the verification progress bar to reach 100% (this process typically takes 10 to 20 minutes depending on connection and SSD speeds).
  5. Once DISM reports “The restore operation completed successfully”, immediately run the System File Checker again:
    sfc /scannow
  6. SFC will now draw upon the freshly repaired WinSxS store to successfully repair all remaining damaged files.

Method 2: Use DISM with an Offline Windows 11 ISO Source

If your PC lacks an internet connection or DISM fails with error codes like 0x800f081f (The source files could not be found), you can supply a clean Windows 11 installation ISO as an offline repair source.

  1. Download the official Windows 11 ISO from Microsoft’s website.
  2. Double-click the ISO file to mount it as a virtual DVD drive (note the assigned drive letter, for example E:).
  3. Open an elevated Command Prompt window.
  4. Execute DISM pointing directly to the mounted image source file:
    DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim:1 /LimitAccess
    (Replace E: with your actual mounted drive letter, and use install.esd if your ISO contains an ESD file instead of WIM).
  5. After DISM completes, run sfc /scannow to finalise repairs.

Method 3: Run SFC and DISM in Windows Safe Mode

Running repair scans in Safe Mode ensures that third-party antivirus filters, graphic drivers, and background shell extensions are completely unloaded, releasing active file locks.

  1. Press Windows Key + I to open Settings.
  2. Navigate to System > Recovery.
  3. Next to Advanced startup, click Restart now.
  4. Upon reboot, choose Troubleshoot > Advanced options > Startup Settings > Restart.
  5. Press 4 or F4 to select Enable Safe Mode.
  6. Once logged in to Safe Mode, launch an elevated Command Prompt and execute sfc /scannow.

Method 4: Parse the CBS.log to Identify Specific Unrepaired Files

If you need to know exactly which files are failing repair, extracting the SFC entries from the CBS log pinpoints the specific files.

  1. In an administrative Command Prompt, run the following filter command:
    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"
  2. Navigate to your Desktop and open the newly created sfcdetails.txt file in Notepad.
  3. Review the entries tagged with [SR] Cannot repair member file. This reveals the precise filename, directory path, and reason for the validation failure.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.