Solved DISM.EXE files check component store

mecanicogolf · Jan 29, 2024

When I ran Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore, It told me it needed a repair. It had 13 repairable and said they were repairable.

I then ran Dism.exe /Online /Cleanup-Image /StartComponentCleanup and it went through the process very fast, jumping up to 20% and saying it was successful.

I then went back to the first anaylisis Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore and it stated the is was not repaired. It still had 13 repairable files.

Why is this not working? Is the component store crucial for the system to be working? Is is OK if this does not repair?

Any other methods would be appreciated from the forum. Thanks

garioch7 · Jan 29, 2024

@mecanicogolf ,

Try running dism /online /cleanup-image /restorehealth.

If that completes successfully, try running your . . . /AnalyzeComponentStore scan again.

I hope this helps. Have a great day.

Regards,
Phil

FreeBooter · Jan 29, 2024

The /AnalyzeComponentStore a parameter that is used as functionality that can determine the actual size of the WinSxS folder.

You need to execute DISM.exe /Online /Cleanup-Image /ScanHealth command to scan the image for component store corruption.

mecanicogolf · Jan 30, 2024

FreeBooter said:
The /AnalyzeComponentStore a parameter that is used as functionality that can determine the actual size of the WinSxS folder.

You need to execute DISM.exe /Online /Cleanup-Image /ScanHealth command to scan the image for component store corruption.

Yes. I did all of this. I have corruption (13) and it tells me to cleanup. So when I run the cleanup, it jumps up to 20% and says it's completed correctly. But when I go to check it again, the same 13 are still there. It's not cleaning up!!!

FreeBooter · Jan 30, 2024

Did you execute Sfc /scannow command?

mecanicogolf · Jan 30, 2024

FreeBooter said:
Did you execute Sfc /scannow command?

Yes. All is well.

x BlueRobot · Jan 30, 2024

mecanicogolf said:
But when I go to check it again, the same 13 are still there. It's not cleaning up!!!

What is the exact message you're being shown?

FRST Fix
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Please note that the fix script won't actually fix anything but will simply run a Powershell to check the state of your packages.

FreeBooter · Jan 30, 2024

Do you get any error message when executing dism /online /cleanup-image /restorehealth command?

The Dism.exe /Online /Cleanup-Image /StartComponentCleanup command used after and recommended reducing the size of compenent store WinSxS folder this command does not fix any errors.

x BlueRobot · Jan 30, 2024

mecanicogolf said:
Why is this not working?

It's difficult to say without examining your DISM log but I should imagine you have a few orphaned packages which have been left in an "uncleanable" state. That's what I want to check with the FRST script.

mecanicogolf said:
Is the component store crucial for the system to be working?

Yes and no, I've seen Component Stores in a complete mess and the operating system still ran fine, however, you'll eventually have a number of problems with installing updates, drivers or doing any version upgrades.

mecanicogolf said:
Is is OK if this does not repair?

Not really, I wouldn't recommend leaving it in that state.

mecanicogolf · Feb 16, 2024

Reinstalled and got it fixed. Thanks all.

x BlueRobot · Feb 18, 2024

A quicker way would have to been to run the provided Powershell script and then remove any packages returned using the following from command prompt:

Code:

DISM /Online /Remove-Package /PackageName:{Package Name}

Solved DISM.EXE files check component store

Well-known member

My Computer

Retired R.C.M.P. Veteran

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Account Closed

Attachments

My Computer

Well-known member

My Computer

Account Closed

My Computer

Well-known member

My Computer

Account Closed

My Computer

Similar threads