How to Use dism /online /cleanup-image /restorehealth on Windows 11 to Repair Your System
Crashing apps, failed updates and slow performance can have many causes, including damaged Windows components. DISM.exe /Online /Cleanup-Image /RestoreHealth checks and repairs the running Windows installation's component store using an available repair source. It is a useful targeted troubleshooting step, not a universal fix for hardware, drivers, malware or application problems. It is not intended to remove personal files, but keep important data backed up before broader recovery work.
What does dism /online /cleanup-image /restorehealth do and why should I use it?
The dism /online /cleanup-image /restorehealth command checks the integrity of Windows 11's system image—the set of core files Windows relies on to operate and update. If some of these files are missing or damaged, Windows may behave unpredictably or fail to update correctly. This command connects to Windows Update or a specified local source to repair or replace those corrupted files, restoring the system image to a healthy state. Using it can prevent many system stability issues that stem from corrupted system components. Because Windows 11 depends heavily on this system image for smooth operation and updates, repairing it can fix problems that simpler tools might not address.
How do I safely run dism /online /cleanup-image /restorehealth on Windows 11?
Open Command Prompt or Terminal with authorized administrator rights, then run DISM.exe /Online /Cleanup-Image /RestoreHealth. /Online means the currently running Windows installation, not “connected to the internet.” Use it from the Windows installation you intend to repair; repairing an offline installation from recovery uses a different target. Let the operation finish and record its final result or error. Windows Update is the usual default repair source, so network or organizational policy can matter. A compatible local repair source is another option. Keep the PC powered and avoid interrupting a progressing operation.
What are common errors when running this command and how can I fix them?
Record the exact error and consult the DISM log, normally at C:\Windows\Logs\DISM\dism.log. Missing-source errors do not prove a simple internet outage: the required component files may be unavailable, incompatible or blocked by policy. A local source must match the target's requirements, including applicable architecture, release, components and language resources; an older patch level can lack files needed by a newer target. For a WIM source, use the correct image index for your installation rather than assuming :1. Some media contain install.esd instead of install.wim, so the literal WIM example will not apply unchanged. /LimitAccess prevents fallback to Windows Update; it is optional and useful only when the selected source can supply what is needed. Do not reset update components routinely without evidence that this is the relevant fault.
How is dism /online /cleanup-image /restorehealth different from sfc /scannow?
DISM /RestoreHealth repairs the Windows component store used for servicing and repair. SFC /scannow checks protected Windows system files and can restore damaged copies using the repair resources. SFC is not limited to files currently in use and is not guaranteed to be quick. Microsoft's standard repair sequence runs DISM successfully, then SFC. If either reports an unresolved issue, preserve the exact output and investigate rather than assuming repeated scans will fix every underlying cause.
What should I do after the command finishes running?
Read the final output. After DISM completes successfully, Microsoft's standard sequence is to run sfc /scannow; a restart between them is not an automatic requirement. Restart if instructed or needed to finish servicing, then test the original problem. If repairs fail, investigate the error and source before escalating. A supported repair installation can preserve apps and files when its requirements and retention choices permit, while Reset this PC removes apps and can also remove personal data depending on the option. Back up and read the chosen recovery procedure before proceeding.
Conclusion
Use an elevated DISM /RestoreHealth operation when Windows component corruption is a plausible cause, record the result and follow a successful repair with SFC. Check a local source's compatibility and WIM index before using it; no single ISO path works for every PC. Test whether the original symptom changes and seek targeted diagnosis if it does not. Successful component repair does not rule out unrelated hardware, driver or application faults.
Frequently Asked Questions
Can I run dism /online /cleanup-image /restorehealth while other programs are open?
Yes, you can run it with other programs open, but it’s best to close unnecessary applications to reduce the chance of conflicts and help the process finish smoothly.
How long does the dism /online /cleanup-image /restorehealth command take on Windows 11?
There is no fixed completion time. Storage performance, the component-store condition, servicing activity and source availability all affect it, and the progress indicator can pause. Do not assume a normal operation failed solely because 30 minutes elapsed. Record an actual error or consult servicing logs when diagnosing a genuine stall.
Do I need an internet connection to use dism /online /cleanup-image /restorehealth?
/Online targets running Windows and does not inherently require internet access. Network access is needed when the selected repair source is Windows Update or a network location. A suitable local source can repair without it; /LimitAccess explicitly stops Windows Update fallback. The source must actually contain the required compatible files.
What does it mean if dism reports no corruption found?
It means the component-store check did not report corruption within that operation's scope. It does not prove every system file, driver, application or hardware component is fault-free. If the symptom persists, use the relevant diagnostic steps rather than treating the report as a complete health certificate.
Should I run sfc /scannow before or after DISM?
You should run DISM first to repair the system image, then run sfc /scannow to fix individual system files. This order is generally more effective for resolving system corruption.