Dism - Restorehealth stuck - Error 87

Hi All,
this is a problem that exists for a while and I checked all available posts ... to no avail.

Description:
- Dism-Restorehealth gets stuck at 62.3% (Checkhealth and Scanhealth work!)
- SFC / scannow works - no problems
- Win11 is, of course, all uptodate and maintained.
- CHKDSK - no problems
- Running DISM in Recovery Environment (Troubleshoot>Advanced>Command Prompt):
none - Checkhealth / Scanhealth / Restorehealth - work ... "Cleanup Image Option Unknown" - Error 87 .. for all three.
- using the full path: C\....System32 ... etc, not working either
-I have not tried to re-install the whole DISM feature, as mentioned somewhere ... afraid of doing that ...?
if so, where to find? and how to do?

Otherwise, machine runs absolutely fine, all other checks, updates, maintenance and repairs work perfectly.
It just bothers me and it should be working!!
Shouls I just forget about it?
But - will SFC work properly if not updated with DISM?

I tried almost everything and hope a more knowledgeable person than me can help.

Thanks

How long have you waited? I had DISM hang at 62.3% for several hours, and after searching around I found that was sometimes normal. There are many posts on the issue. In my case, I left it and went to lunch and ran some errands, when I came back it has finally completed.

You can download a full Windows image of the same build as you're running and use DISM scan to extract from that downloaded Windows image. This is detailed in Option 3 of the DISM tutorial here.


One of the "last resort" options if it persists is a repair installation. That leaves all your applications intact but replaces all the Windows files. Obviously a full backup (or two) is highly recommended before you do anything like this.

Hanging at 62.3 percent is perfectly normal if there are errors to fix as that's when it will execute the repairs. Depending on the amount and severity of the of the errors will determine how long it stays at 62.3 before advancing again.

FrancoDT said:

Hanging at 62.3 percent is perfectly normal if there are errors to fix as that's when it will execute the repairs. Depending on the amount and severity of the of the errors will determine how long it stays at 62.3 before advancing again.

Click to expand...

I had this hanging problem; restarted process, again. Not sure if I then restarted the computer, I only know that when I again ran the process it completed extremely quickly, reporting that all problems had been solved. Were they? I don't know, can only hope that the singular problem with the computer is me....

Be careful of that command. My desktop PC had issues recently after running that command and I had to recover from backup.

After a day of troubleshooting, I finally found that my Windows has ended up in Windows PE state. Removing the following folder via regedit and restarting fixed all the DISM issues.
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT
```
Hope this helps someone who finds this in future.

Sualk said:

Dism-Restorehealth gets stuck at 62.3% (Checkhealth and Scanhealth work!)

Click to expand...

Same for most people, it’s not stuck. Sometimes much patience is needed. It can also seem stuck at 100%. Same rule, patience.

dism / online / cleanup-image /restorehealth can be closed and restarted to run overnight while sleeping.

The restorehealth command when running in windows RE can also be closed and restarted to run overnight while sleeping.

If you're wondering whether DISM restorehealth is actually doing anything sitting at 62.3% (or whatever number)...

Open a powershell command window as administrator, then paste in the following command:

Get-Content C:\Windows\Logs\CBS\CBS.log -tail 10 -wait

and leave this window open.

You may see various messages right away, or more likely if you've been waiting stuck for some time, you may see downloading message of the same item (e.g. 47 of 100, or similar) over and over every two or three seconds. MS download servers can be very very slow at times, it's not your PC.

As long as you're seeing a message issued with some frequency (new message or same downloading message) then DISM is working. Just let it run and hope it finishes in some minutes, hours, or even a few days on very old hardware.