DISM RestoreHealth stuck at 62.3% [Info / Resolved]

This is the result after 8 days? Did you used /source in the beginning?

What was the original command you used to repair your store which produces (after 8 days) this error?

This error tells me you are trying to repair a windows system with build 26100.3194 using a source with build 26100.3676 (version numbers are fictive)

With other words; the build versions are not the same. Yes it will throw this error. If you are repairing a 26100.3194 build the source must be also a 26100.3194 build. That could explain the abnormal duration of the repair. It can't fix things if the build version are different. Find it strange that it tells you this after 8 days while you should see this error directly after the command was given. It sees your current build and it could get info about the source. As they don't match it could throw an error immediately. Apparently MS doesn't warn you and just like a blind bat goes ahead and tries....

Use winver to get your current build you are sitting on.

Use the Get-WimInfo command to check the source build. dism /Get-WimInfo /WimFile:X:\sources\boot.wim /index:1 (adjust if necessary)

If the builds doesn't match then that is not correct. You should had used the online method instead; Dism /Online /Cleanup-Image /RestoreHealth

/Online doesn't mean using the internet. It just means that your current build must be mounted and "Online" if the repair starts. In normal cases Windows is always mounted and online. It is possible to do this offline but that means you have to boot from an USB stick and give the proper commands. It must see the source onto a USB drive or disk and also see the C-drive in able to function. In this case Windows on the USB stick is Online and the one on the C-drive is Offline. In any case; If DISM sees something corrupted it wil go onto the internet and download that broken part and replaces the package and checks it again if the error is gone. Doing a repair without the intrenet is not possible. It must than use a local source in order to repair stuff. (that sources command)

With hindsight it would be beter if you gave me that starting command from the start. I didn't know you are using a source command. I would given you the advice to break off and to check both versions first. As for now? I advice you to install Windows with a fresh start, Let the update proces proceed and bring you up to the current level; 26100.3624. Enough time wasted.

So finally completed today (8 days since starting) with the following message:

[==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\Windows\System32>

Mhhmmm. Yes that would be a good idea. That it is running for 4-5 days is ridiculous. Installing Windows (new preferably) would be a good idea. By that way you would be faster to solve this issue. Copy in advance as much as personal data as you can. Than make a backup (Full disk or Partition) with a free tool; Hasleo Backup Suite software. It's free and amazing in it's versatility and it's not crippled by trail stuff. (https://www.easyuefi.com/backup-software/backup-suite-free.html) It's quick and easy to use. You can restore files without rebooting.

Once you've made a Full backup (Choose the Windows partition. The rest is made by Windows itself; Recovery etc. A new install will recreate everything again.) and install Windows. (Let the update proces first go ahead so you are quickly on 26100.3624 and skipping a lot of patches) You can start the backup program again and point to the backup file. You can restore everything on a file level. There are 3 options; Complete disk option, Partition option and File option. (Choose this option) If you know your way arround where all of your personal data is located you don't have to save your personal data in advance. It's all there inside the backup. (Make sure that the from location matches exactly the right existing location on your disk. If not it will be placed next to it with a [+xxx] mark and directory's below. You have to copy the files to the correct location by hand and delete the [+xxx] tree) Retrievable all the time until you delete that backup file. Clean your system as good as you can. Settings - System - Storage - Temporary files. No need to drag a lot of garbage over to a backup. Will reduce the backup time and the backup file size. You can also choose to do an installation and leaving the apps and personal data alone. Don't have a good experiences with that. Sometimes it messes things up and leaves you with problems.

Good luck.

Wow, that's a LOT. I'm wondering if at this point it might just be better to re-install Windows from bootable media? It would definitely be faster than waiting for my current DISM iteration to complete (which it still hasn't), btw.

It's still running today, even (3/29/25). New lines are still being added to the log file every day. My system specs are MS Pro 9, Intel core i7, 2.60GHz, 16.0 GB RAM (15.8 GB usable). 64-bit OS and x64-based processor. Using a really fast Wifi connection (Wifi 6) that gets about the same Speedtest results as my other Surface which is wired (Cat 5e).

I saw that there's a way to download an image for DISM to use instead of the /online switch. I'm wondering if I should try that?