Windows SFC /scannow Found Corrupt Files But Unable to Fix

When sfc /scannow reports 'Windows Resource Protection found corrupt files but was unable to fix some of them,' additional repair steps are needed. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: 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. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: 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. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Run DISM /Online /Cleanup-Image /RestoreHealth first to repair the component store. If DISM fails, use installation media: DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim. After DISM succeeds, run sfc /scannow again. Check CBS.log for specific failed files: findstr /c:'[SR] Cannot' C:\Windows\Logs\CBS\CBS.log. As last resort, run an in-place upgrade (repair install) from Windows ISO. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Windows Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.