SFC and DISM Repair — System File Checker and Image Repair Guide
About SFC and DISM Repair
Complete guide to using SFC /scannow and DISM to repair corrupted Windows system files, fix component store corruption, and restore system health. 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 (System File Checker) scans and repairs protected Windows system files. DISM (Deployment Image Servicing and Management) repairs the Windows component store used by SFC. Run DISM first if SFC reports 'Windows Resource Protection found corrupt files but was unable to fix some of them'. SFC logs results to C:\Windows\Logs\CBS\CBS.log. DISM /RestoreHealth downloads repair sources from Windows Update. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: System files corrupted by malware, failed updates, or disk errors. SFC unable to repair because the component store itself is corrupted. Windows Update failing due to corrupted system components. Application installations replacing protected system files with incompatible versions. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Run SFC first: sfc /scannow in elevated Command Prompt (takes 10-30 minutes). If SFC finds unfixable corruption, run DISM: DISM /Online /Cleanup-Image /RestoreHealth. After DISM completes, run SFC again: sfc /scannow. Check SFC results: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > %userprofile%\Desktop\sfclog.txt. If DISM fails: try with a Windows ISO: DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim. As a last resort: perform an in-place upgrade repair using the Windows Media Creation Tool. 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.
Quick Answer
Should I run SFC or DISM first?
Run SFC first. If SFC reports it cannot fix corruption, run DISM to repair the component store, then run SFC again. DISM fixes the repair source that SFC uses.
Overview
Complete guide to using SFC /scannow and DISM to repair corrupted Windows system files, fix component store corruption, and restore system health.
Key Details
- SFC (System File Checker) scans and repairs protected Windows system files
- DISM (Deployment Image Servicing and Management) repairs the Windows component store used by SFC
- Run DISM first if SFC reports 'Windows Resource Protection found corrupt files but was unable to fix some of them'
- SFC logs results to C:\Windows\Logs\CBS\CBS.log
- DISM /RestoreHealth downloads repair sources from Windows Update
Common Causes
- System files corrupted by malware, failed updates, or disk errors
- SFC unable to repair because the component store itself is corrupted
- Windows Update failing due to corrupted system components
- Application installations replacing protected system files with incompatible versions
Steps
- 1Run SFC first: sfc /scannow in elevated Command Prompt (takes 10-30 minutes)
- 2If SFC finds unfixable corruption, run DISM: DISM /Online /Cleanup-Image /RestoreHealth
- 3After DISM completes, run SFC again: sfc /scannow
- 4Check SFC results: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > %userprofile%\Desktop\sfclog.txt
- 5If DISM fails: try with a Windows ISO: DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim
- 6As a last resort: perform an in-place upgrade repair using the Windows Media Creation Tool