System file corruption detected but 'unable to fix all' by SFC

Symptoms

• Command Prompt output after sfc /scannow specifically says it found corrupt files but could not fix some
• A log file path is mentioned (CBS.log) for details
• PC may still show related instability or errors after running sfc
• sfc /scannow may have been run multiple times with the same partial result

Likely causes

• CommonSFC's local repair source is itself damagedSFC needs a healthy copy of files to repair from, and if that's also corrupted, it can't complete the fix.
• CommonDeeper corruption than SFC alone is designed to handleSome Windows component damage needs DISM's more thorough repair process first.
• PossibleNo internet access for DISM to pull a fresh repair sourceDISM's repair often needs to download replacement files from Windows Update.
• PossibleDamage to a file currently in use that can't be replaced liveSome files can only be replaced during a restart or from outside the running OS.
• Less commonFailing drive causing new corruption as fast as it's repairedOn a failing drive, repairs may not hold because damage keeps recurring.

What to do

1. Run 'DISM /Online /Cleanup-Image /RestoreHealth' in an administrator Command Prompt, which can repair the underlying repair source SFC relies on; this requires an internet connection.
2. After DISM completes successfully, run 'sfc /scannow' again, since it often succeeds fully once DISM has repaired the component store.
3. Check 'C:\Windows\Logs\CBS\CBS.log' for specific details on which files couldn't be fixed, searching for '[SR]' entries that indicate System Resource (SFC) results.
4. If DISM itself fails due to no internet or a restricted network, you can specify a Windows installation image as an alternate source using the '/Source' option with DISM, pointing to a mounted ISO of a matching Windows version.
5. Restart the computer and run sfc /scannow once more after a fresh boot, since some fixes only fully apply after a restart.
6. If corruption keeps recurring even after successful DISM and SFC runs, run 'chkdsk C: /f /r' to rule out a failing drive as the root cause.
7. If corruption persists despite all of this, back up files and consider an in-place repair install (reinstalling Windows over itself, keeping files and programs) as a more thorough fix.

When to call a pro

If DISM and SFC together still can't fully repair the corruption, or the CBS.log points to files that keep failing, a technician can perform an in-place repair install or investigate a failing drive.

Safety