System File Checker (SFC) and Deployment Image Servicing and Management (DISM) are the absolute cornerstones of Windows OS repair. While heavily recommended, 90% of users execute them incorrectly or in the wrong sequence, leading to failed repairs.
1. The OS Image Architecture
Windows relies on a local hidden store called the `WinSxS` (Windows Side-by-Side) folder. This acts as a backup repository containing pristine copies of every DLL, SYS, and EXE file required by the OS. When a file in System32 becomes corrupted by malware or a bad sector, Windows needs to replace it.
2. Why DISM Must Always Precede SFC
The most common mistake in IT troubleshooting is running sfc /scannow first. This is architecturally backward.
SFC (System File Checker) repairs the active OS files by copying clean versions from the WinSxS component store. However, if the WinSxS component store itself is corrupted, SFC will fail with the message: "Windows Resource Protection found corrupt files but was unable to fix some of them."
DISM repairs the component store. SFC repairs the OS. Therefore, always repair the component store before repairing the OS.
3. The Correct DISM Execution Sequence
Open an Elevated Command Prompt (Run as Administrator) and execute the following in order:
Step A: Checking Component Store Health
DISM /Online /Cleanup-Image /CheckHealthThis command performs a rapid check (takes seconds) to see if corruption flags have been set in the registry. It does not scan the files.
Step B: Scanning Component Store
DISM /Online /Cleanup-Image /ScanHealthThis performs a deep topological scan of the component store. It takes 10-15 minutes but makes no repairs.
Step C: Restoring Component Store Health
DISM /Online /Cleanup-Image /RestoreHealthThis is the critical repair command. By default, it reaches out to Windows Update (online) to download pristine replacement files for any corrupted items found in the WinSxS folder.
4. Advanced DISM: Offline Repair (No Internet)
If Windows Update is broken or the machine is offline, DISM will fail. You must point DISM to an offline Windows 10/11 ISO file (specifically the install.wim or install.esd file inside the ISO's `sources` folder).
DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess(Replace `D:` with your mounted ISO drive letter).
5. Executing the Final SFC Sweep
Only after DISM reports "The restore operation completed successfully" should you run SFC.
sfc /scannowSFC will now draw upon a perfectly pristine WinSxS store to repair your active System32 files. If SFC fails after a successful DISM, check the CBS log (C:\Windows\Logs\CBS\CBS.log) to identify locked files that may require a Safe Mode repair.