Why does SFC fail even after running DISM?

The specific corrupted file may not be present in the DISM repair source; try /Source with a matching install.wim, or move to a repair install.

Where do I find the Windows drive letter in WinRE?

Drive letters can shift in WinRE; use diskpart's list volume command or check via Notepad's Open dialog to confirm before running offline SFC.

Is it safe to manually replace a system file?

It carries real risk if versions or architecture (32/64-bit) don't match exactly; use DISM/SFC or a repair install instead when possible.

Fixing 'SFC Found Corrupt Files But Could Not Fix Some of Them'

Download now

When System File Checker can't repair everything it finds, the fix usually involves DISM, reading CBS.log for specifics, or running SFC offline from Windows Recovery Environment.

Updated August 9, 2026 · PC Utility Hub Editorial Team

Step 1: Run DISM to repair the component store

This message almost always means the local WinSxS component store SFC pulls replacement files from is itself damaged. Repair it first:

DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Step 2: Read CBS.log to find the specific file

SFC's detailed log lives at C:\Windows\Logs\CBS\CBS.log. Extract the relevant lines to a readable file:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > %userprofile%\Desktop\sfcdetails.txt

Reading the log output

Look for lines containing "Cannot repair member file" — they name the exact file and its expected hash. Common offenders are drivers or optional-component DLLs added by third-party software. Once you know the file name, you can sometimes replace it manually by copying a known-good copy from another identical Windows installation, though this is an advanced, risky step.

Manually replacing system files by hand can make things worse if versions don't match exactly. Prefer DISM/SFC or a repair install over manual file copying.

Step 3: Run SFC offline from WinRE

If Windows won't boot, or SFC can't run in normal mode, boot into Windows Recovery Environment and run SFC against the offline OS partition.

1Boot to WinRE (hold Shift and click Restart, or boot from Windows installation media and choose Repair your computer).
2Go to Troubleshoot > Advanced options > Command Prompt.
3Identify the Windows drive letter — in WinRE it's often D: or E:, not C:. Use notepad to open File Explorer's Save dialog and check drive letters, or run diskpart > list volume.
4Run: sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows (replace D: with your actual Windows drive letter).
5Restart normally once the scan finishes.

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Step 4: When nothing repairs it

If DISM, SFC, and offline SFC all fail, run chkdsk to rule out a failing disk, then perform an in-place repair install using media from the Media Creation Tool. This replaces all Windows system files while keeping apps and personal files intact.

Frequently asked questions

Why does SFC fail even after running DISM?: The specific corrupted file may not be present in the DISM repair source; try /Source with a matching install.wim, or move to a repair install.
Where do I find the Windows drive letter in WinRE?: Drive letters can shift in WinRE; use diskpart's list volume command or check via Notepad's Open dialog to confirm before running offline SFC.
Is it safe to manually replace a system file?: It carries real risk if versions or architecture (32/64-bit) don't match exactly; use DISM/SFC or a repair install instead when possible.