Solved DISM says component store reparable, but attempt to repair is stuck at 62.3%

Back story: I've been having a memory problem that periodically triggers a BSOD. Windows 11 has generally been really good at recovering. I'm waiting for replacement RAM that UEFI testing found faulty.

Meanwhile, I ran SFC /scannow and found that the component store has many errors in it. I've run DISM before, with success. But this time? I just can't get beyond "dism.exe /online /cleanup-image /restorehealth". It progresses to 62.3% and then just hangs. After an hour, I just presumed it'll never complete and then aborted.

I have searched online and this number is apparently a frequent occurrence. But a viable solution is fleeting. So many recommendations given on different things to do, but I find none of it working. In fact, my component store is bad enough that running Windows 11 23H2 ISO image repair fails to complete, forcing a rollback.

Do I really need to wait longer, like multiple hours? Or is there some fault in play that won't let it complete? Is there a way to just do a complete brute-force refresh of the component store, to ensure all faults are gone?

I tried going the route of Windows 11 update for 23H2, but when I attempt it, I get this error: Download error - 0x80248007.

Have you tried running DISM in safe mode?

cytherian said:

Do I really need to wait longer, like multiple hours?

Click to expand...

No, it should be done in max 20 or so minutes.

Try selecting Command Prompt and hit Enter key to see that will help or execute Dism command from recovery environment.

If Windows 10 or Windows 11 has missing or corrupted system files, in this video, i will guide you how to repair the corrupted system files using the DISM and SFC command tools from Windows Recovery Environment.

zebal said:

Have you tried running DISM in safe mode?

Boot to Safe Mode in Windows 11

This tutorial will show you how to boot Windows 11 into normal mode, Safe Mode, Safe Mode with Networking, or Safe Mode with Command Prompt. Safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default...

www.elevenforum.com

No, it should be done in max 20 or so minutes.

Click to expand...

I hadn't... but I'm now trying to boot to safe mode to do this, but the commands given in that link are failing.

bcdedit /set "Windows 11" safeboot minimal
--> The integer data is not valid as specified.
--> Run "bcdedit /?" for command line assistance.
--> The parameter is incorrect.

Hi, Cytherian.

It certainly should not take hours.


This is just me, so take it with a grain of salt... I would first run sfc /scannow, then run DISM command ~ Dism.exe /Online /Cleanup-Image /StartComponentCleanup > reboot > and run sfc /scannow again. And see what the result is.

Personally, I have never once had a need to run the 'Restorehealth' command.

Wishing you the best.

@cytherian
I can't help with the commands but does option 1 or 2 from tutorial not work?

zebal said:

@cytherian
I can't help with the commands but does option 1 or 2 from tutorial not work?

Click to expand...

I was able to finally figure out that {default} was the preferred value (not "Windows 11"). But the bcdedit commands still failed. Thus, what I did was to run a command to force a shutdown and boot into command prompt. "shutdown /r /o /f /t 00"

The trouble is, in that state... SFC /scannow and DISM behave differently. SFC could not complete beyond 60% of validation. DISM does not recognize option "/cleanup-image". That boot into command prompt must cut back on some privileges, which interfere with these commands.

WXC said:

Hi, Cytherian.

It certainly should not take hours.


This is just me, so take it with a grain of salt... I would first run sfc /scannow, then run DISM command ~ Dism.exe /Online /Cleanup-Image /StartComponentCleanup > reboot > and run sfc /scannow again. And see what the result is.

Personally, I have never once had a need to run the 'Restorehealth' command.

Wishing you the best.

Click to expand...

Thanks. I had run SFC /SCANNOW and it did find issues. But the DISM /Online /Cleanup-Image /ScanHealth gave a prognosis that the component store was reparable. In the past I have run "RestoreHealth" and it worked with no problems. I've rebooted my problem computer and it's presently in a "Diagnosing your PC" mode (going on 20 minutes). But once done I'll try the /StartComponentCleanup. Do you know about the /ResetBase option as well? I'm going to leave that off, just in case, but it's in my notes from the last time I used DISM commands.

Option one in the tutorial should get you to safe mode without having to use any commands.
Once you get to safe mode and logged in click on Start and type CMD in the search bar. Select CMD (admin) on the right. Run 'restorehealth' and 'sfc' there.

@cytherian
my mistake sorry, dism should not be run in safe mode.
I've just tested on my pc and it doesn't work because it can't find sources.

zebal said:

@cytherian
my mistake sorry, dism should not be run in safe mode.
I've just tested on my pc and it doesn't work because it can't find sources.

Click to expand...

Didn't check that, only sfc.

Question hardware guys. I'm curious why would it be advisable for this poster to keep running dism if he knows his ram is bad. From what he said it looks like he's known it for a while and used dism multiple times but his situation has continued to degrade further. All the commands in the world won't fix a hardware problem so isn't doing so just beating a dead horse and just maybe (possibly)creating a corruption problem once the defective hardware is replaced? Inquiring minds want to know.

Fabler2 said:

Option one in the tutorial should get you to safe mode without having to use any commands.
Once you get to safe mode and logged in click on Start and type CMD in the search bar. Select CMD (admin) on the right. Run 'restorehealth' and 'sfc' there.

Click to expand...

OK. I rebooted again, and this time I managed to restart in full safe mode (not command prompt). From there I could run SFC /scannow and DISM. The scanhealth flag worked and completed successfully. Running the StartComponentCleanup flag now... and YES, it just indicated that it completed successfully. I'm going to boot back to normal mode and then run SFC /scannow again to see if errors are cleared.

Should all of this progress be preserved when booting back to normal mode (not safe mode)?

glasskuter said:

Question hardware guys. I'm curious why would it be advisable for this poster to keep running dism if he knows his ram is bad. From what he said it looks like he's known it for a while and used dism multiple times but his situation has continued to degrade further. All the commands in the world won't fix a hardware problem so isn't doing so just beating a dead horse and just maybe (possibly)creating a corruption problem once the defective hardware is replaced? Inquiring minds want to know.

Click to expand...

That's a good question. I had issues with HP support validating the sending of replacement RAM for a 2nd time (it's a long story--the first replacement wasn't the same as original memory specs and my notebook refused to boot--couldn't even get to the BIOS). SO, I'm going to send in the notebook for them to handle it. I created a special account for the HP support team so I wanted to fix things enough so that the notebook can boot up.

OK, good news. The SFC /scannow has confirmed.

My save point recovery had brought me back to 22H2, and before when I tried to use Windows Update to roll forward to 23H2, it would immediately fail. And I think that must've been something to do with the component store errors. I just now ran Windows Update and it did complete this time.

Anyway, the only way I could recover was running bcdedit to configure for safe mode (not command prompt only). From that mode, DISM would run in an elevated command prompt and allow using flag /StartComponentCleanup. That seems to have done the trick. Thanks to everyone here for their advice and assistance on this!

I know it's too late to answer but I found out why and why not to worry that it is taking so long.

My case; Win 11 Pro 24H2 Build 26100.3194. After Patch Tuesday today (Wednesday) My system went from 26100.3037 to 26100.3194. Because I had some issues in the past I decided to track everything including the content in the SxS store. I know that store contained after the update packages belonging to 1742, 3037 and 3194. Analyzed the SxS store and 3 reclaimable packages appeared. (2 of those are never re-claimable belonging to the base package 1742. That Build was released officially by Microsoft (ISO) and those packages will remain there until a new release of 24H2 SP1 (a newer current ISO) will be released. Removing those 1742 packages will corrupt your system for sure!! Tried it in a VM environment.)

Did a cleanup of SxS Store and as expected 2 unreclaimable packages. (All 3037 packages were gone as expected. Only the 1742 and 3194 packages remains.) So far so good. Did a sfc /scannow with no problems. But after the DISM /Online /Cleanup-Image /Checkhealth command it came up with an unexpected message; "The component store is repairable" So? Something is damaged? What?

I went ahead and issued the DISM /Online /Cleanup-Image /RestoreHealth command and... It seems to get stuck at 62,3%. Why? Looked in the C:\Windows\logs\DISM\DISM.log file. There I read something that the further progress can be seen in the C:\WIndows\logs\CBS\CBS.log file. Looked in there; it was quite busy downloading stuff constantly. Looked at the CPU load; processes. The servicehost update was quite busy. So it was doing it's thing. After some time the DISM /Online /Cleanup-Image /RestoreHealth came to an end with 100% succes. By using the /Online parameter it was downloading stuff all the time. After a second /DISM /Online /Cleanup-Image /CheckHealth command it said it did not see any errors anymore.

Conclusion: Watch the CBS.log and see it's progress and be patient. (In my case; duration: 23 minutes) It's normal behavior. The reason why this occurred after an successful update?.. Remains a mystery. I suspect it would also happen before the update.

Keep in mind the the duration depends on your download (maybe also disk, CPU) speed and how busy the download Microsoft servers are.

hader said:

.... The reason why this occurred after an successful update?.. Remains a mystery. I suspect it would also happen before the update.

Click to expand...

About this... Nope!!! Had a virtual machine. Did the same update. Before the Component Store Cleanup: DISM /Online /Cleanup-Image /CheckHealth gave no errors. After the cleanup of the SxS Store; /DISM /Online /Cleanup-Image /CheckHealth gave errors. So a /RestoreHealth was needed. This is introduced with the update itself. This is no normal behavior!!! After a Cleanup of the Component Store no errors should be introduced which are visible during a Check Health check! Repairing it took also some 20 minutes and they all fell about some (the same) photon components. (??)