Windows SFC /scannow Found Corrupt Files But Unable to Fix

Overview

When sfc /scannow reports 'Windows Resource Protection found corrupt files but was unable to fix some of them,' additional repair steps are needed.

Key Details

• SFC found corruption but cannot replace the files from its cache
• The component store (WinSxS) itself may be corrupted
• Log file at C:\Windows\Logs\CBS\CBS.log shows which files failed
• DISM tool can repair the component store that SFC relies on
• May need Windows installation media as a repair source

Common Causes

• Component store (WinSxS folder) corruption
• Windows Update cache containing corrupted source files
• Previous failed repairs leaving inconsistent state
• Disk errors corrupting system files and their backups
• Third-party system tweakers modifying protected files

Steps

1. 1Run DISM /Online /Cleanup-Image /RestoreHealth first to repair the component store
2. 2If DISM fails, use installation media: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim
3. 3After DISM succeeds, run sfc /scannow again
4. 4Check CBS.log for specific failed files: findstr /c:'[SR] Cannot' C:\Windows\Logs\CBS\CBS.log
5. 5As last resort, run an in-place upgrade (repair install) from Windows ISO

Tags

More in System Errors

Frequently Asked Questions