Command Reference
DISM /Online /Cleanup-Image /ScanHealth
Gnojo Analysis
Understanding DISM /Online /Cleanup-Image /ScanHealth
What This Command Does
Checks whether the running Windows image has repairable component-store corruption.
When to Use It
Use DISM /Online /Cleanup-Image /ScanHealth when troubleshooting system integrity issues and you need information that can help narrow down the cause.
What to Look For
No component store corruption detected
Windows did not detect component-store corruption.
The component store is repairable
Corruption was detected and a separately approved repair may be appropriate.
The component store cannot be repaired
Escalation or recovery media may be required.
Permissions
Run this command from an elevated terminal with administrator access.
Risk and impact
ScanHealth is diagnostic but can take several minutes and writes servicing logs and temporary working data. Do not close the terminal while it is running.
Typical Next Steps
Continue troubleshooting with one of these related commands:
Summary
Checks whether the running Windows image has repairable component-store corruption.
Syntax
DISM /Online /Cleanup-Image /ScanHealth
Examples
DISM /Online /Cleanup-Image /ScanHealth
Scans the active Windows image without performing a component-store repair.
Permissions
Administrator required: Yes
Run from Command Prompt opened as administrator and follow organizational support policy.
Risk and Impact
Risk level: Low
Changes the system: No
ScanHealth is diagnostic but can take several minutes and writes servicing logs and temporary working data. Do not close the terminal while it is running.
Supported Platforms
Important Output Fields
No component store corruption detected
Windows did not detect component-store corruption.
The component store is repairable
Corruption was detected and a separately approved repair may be appropriate.
The component store cannot be repaired
Escalation or recovery media may be required.
Common Errors
Error: 740
DISM requires an elevated terminal.
The source files could not be found
Windows could not access required servicing content.
Related Commands
Continue troubleshooting with related diagnostic commands.
Official References
Repair-WindowsImage
Microsoft Learn · Official Documentation