I'm running DISM /Online /Cleanup-Image /RestoreHealth on Windows 11, and the progress has been sitting at 63.4% for a long time. I keep seeing people mention that 62.4% can take a while, but I haven't found much about 63.4%, so I'm worried something went wrong. The DISM log in WindowsLogsDISM hasn't shown a new timestamp for about 100 minutes, and CPU usage is very low. Is it safe to stop the scan, or should I leave it running? I originally started this because Audacity kept crashing immediately when I tried to launch it, despite reinstalling it, running it as administrator, restarting, trying different installers, and checking my antivirus settings.
4 Answers
If it truly stops making progress, Ctrl+C in the console can sometimes get DISM past a hung step, though it also acts as a cancellation command, so use that cautiously. Afterward, reboot and run the repair command again. If DISM repeatedly fails or doesn’t resolve the original problem, an in-place Windows repair installation is another option, but make sure important files are backed up first.
DISM can appear frozen anywhere around 58%–68%, and it may take a surprisingly long time to finish. Low CPU usage doesn’t necessarily mean it has stopped working. I’d avoid interrupting it unless you have a strong reason to believe the system is completely unresponsive. You can also press Enter once to see whether the displayed progress is simply stale.
It may be downloading or processing fairly large repair files, so the progress bar can sit at one percentage for quite a while. Give it plenty of time before trying to cancel it.
I left it running, and it eventually finished after roughly five or six hours. It reported that corrupted files had been found and repaired, so I’m glad I didn’t stop it.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures