Fix DISM stuck at 62.3%

Best place to run it

Elevated Command Prompt is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.

Fast repair workflow

1. Start from the exact symptom on this page: DISM stays on 62.3 percent for a long period
2. Run the primary repair line exactly as shown: DISM /Online /Cleanup-Image /RestoreHealth DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /LimitAccess.
3. This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
4. Reboot if the servicing stack or protected files were changed, then retry the original Windows action.
5. Escalate only after reading the output, usually toward CBS.log, DISM source repair, or Windows Update-specific repair.

Copyable wrapper script

Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.

Verification commands after the repair

These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.

What problem this command is trying to solve

This page focuses on RestoreHealth runs that appear stuck at the same percentage for an unusually long time.

• DISM stays on 62.3 percent for a long period.
• The command window shows no visible progress change.
• Users often cancel too early and make the repair path longer.

How the command works

The first command is the normal repair attempt. The second is the fallback when online repair sources are the reason progress never moves.

When it makes sense to run it

Use the fallback only after giving the normal run enough time and confirming it is not simply a slow repair stage.

Before you run this command

• Open an elevated Command Prompt or PowerShell window before running DISM /Online /Cleanup-Image /RestoreHealth DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /LimitAccess.
• Confirm that the symptom really matches this guide, especially if you are seeing signs such as: dism stays on 62.3 percent for a long period.
• Keep any exact DISM, SFC, CBS, or Windows Update error output because those details matter in the next step.

What result to expect

After running DISM /Online /Cleanup-Image /RestoreHealth DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /LimitAccess, compare the result against the symptom that brought you here. The most useful checkpoint is whether dism stays on 62.3 percent for a long period becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.

How to verify that it worked

The best verification step after DISM /Online /Cleanup-Image /RestoreHealth DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /LimitAccess is to repeat the action that previously triggered the problem. If the command window shows no visible progress change still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.

Why administrator rights matter here

This command changes system integrity and component corruption. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.

Before you run it

Do not interrupt DISM just because the percentage stops moving for several minutes. Watch actual system activity before deciding it is truly stuck.

When this is probably the wrong fix

This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.

What to do if it does not help

If DISM /Online /Cleanup-Image /RestoreHealth DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /LimitAccess does not improve dism stays on 62.3 percent for a long period, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about system integrity and component corruption.