DISM RestoreHealth stuck at 62.3% [Info / Resolved]

Anonymous
2025-02-24T16:34:33+00:00

This is not a question. I would give some information about the above message, I found some stuff arround this subject and I want to share it with you all. My question; Did you also see the problems and it's progress as I did? I'll explain. Read on.... 🤔

(Applies manly for those who are using Windows 11 (Pro) 24H2 Build 26100.3194 and below. Maybe the problem also occurs with 21, 22, 23H2? Reason may differ but the problem maybe the same. Can't check that anymore. I am already sitting at the latest Build of 24H2 itself. I want to be up to date and not left behind with MS versions.)

I see a lot of entry's about the above issue. Unfortunately I can't comment on them because the thread is locked and can not be replied at. For this reason the same question is asked by someone else again and again etc. Policy's..... This has a negative effect. I would rather see this in 1 thread with 100 pages than this......

This issue has been asked a lot; Why? The reason for it; people look at the value and it seems to be stuck at 62,3% for quite some time. (Many minutes. Hour or hours even.) The question is understandable because everyone is asking; What is my system doing?

I self ran against this problem for the first time after an 24H2 26100.3037 update to 24H2 26100.3194. I had never ever had this problem and after cleaning the Component Store a /CheckHealth DISM command; It found problems. So I started to fix it with the DISM /RestoreHealth command and till my amazement it got stuck at 62,3% !!

(I found: there was an issue build in the update 26100.3194. (Could be repeated at a separate VM) After an /AnalyzeComponentStore it found a number of reclaimable packages, so I ran the /StartComponentCleanup command. Check it's health again and suddenly it found problems. In my case a "photon" package (some internal Windows stuff) inside the C:\Windows\WinSxS directory that got damaged and needed repair.... It's called:

amd64_userexperience-photon_31bf3856ad364e35_10.0.26100.1591_none_faf85d9f2170dfcf )

"What is my system doing??...." Hanging? In the contrary; Your system is quite busy with checking, downloading (Only with the /Online switch), applying. checking etc. How can you see that? There is one useful command that tails the log file of the DISM command. Start PowerShell as an admin and enter the following command.

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

Watch your Powershell screen; It's adding lines at the bottom each time the CBS.log got updated by the DISM command. You can see it's progress here. It should add new lines on a regular basis. The DISM command is really finished when you see: "Ending TrustedInstaller finalization." Terminating the proces premature won't help. At the next /RestoreHealth command it will start the whole proces again, checking, checking, downloading, applying, checking.

You have to let it run as long as it takes it to finish. I my case I have a fast system, disks & internet and for me this Restoring fase took me 20 minutes to complete. (for me? Strangely very slow.) On slower machines it can take hours of even longer. Be patient!! It speed is depending upon how fast your system is. If you see NO lines added to your Powershell window; then there is something else wrong! You should see progress!!

When DISM is finished you can see that the service; Windows Modules Installer (aka TrustedInstaller) will shut itself down after a while. Reason? Nothing to do..

For people that have 24H2: I must conclude that 2 reclaimable packages will be there to stay forever. (until 25H2) They belong to the base version 26100.1742 and are extremely superseded. Can't be fixed or removed. Did it once (together with other 1742 packages) inside my VM and it messed up Windows 24H2 really good!! Only a new reinstall of putting a backup back will fix the damaged Windows 11 24H2.

The 2 unreclaimable packages are;

  • [Microsoft-Windows-FodMetadataServicing-Desktop-Metadata-Package~31bf3856ad364e35~amd64~~10.0.26100.1742]
  • [Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10]

Both packages has the status; "is a top-level package and is deeply superseded"

They are only visible inside the C:\Windows\Logs\CBS\CBS.log file!! Proof? Rename the CBS.log file. Start a DISM /AnalyzeComponentStore command and after completing search the file for that status. Only those 2 will have that status. Those are the 2 unreclaimable packages.

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

41 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-05-12T22:18:10+00:00

    It worked, thank you so much!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2025-05-11T19:25:28+00:00

    No! 2009 or 2025, Pro or Home it does not matter. The same! (They say Yes... It's all marketing in the end!) If you have an older system? Yep can matter but only in time. I will take you a bit longer to fix it. When Win 11 came out? If I would listen to them? 'Run to the store right now! Buy a brand new system!!' BS My old system ran just as fast as Win 10! (A little better I must admit!.) Go to this site! Download the ISO (Choose the link at the bottom!) Choose Win 11. Download it. Mount it. Press setup. Take some koffie or a day off. 😮😆😆😆😆In the end tada.... Press update and Problem solved! Site? https://www.microsoft.com/nl-nl/software-download/windows11 Just do it!!!...... It can be strange like that but sometimes so easy! And... Don't forget!! Make a backup first!! (I have seen company's die that forget that rule) This will help you! A great product! They saved me many times... Its free and also easy. https://www.easyuefi.com/backup-software/backup-suite-free.html If I had the chance? I would work for free also for them! In the end.. You don't need to be a tech guy like me. I am a fixer. Asking no money. But I can fix your problems!! It's not that complicated in te end. Follow my directions and do it!!!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2025-05-01T16:35:18+00:00

    It looks nice I must say. I only have one problem with these kind of programs. Where is the analyze part of all of this? Blind clicking on buttons without knowing what it does can you get in trouble. I am also missing; "Creating a System restore point" that if things go wrong you can always go back before the change. I am not willing to fix things if there is no need of fixing things in the first place.

    It would be a better option to analyze your system if there are problems and show only those things which needs or can be fixed. There is a risk of clicking on the a fix button and have to reinstall Windows again because the fix caused some problems. These kind of program should made monkey proof to protect the layman from clicking on any button.

    I rather do it by hand because after an investigation I know what's wrong with it and how to solve it.

    Those 2 packages which Windows claims are reclaimable (they are not!!) during a DISM /Online /Cleanup-Image /AnalyzeComponentStore can be solved so that the 2 drops down to 0. It's no small thing to delete a package so I wait if any future updates doesn't go terrible wrong. I use a VM for that purpose.
    I can safely now say the this command will delete the offending package. After a DISM /Online /Cleanup-Image /StartComponentCleanup a second DISM /Online /Cleanup-Image /AnalyzeComponentStore will show that there is no packages anymore which can be reclaimed. Zero! (as it should be)

    Deleting the offending package:
    DISM /Online /Remove-Package /Packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10

    In this case I know the cause and how to fix it. One stupid package from the first edition (26100.1742) that (like 56 other 1742 ones) are never gonna be used anymore. All superseded by a current release version like (at this moment); 26100.3915. (not excactly true. Windows reports 26100.3915 but under the hood there are 1x 3910, 57x 3912 and only 4x 3915. Only by those existing 4 packages it's called "3915" If they were absent it would be "3912" Seems to normal since the past 2 latest updates.... Beforehand? They ALL had the same build number!)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2025-04-14T19:13:30+00:00

    Yes. So far, so good! (The operation completed successfully) 8 reclaimable packages. That is possible and can be normal after an update. In the line underneath it it also states: Cleanup recommended: Yes. That will be the next step.

    The next thing you should do is to issue (as admin again) DISM /Online /Cleanup-Image /StartComponentCleanup

    This will cleanup your SxS store. Can take some time so be patient. It will go though more than 200 packages and tries to give them a good status. 95% will be a check and they are already good. Except for 6 packages..... (because I already know that 2 packages will remain reclaimable... They are not!!)

    If you didn't applied the "Fix": after a  second DISM /Online /Cleanup-Image /AnalyzeComponentStore

    You should see that the number is reduced from 8 to 2. (As I said earlier; That's normal behavior for Win11 24H2 if you didn't applied the fix.)

    You can run /StartCompnentCleanup and /AnalyzeComponentStore as much as you want; There will aways be 2 packages unreclaimable.

    Windows will be good despite the fact 2 are not reclaimable. The majority of Windows users will have those 2 also. It's not a problem. Ignore it.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2025-03-24T18:56:26+00:00

    So, I'm showing the last few entries in the Powershell log as as:

    2025-03-24 09:10:15, Info CBS Read out cached applicability from TiLight for package: Package_for_KB5048779~31bf3856ad364e35~amd64~~26100.2448.1.2, ApplicableState: 112, CurrentState:0

    2025-03-24 09:10:15, Info CBS WU creates the package, AppID:<>: WindowsUpdatesDm.exe: Microsoft.SurfaceHub_75.2130.125.0_x64__8wekyb3d8bbwe, UpdateID:{9F957E77-346A-43C7-81A1-E46B2B30B0EA}, revision: 200

    2025-03-24 09:10:15, Info CBS Read out cached applicability from TiLight for package: Package_for_KB5046683~31bf3856ad364e35~amd64~~26100.2150.1.0, ApplicableState: 112, CurrentState:0

    It's showing the most recent entry was 9:10AM, and it's now 11:55AM with no additional log entries. Is that "normal"? Should I continue to wait for it to finish?

    Thanks in advance for any help you can provide!

    Was this answer helpful?

    0 comments