Additional System Center tools and components for managing infrastructure, applications, and services
DISM /Online /Cleanup-image /Restorehealth can legitimately take a long time and appear stuck at a specific percentage (such as 62.3%). The first step is to let it run to completion; this can take many minutes or longer depending on system health and performance.
If it has clearly failed or stopped progressing after a long time and exits with an error, use these steps:
- Run DISM again with a known-good source
- Open Command Prompt as administrator.
- Use a repair source instead of Windows Update, for example:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess - Replace
C:\RepairSource\Windowswith the actual path to a valid Windows installation or side-by-side store.
- If DISM completes successfully
- Run System File Checker to repair remaining issues:
sfc /scannow - Wait for verification to reach 100% and then review the result.
- Run System File Checker to repair remaining issues:
- If DISM continues to fail
- Review the DISM/CBS logs under
%SYSTEMROOT%\Logs\CBS\(for example,CBS.log) to identify specific corrupt components. - For advanced cases, copy the correct versions of corrupted files into a folder such as
C:\temp\Source, then rerun DISM with:DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\temp\Source\ /LimitAccess
- Review the DISM/CBS logs under
If DISM and SFC both complete successfully but problems persist (for example, with Windows Update), rerun Windows Update or follow the broader Windows update troubleshooting guidance.
References: