How to fix DISM RestoreHealth stuck at 62.3% in Windows?

DISM /Online /Cleanup-Image /RestoreHealth often holds at 62.3 % for many minutes, sometimes hours, while it is still repairing Windows in the background. Microsoft's documentation does not explain that number, but the CBS.log file shows whether the work goes on. Check the log first and stop the run only when the log has gone silent.

Facts checked on 14 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What DISM RestoreHealth stuck at 62.3% means

DISM (Deployment Image Servicing and Management) repairs the component store, the folder C:\Windows\WinSxS and its records, from which Windows rebuilds its own system files. Microsoft's reference describes /RestoreHealth in one line: it "scans the image for component store corruption, and then performs repair operations automatically. This operation will take several minutes."

While it works, DISM draws a text bar such as [=====62.3%==== ]. The bar does not move evenly. It can stay on one figure while a long step runs underneath. Most readers see exactly 62.3 %, others 62 %, 63 % or 64 %. None of these figures is an error code, and none tells you what is damaged.

Microsoft's documentation says nothing about the 62.3 % mark, and we did not find a Microsoft statement that explains it. What the documentation does give is the log: DISM "creates a log file (%windir%\Logs\CBS\CBS.log) that captures any issues that the tool found or fixed". That file, not the bar, tells you whether the run is alive.

Why DISM stops at 62.3%, from most to least common

• Most often: it is not stuck. The repair stage runs without moving the bar. Users report 20 minutes on a fast PC and several hours on a slow one. CBS.log keeps getting new lines. Fix 2.
• Often: the window is paused. In the classic console window a single mouse click starts a text selection, and while it is active the program cannot print its next line. Users report that pressing a key made DISM jump to 100 %. Fix 1.
• Less often: DISM waits for Windows Update. RestoreHealth downloads clean copies from Windows Update by default. A slow connection, a blocked update service or a company update policy makes it wait, then end with 0x800f0906 or 0x800f081f. Fixes 4 and 5.
• Rarely: the store is too damaged. When hundreds of manifests are missing, a volunteer moderator on Microsoft Q&A advised a repair install instead of sourcing them one by one. Fix 6.
• Rarely: the drive is failing. If the whole PC crawls and the disk shows 100 % activity for hours, the drive itself can be the bottleneck. See the last section.

How to tell a working DISM run from a stuck one

You need three checks, and none of them touches the running repair. Do them in this order: the title bar of the DISM window, the end of CBS.log, and the Windows Modules Installer Worker process in Task Manager. That worker is the servicing process that DISM hands the repair to.

One user on Microsoft Q&A who measured it reports that the run is really over when CBS.log prints Ending TrustedInstaller finalization. After that the DISM window shows its final message and the worker process closes by itself.

How to fix DISM RestoreHealth stuck at 62.3%

Fixes 1 and 2 cost nothing and solve most cases: they unpause the window and show you that the repair is still running. Fix 3 stops a run that really froze. Fixes 4 and 5 give DISM a source it can actually reach. Fix 6 is the last step when the store cannot be repaired.

Fix 1. Check that a mouse click has not paused the DISM window

1 minuteNo riskYou clicked into the DISM window, or its title bar begins with Select.

The classic console window has QuickEdit Mode, which Microsoft describes as letting you "use the mouse to select and edit text". While a selection is active the window stops taking new output, so DISM waits until you clear it.

1. Look at the title bar of the DISM window. If it begins with Select, or part of the text is highlighted, the window is paused.
2. Click once on the title bar of that window so it has the keyboard focus. Do not click inside the black area again.
3. Press Esc once to cancel the selection. Select disappears from the title.
4. Watch the bar for a minute. If DISM had finished its work during the pause, it may jump straight to 100 % and print its result.

We could not find a Microsoft page that documents this pause for DISM. It is reported many times on Microsoft Q&A, where users say that clicking into the window and pressing a key made DISM continue. We could not confirm whether Windows Terminal, the default on Windows 11, pauses in the same way. If you see highlighted text there, press Esc anyway, then go on to Fix 2.

Fix 2. Watch CBS.log and Task Manager, then let DISM finish

5 minutes, then the waitNo riskThe bar sits at 62.3 % and you want to know whether DISM is still working.

Microsoft documents CBS.log as the file where DISM records what it found and fixed. Reading its last lines in a second window shows each step as it happens, so you can see the repair go on while the bar stands still.

1. Leave the DISM window open. Right-click Start and select Terminal (Admin) on Windows 11, or Windows PowerShell (Admin) on Windows 10. Select Yes.
2. In the new window, show the last 10 lines of CBS.log and keep following it.

   Get-Content C:\Windows\Logs\CBS\CBS.log -Tail 10 -Wait

3. Watch the time stamps at the start of each line for a few minutes. New lines, even one every few minutes, mean DISM is working.
4. Press Ctrl + Shift + Esc to open Task Manager, select Processes and find Windows Modules Installer Worker. CPU or disk use there means the repair is active.
5. Keep the PC on power and stop it from sleeping until DISM prints its final line.
6. When you are done watching, press Ctrl + C in the PowerShell window. This stops only the log viewer, not DISM.

Do not open CBS.log in Notepad and save it while DISM runs. Get-Content only reads the file. If you want to search it later, copy it first, for example to your Desktop, and open the copy.

Fix 3. Stop a frozen run cleanly, restart, and check the store before running it again

20 to 40 minutesLow riskCBS.log has been silent for an hour or more and the worker process shows no activity.

A restart lets Windows finish or roll back what the servicing stack left pending. CheckHealth and ScanHealth then tell you whether the store needs RestoreHealth at all, so you do not repeat a long run for nothing.

1. Click the DISM window and press Ctrl + C once. Wait until the prompt C:\Windows\System32> returns. This can take a while.
2. If the prompt does not return after 10 minutes, close the window with the X button.
3. Restart through Start > Power > Restart. Do not hold the power button: Windows may have repair work to finish during the restart.
4. Open Terminal (Admin) again and ask DISM whether the image was flagged as damaged. This takes seconds.

   DISM /Online /Cleanup-Image /CheckHealth

5. Run a full scan without repairing anything. Microsoft says it "will take several minutes".

   DISM /Online /Cleanup-Image /ScanHealth

6. If the result is The component store is repairable, run RestoreHealth again and then System File Checker, as in the procedure below.
7. If the result is No component store corruption detected, you do not need RestoreHealth. Run only sfc /scannow.

Step by step, with screenshots of each scan: Run DISM and SFC to repair Windows system files. Run RestoreHealth before SFC, as Microsoft's own sequence does, because SFC repairs files from the store that DISM has just fixed.

Fix 4. Repair from a Windows ISO with /Source and /LimitAccess

30 to 60 minutesLow riskDISM ends with 0x800f081f, or it freezes again while waiting for Windows Update.

Without a source, RestoreHealth fetches clean files from Windows Update. Microsoft documents /Source to give it a Windows image instead and /LimitAccess to stop it from contacting Windows Update, which removes the download wait.

1. Press Win + R, type winver and press Enter. Note the version (for example 25H2), the build number and your edition (Home or Pro).
2. Download the Windows 11 ISO from Microsoft's software download page, in the same language as your Windows. The page currently offers version 26H2.
3. Right-click the ISO file and select Mount. Note the drive letter it gets in File Explorer, for example E:.
4. In Terminal (Admin), check which image file the ISO holds.

   dir E:\sources\install.*

5. List the editions inside it and note the Index of yours (Home, Pro).

   DISM /Get-ImageInfo /ImageFile:E:\sources\install.wim

6. Run the repair from that image. Replace E: with your drive letter and 6 with your index.

   DISM /Online /Cleanup-Image /RestoreHealth /Source:Wim:E:\sources\install.wim:6 /LimitAccess

7. When it ends successfully, run sfc /scannow, then restart the PC.

Two Microsoft rules decide whether this works. The source must be patched at least as high as your PC: "If the target OS is patched to a higher level than the source, adding features or repairing Operating Systems may fail." And it must contain your language packs. A 26H2 ISO cannot always repair a 25H2 PC, so when the versions differ, Fix 6 with the same ISO is the more reliable way.

If a Windows update also fails with store errors, our guide to Windows update error 0x80070302 shows how to find the exact missing package in CBS.log.

Fix 5. Make Windows Update reachable as the repair source

15 minutesLow riskYou have no ISO, and the logs show download failures, 0x800f0906, or a company update policy.

Microsoft names Windows Update as the default repair source when policy allows it, and says that DISM repair "works best when you connect to Microsoft Update servers". If the update service or its cache is broken, DISM waits on a download that never arrives.

1. Open C:\Windows\Logs\DISM\dism.log (make a copy first) and search for 0x800f0906 or 0x800f081f near the end.
2. Check that the PC is online and that Settings > Windows Update > Check for updates works without an error.
3. Reset the Windows Update services and their cache with the procedure below, then restart.
4. Run DISM /Online /Cleanup-Image /RestoreHealth again without /LimitAccess and watch CBS.log as in Fix 2.

Step by step: Reset Windows Update components. On a work or school PC, an administrator may point Windows at a company update server. Microsoft's Group Policy setting for this is Computer Configuration > Administrative Templates > System > Specify settings for optional component installation and component repair. Ask your IT team before you change it.

Fix 6. Reinstall Windows over itself and keep your files and apps

1 to 2 hoursLow riskThe store is non-repairable, hundreds of manifests are missing, or Fix 4 failed with a matching ISO.

A repair install replaces the whole component store with a fresh copy. Microsoft says the Windows 11 option "repairs system files and components" and "preserves your apps, files, and settings", so it fixes what RestoreHealth could not.

1. Back up the files you cannot lose first: Back up your files (Windows Backup, File History, Time Machine).
2. On Windows 11 open Settings > System > Recovery and, under Fix problems using Windows Update, select Reinstall now. Keep the PC on power and online.
3. If that option is missing (managed PCs, older builds), mount a Windows ISO of the same version and run setup.exe, keeping personal files and apps.
4. After the restart, run DISM /Online /Cleanup-Image /ScanHealth to confirm the store is clean.

Step by step, with both ways and the Windows 10 path: Reinstall Windows without losing files. Microsoft notes that Fix problems using Windows Update needs Windows 11 22H2 or later with the February 2024 optional update, and is unavailable on PCs whose updates are managed.

If DISM still stops at 62.3%: logs, support and hardware

1. Copy C:\Windows\Logs\CBS\CBS.log and C:\Windows\Logs\DISM\dism.log to your Desktop. Work on the copies.
2. In the CBS.log copy, search for Summary:. Microsoft's example shows Total Detected Corruption, Total Repaired Corruption and Operation result.
3. Lines such as CSI Payload Corrupt or CBS MUM Missing name the damaged component and its build number, for example 10.0.19045.4291.
4. In dism.log, read the last Error lines. 0x800f081f means no clean copy was found, 0x800f0906 means the download failed.
5. For help on Microsoft Q&A or from support, zip the whole C:\Windows\Logs\CBS folder and dism.log. Volunteers there ask for exactly these files.

Suspect the hardware when everything is slow, not only DISM: Task Manager shows the disk at 100 % for hours, files take long to open, or the drive makes noise. Check the drive with Check a disk for errors (chkdsk) and back up your files before anything else. A failing drive can also be what damaged the component store in the first place.

How to keep RestoreHealth from stalling next time

Windows already cleans the store on its own through the StartComponentCleanup task in Task Scheduler, which waits at least 30 days before it removes older component versions. You can run the same cleanup by hand with Dism.exe /online /Cleanup-Image /StartComponentCleanup, but it shrinks the store and does not repair it.

Frequently asked questions

Why does DISM stop at exactly 62.3%?

Microsoft has not explained the number in its documentation, and we found no Microsoft statement about it. Users on Windows 10 and on every Windows 11 version report the same figure, so it marks a point in DISM's own progress, not a fault on one PC. Others see 62 %, 63 % or 64 %. The number itself is not an error and does not tell you what is damaged. CBS.log shows what DISM is actually doing at that moment.

How long should DISM RestoreHealth take?

Microsoft only says the operation "will take several minutes". In practice it depends on how much is damaged, the speed of the drive and, without /Source, the speed of the download from Windows Update. Users on Microsoft Q&A report about 20 minutes on a fast PC and several hours on slow ones. Judge by the log, not the clock: as long as CBS.log keeps getting new lines, the run is working.

Is it safe to close DISM while it is stuck at 62.3%?

Only when it is really stuck: CBS.log silent for an hour or more and no activity from Windows Modules Installer Worker. Then press Ctrl + C, wait for the prompt, and restart through Start > Power > Restart. Microsoft does not document the effect of an interruption, and users report that the next run starts again from zero. Never cut the power during a repair, because Windows may still be writing to the component store.

Does pressing Enter really make DISM continue?

Only when the window was paused by a text selection. In the classic console window a mouse click starts a selection, and while it is active DISM cannot print its next line, so it waits. Pressing Enter or Esc clears the selection and the run goes on. Users on Microsoft Q&A report DISM jumping to 100 % right after a key press. If nothing was selected, a key press does nothing at all.

Do I run SFC or DISM first?

Microsoft's Windows Update repair article runs DISM RestoreHealth first and sfc /scannow second. SFC replaces damaged system files with copies from the component store, so the store must be healthy before SFC can do its job. If SFC already ran and said it could not fix some files, run DISM now and then SFC once more. Our step-by-step page with both commands is linked in Fix 3.

Should I restart after DISM RestoreHealth?

Yes, after RestoreHealth and SFC have both finished. DISM itself does not always ask for a restart, but files that were in use can only be replaced at startup, and Windows may finish pending servicing during the restart. After you stopped a frozen run, a restart is required before you try again. Use Start > Power > Restart rather than Shut down, so a fast startup setting does not skip the full restart.

What is the difference between CheckHealth, ScanHealth and RestoreHealth?

CheckHealth only reads whether a failed process has already flagged the image as damaged and whether it can be repaired. It takes seconds. ScanHealth scans the whole component store for damage and repairs nothing. RestoreHealth scans and then repairs automatically, which is why it takes the longest and is the one that stalls at 62.3 %. Microsoft's DISM reference describes the three options this way. Run ScanHealth first to know whether RestoreHealth is needed.

Can I use an ISO of a newer Windows version as the DISM source?

Sometimes, but not reliably. Microsoft warns that when the PC is patched higher than the source, a repair may fail because the PC needs newer files than the source holds. A newer ISO can lack the older component versions your PC refers to. Microsoft's download page offers only the current release, now 26H2. When the versions differ, an in-place repair install from that ISO (Fix 6) is the more dependable way.

Is my data at risk when DISM hangs?

Not your personal files. DISM RestoreHealth works only on the Windows component store in C:\Windows\WinSxS and its records, and it never touches documents, photos or apps. The risk is to Windows itself if the PC loses power in the middle of a repair, which is why you stop it with Ctrl + C and a normal restart. Back up your files anyway before Fix 6, as you would before any reinstall.

I searched 'restorehealth se queda en 62.3'. Does this guide apply?

Yes. "Se queda en 62.3" is the Spanish way of saying that RestoreHealth stays at 62.3 %, and it is the same behaviour on a Spanish Windows. The commands are identical in every language, and the log paths are the same. Only the messages DISM prints are translated. Add /English to a DISM command if you want its output in English while you follow this guide.