Repository navigation
System Health
System Health groups the core Windows repair tools: SFC, DISM, CHKDSK, and a guided Quick Fix that runs them in sequence. Most actions open a separate elevated console and can take a long time.

System Health. Each button launches a different Windows repair path; Quick Fix combines SFC, DISM, and temporary-file cleanup.
- Save your work. SFC and DISM can run for many minutes, and CHKDSK can run for hours.
- Connect to power on a laptop. A repair interrupted by shutdown can leave the system in a worse state.
- Make sure you have a current backup and, where possible, a restore point.
- Do not close the repair console until it reports completion. Closing it can terminate the operation.
- These tools repair Windows components. They do not fix failing hardware, and CHKDSK
/rcannot repair a physically failing disk.
Quick Fix runs a fixed four-step sequence in one elevated console:
SFC /SCANNOWDISM /Online /Cleanup-Image /CheckHealthDISM /Online /Cleanup-Image /RestoreHealth- Temporary-file cleanup of the user temp folder and
C:\Windows\Temp
WMT asks for confirmation before starting. The console prints each step, the exit codes for SFC and both DISM stages, the number of temp items removed, and the approximate space reclaimed. It then waits briefly and closes.
Use Quick Fix when you want a single guided repair and do not need to inspect each stage interactively. If you need to read the full output, use the individual buttons instead.
SFC Scan opens an elevated PowerShell window and runs:
sfc /scannow
System File Checker scans protected Windows files and replaces corrupted copies from the component store. The console stays open with Press Enter to close so you can read the result.
Typical outcomes:
- No integrity violations found.
- Corruption was found and successfully repaired.
- Corruption was found but some files could not be repaired. In that case, run DISM RestoreHealth and then repeat SFC.
DISM Check runs a read-only component-store health check in the background:
dism /online /English /cleanup-image /checkhealth
WMT waits up to about two minutes and interprets the output:
| DISM result | WMT message |
|---|---|
| No component store corruption detected | DISM Check: no corruption detected. |
| The component store is repairable | DISM Check: corruption detected (repairable). WMT offers to run RestoreHealth |
| The component store cannot be repaired | Reports that corruption was detected but cannot be repaired |
| Output cannot be interpreted | Shows the raw output for review |
If repair is needed, WMT asks whether to start DISM RestoreHealth immediately.
DISM Restore opens an elevated PowerShell window and runs:
dism /online /cleanup-image /restorehealth
This repairs the Windows component store using Windows Update or a configured repair source. It can take a long time and may download files. Run SFC again afterward if SFC previously reported unrepaired files.
CHKDSK asks for confirmation and then opens a live console that checks every local file-system drive:
chkdsk <drive>: /f /r
- The system drive is checked with
/f /r; if Windows cannot lock it, the console answers the schedule prompt withYso the repair runs at the next reboot. - Other drives use
/f /r /x, which dismounts the volume first. - The console prints per-drive results and a summary of completed and warned drives.
CHKDSK /r scans for bad sectors and can take hours on large or slow disks. Do not run it unnecessarily on a healthy SSD; use the drive's own health tools and My Device for a quick status check.
| Tool | Scope | Typical use |
|---|---|---|
| SFC | Protected Windows system files | Missing or corrupted system files |
| DISM CheckHealth | Component store metadata | Quick read-only health check |
| DISM RestoreHealth | Component store contents | Repair the source SFC uses |
| CHKDSK | File system and disk sectors | File-system errors, bad sectors, dirty volumes |
| Quick Fix | SFC, DISM, temp cleanup | One-pass guided repair |
- SFC and DISM report their own exit codes in the console. A non-zero code does not always mean the repair failed; read the message above it.
- WMT writes a short summary to the activity log when a tool is launched or when DISM Check completes.
- Repair consoles are separate processes. Their detailed output is not copied into the WMT activity log.
- For persistent diagnostics, enable Debug Logs in Support & Credits.