It means it's very busy fixing things for you, patience is a virtue. It stopping at 62% is something that has been discussed in great depth.
www.tenforums.com
www.tenforums.com
DISM /Online /Add-Capability /CapabilityName:WMIC~~~~
cmd /c powershell -c "gc %windir%\Logs\CBS\CBS.log -tail 10 -wait"gc $env:windir\Logs\CBS\CBS.log -tail 10 -waitgc is an alias for the Get-Content Cmdlet.) All the command does is keep showing the last 10 lines of the log file until you press Ctrl + C or you close the console or close the Windows Terminal (or tab).
When things are damaged it is not strange that a repair can take a long time. To you DISM seems to be stuck but I bet in reality your system is quite busy in the background. It all depends how fast your machine is.
It can sit for some time at certain points. The hang at 62.3% is well known and can last for hours before you should panic. I'm guessing that Internet speed and server load can make this a very long wait, depending on the size of the files DISM has to fetch from MSC.Another input:
Someone else had it stuck at that percentage, and they let it sit there for a few hours, and it completes:
Dism /Online /Cleanup-Image /restoreHealth stuck at 62.3% - Microsoft Q&A
Following an issue I was running the above command. I can see in the CBS.log file it is stuck here: 2025-02-25 10:29:10, Info CBS FC: FCAcquirerWUClient: WULib DownloadProgress: [75 / 100] Its been like this for nearly an hourlearn.microsoft.com
Also, someone says pressing Enter makes it continue in the post afterwards, you can also try pressing Enter when it's stuck and see what happens.
That's not what he meant. The system fell asleep is more likely and woke up again after pressing Enter. It's important not to interrupt this proces. The chance is very high that it must start again at the beginning. Pressing Enter while the system is busy will do nothing or not make it go any faster. Can take in some cases more than 1 hour depending how fast the speed of the system and internet connections is. Seen cases where it took several hours. Patience is all you have to have.... It will fix it in the end in most cases.Another input:
Someone else had it stuck at that percentage, and they let it sit there for a few hours, and it completes:
Dism /Online /Cleanup-Image /restoreHealth stuck at 62.3% - Microsoft Q&A
Following an issue I was running the above command. I can see in the CBS.log file it is stuck here: 2025-02-25 10:29:10, Info CBS FC: FCAcquirerWUClient: WULib DownloadProgress: [75 / 100] Its been like this for nearly an hourlearn.microsoft.com
Also, someone says pressing Enter makes it continue in the post afterwards, you can also try pressing Enter when it's stuck and see what happens.
Remember; When using SFC or DISM always open a CMD-box as admin.
> sfc /scannow
You must be an administrator running a console session in order to use the sfc utility.
> dism /online /cleanup-image /restorehealth
Error: 740
Elevated permissions are required to run DISM.
Use an elevated command prompt to complete these tasks.
It was not 'stuck', it was just busy. This is normal behaviour. The wait is down to the speed of your system.
?? Just as what I said.... "When using SFC or DISM always open a CMD-box as admin." So?...
Or. Just open a CMD-box as admin and execute the following commands; (at the default location C:\Windows\System32)
Dism /Online /Cleanup-Image /RestoreHealth
SFC /scannow
