Analyze Component Store - 2 reclaimable packages?

Why does Dism /online /cleanup-image /analyzecomponentstore sho 2 reclaimable packages? I have tried many things to check, clean, analyze, look for pending packages, look for corruption.....it doesn't seem like they are there.

Does someone know what this is - false report?

Do not worry about if for now as it is another bug of 24H2.
Run this one then do not worry about it.

KevTech said:

Do not worry about if for now as it is another bug of 24H2.
Run this one then do not worry about it.

Code:

Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase

How to identify Reclaimable Packages reported as count by "Dism /Online /CleanUp-Image /AnalyzeComponentStore"

"Dism /Online /CleanUp-Image /AnalyzeComponentStore" reports that there are Reclaimable Packages: Number of Reclaimable Packages : 2 Component Store Cleanup Recommended : Yes After running "Dism /Online /CleanUp-Image /StartComponentCleanup" the number of Reclaimable Packages does not change...

www.elevenforum.com

Click to expand...

Did that several times....no change. She of the things I did in varying orders in and around reboots:
Dism /online /cleanup-image /startcomponentcleanup /resetbase /cleanupresetbase
Dism /online /cleanup-image /SPSuperseded
Dism /online /cleanup-image /restorehealth
Dism /online /cleanup-image /startcomponentcleanup /resetbase
Dism /online /get-packages | findstr /i pending (see if any pending ones can be manually deleted)
Disk cleanup
Dism /online /get-packages > C:\packages.txt (look for 'superceded' or other weird states)
net stop bits
net stop wuauserv
net stop cryptsvc
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start bits
net start wuauserv
net start cryptsvc
then Dism /online /cleanup-image /startcomponentcleanup /resetbase again
looked for ERRORs in the dism log
Dism /online /Get-Features /Format:Table (look for Disabled but Installed features)
Looked for Superseded in Powershell
Looked for pending updates in WinSxS\pending.xml


So I would say yes, I agree with you @KevTech - it must be a bug

Awalt said:

Did that several times....no change. She of the things I did in varying orders in and around reboots:
Dism /online /cleanup-image /startcomponentcleanup /resetbase /cleanupresetbase
Dism /online /cleanup-image /SPSuperseded
Dism /online /cleanup-image /restorehealth
Dism /online /cleanup-image /startcomponentcleanup /resetbase
Dism /online /get-packages | findstr /i pending (see if any pending ones can be manually deleted)
Disk cleanup
Dism /online /get-packages > C:\packages.txt (look for 'superceded' or other weird states)
net stop bits
net stop wuauserv
net stop cryptsvc
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start bits
net start wuauserv
net start cryptsvc
then Dism /online /cleanup-image /startcomponentcleanup /resetbase again
looked for ERRORs in the dism log
Dism /online /Get-Features /Format:Table (look for Disabled but Installed features)
Looked for Superseded in Powershell
Looked for pending updates in WinSxS\pending.xml


So I would say yes, I agree with you @KevTech - it must be a bug

Click to expand...

HA HA! Just scrolling not paying attention, and I thought that was a real bug on my screen!

When you post about possible bugs, please type winver into Windows search and tell us the results, what build.
If you’re using 24H2, I believe there are still many people complaining about this oversight.

I am on 26120.3281.

Awalt said:

I am on 26120.3281.

Click to expand...

Cheers. Pain in the butt bug for 24H2 apparently. See if this is of any use to you:



Also

• Add WinSxS Component Store Cleanup Context Menu in Windows 11
• Repair Windows Image Component Store in Windows 11
• Use Disk Cleanup in Windows 11

Awalt said:

Does someone know what this is - false report?

Click to expand...

It's a problem typical for 24H2. And no! there is nothing wrong or corrupt; It's normal! (I Know but I looked very deep in this issue and it can't be resolved!)

Had a look at it; How to identify Reclaimable Packages reported as count by "Dism /Online /CleanUp-Image /AnalyzeComponentStore"

To be short; Run a dism etc. /AnalyzeComponentStore command. When done: Open the C:\Windows\Logs\CBS\CBS.log file and search for; "is a top-level package and is deeply superseded"

You will find 2 hits; Those are those 2 unreclaimable packages.
1) [Microsoft-Windows-FodMetadataServicing-Desktop-Metadata-Package~31bf3856ad364e35~amd64~~10.0.26100.1742]
2) [Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10]
Both has the status: "is a top-level package and is deeply superseded"

Whatever they advise you to do; it won't help! (I have done it all to no reveal) It's a fact we have to live with. Not the ideal situation. But those 2 package belongs to the baseline version of 24H2; Build 26100.1742. I am sitting now on Build 26100.3194 and they are still there (together with a lot of 1742 packages.) With each update which advances the Build number; the last one is removed and replaced by the current one BUT all 1742 packages will remain.
I even removed those 1742 forced in one go and ended (it was still 3194 it seemed...) but corrupted the Windows 11 system. So don't !! They are needed even if they are heavy superseded.

The only solution comes from Microsoft themselves; As soon as they see those packages don't show them as being reclaimable. They are not! So basically it should say just 0. Don’t wake up the sleeping dogs… Now? We are awake and asking questions…

At least I ran
Dism /online /cleanup-image /startcomponentcleanup /resetbase
Dism /online /cleanup-image /analyzecomponentstore

To verify it's back to 2 packages on both computers lol. I guess this is a new category of OCD lol.

I found this thread PowerShell Archives - Ed Tittel
If you scroll down or search for on the page
Running Remove Package Kills Spurious Reclaimables, there is an explanation that there is an outdated package
"Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10] is a top-level package and is deeply superseded"
I ran this elevated command as per the page
dism /online /remove-package /packagenameackage_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10
which worked on my Windows 11 24H2 Build 26100.4652.
I ran an elevated command DISM /Online /Cleanup-Image /AnalyzeComponentStore I still had 2 reclaimable packages then ranDISM /Online /Cleanup-Image /StartComponentCleanup and the cleanup removed the two reclaimable packages and then reran
DISM /Online /Cleanup-Image /AnalyzeComponentStore and confirmed no reclaimable packages.

EB2XR6 said:

I found this thread PowerShell Archives - Ed Tittel
If you scroll down or search for on the page
Running Remove Package Kills Spurious Reclaimables, there is an explanation that there is an outdated package
"Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10] is a top-level package and is deeply superseded"
I ran this elevated command as per the page
dism /online /remove-package /packagenameackage_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10
which worked on my Windows 11 24H2 Build 26100.4652.
I ran an elevated command DISM /Online /Cleanup-Image /AnalyzeComponentStore I still had 2 reclaimable packages then ranDISM /Online /Cleanup-Image /StartComponentCleanup and the cleanup removed the two reclaimable packages and then reran
DISM /Online /Cleanup-Image /AnalyzeComponentStore and confirmed no reclaimable packages.

Click to expand...

It's a well know and old issue. It is just like Microsoft is testing their own meat and is saying those 2 smells funny. You can delete the one and the problems disappears. I can't be bothered anymore. I have done so much In-Place-Installments that they were back again. I even wrote an automatic script that was searching for it and deletes the package. I stopped running that script again and again. MS know this already and has done nothing about this. I hope that with 25H2 this issue will disappear completely. The new ISO must start with a higher number now. No more obsolete 1742 anymore.

hader said:

It's a well know and old issue. It is just like Microsoft is testing their own meat and is saying those 2 smells funny. You can delete the one and the problems disappears. I can't be bothered anymore. I have done so much In-Place-Installments that they were back again. I even wrote an automatic script that was searching for it and deletes the package. I stopped running that script again and again. MS know this already and has done nothing about this. I hope that with 25H2 this issue will disappear completely. The new ISO must start with a higher number now. No more obsolete 1742 anymore.

Click to expand...

I've often likened Windows to a teenage boy's messy bed room. It never quite gets cleaned up but when it happens he can't find anything afterward.

I had been seeing this "two reclaimable packages" on my 2019 origin Dell Inspiron 3280 for long but didn't bother to get rid of them since dism checkhealth and sfc - which I ceremoniously run after every Windows update - were proclaiming everything fine. After reading @EB2XR6's post and also therein mentioned Ed Tittel's Blog - Remove Package Kills Spurious Reclaimables - Ed Tittel - I successfully removed those two. ( Incidentally Ed Tittel mentions @Bree as guru Bree in that blog )

I then turned my attention to the Beelink SEi12 MiniPC and ran dism -AnalyseComponentStore. It found 12 reclaimable packages. Ran dism - StartComponentCleanup which "reclaimed" only 10 leaving that 2 obnoxious reclaimable packages which again I removed with Ed Tittel's blog. Thanks to EB2XR6.

jumanji said:

I had been seeing this "two reclaimable packages" on my 2019 origin Dell Inspiron 3280 for long but didn't bother to get rid of them since dism checkhealth and sfc - which I ceremoniously run after every Windows update - were proclaiming everything fine. After reading @EB2XR6's post and also therein mentioned Ed Tittel's Blog - Remove Package Kills Spurious Reclaimables - Ed Tittel - I successfully removed those two. ( Incidentally Ed Tittel mentions @Bree as his guru in that blog )

I then turned my attention to the Beelink SEi12 MiniPC and ran dism -AnalyseComponentStore. It found 12 reclaimable packages. Ran dism - StartComponentCleanup which "reclaimed" only 10 leaving that 2 obnoxious reclaimable packages which again I removed with Ed Tittel's blog. Thanks to EB2XR6.

Click to expand...

@Ed Tittel and I have been working on understanding these (un)reclaimable packages since they first started appearing in some insider builds a couple of years ago. We've been comparing notes since then.

Bree said:

@Ed Tittel and I have been working on understanding these (un)reclaimable packages since they first started appearing in some insider builds a couple of years ago. We've been comparing notes since then.

Click to expand...

Thank you Bree, for your excellent piece of Detective Work.

dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10

EB2XR6 said:

Thank you Bree, for your excellent piece of Detective Work.

Click to expand...

It was a collaborative effort. I couldn't have got there without the help of other members, as I said in:
24H2 - how to remove the two (un)reclaimable that always show in DISM - post #1

Bree said:

It was a collaborative effort. I couldn't have got there without the help of other members, as I said in:
24H2 - how to remove the two (un)reclaimable that always show in DISM - post #1

Click to expand...

I agree also. Now let's wait if 25H2 has the same problems. I have warned MS about this issue. But they just don't listen while the solution is so easy; Don't show this "error" if it's normal behavior. Be aware of the fact; report 0 and move along. Reporting 2 is just like showing a red flag at a bull. Some will react. In the long run; it does not matter if you delete that one package yes or not. The main issue is keep your Windows system healthy. I also ran into strange problems that occur under the hood of the CBS engine. Other people ran into these problems also. Strange errors after a failed updates. I also watched closely the Microsoft responses on those problems. The just reacted with a load of blabla.. "Check this, do that etc." They always reacted with the same scripted helpdesk answers and did not solve the problem. In the end? Do an In-Place-Installment. And yes that solved many issue. I want to help other people also. When stuff is getting strange? I stop investigating the problem because a quick fix like "do a In-Place-Install" it's a quick fix and wil solve 99% of all problems. Investigating could take hours, days, weeks even. So cut to the chase. Do this and your fine within an hour... The main thing is to remember; Leave all the personal data alone!!! That is above anything. I have lost a storage drive once with all kind of timeless data once. Gone and lost forever... Photo's and a lot of documents I wanted to hold onto a lot. Into the digital bin. Gone forever. That hurts. So since then hello to a strong backup stratagy. I make a strong backup every month. And yes Google and Onedrive are helping also to retrieve the latest data. There will be a gap between restoring your data back again and this day. Google and Onedrive fill that gap in the mean time. (I see a lot of Macrium users here and complaining. Never heard of that company as a backup solution. I just found out (for many years) that Hasleo has a better and free solution that is quick and easy. So use their solution.....I don't understand why that is so difficult. If you have troubles with restoring. It sucks but choose an other company than that is more reliable. Yes I also lost valuable data also. Just cry and try again. Learn..... )

I have some challenge for you to fix. (Don't know if your up to it... But surprise me....)
#1; Hahaha... Tried MS Sandbox if it could compete with the other VM specialists like VMWare or VirtualBox. No it can't. When started each virtual environment is the same and fresh. No trace left from the previous start... OK.... Thanks to some other geeks I could manipulate the Sandbox in such a way that at startup I changed my screen and installed some default programs. Wrote a paper about his and published on Usenet. Eyes were opening. It was just a tryout to see where Sandbox was capable of. Then it crashed. The error? Searching through the whole internet? Not known. OK So deinstall Sandbox then. Disabled everything through features and during a reboot it just said. "Something went wrong. I am reverting the changes...." Damn. No solutions. I have looked in every log that a Sandbox could produce. No clue. So hello to a In-Place-Instalment.

#2 I have installed some wsl component by accident (wslservice.exe) with powershell. It's shows up in my file explorer like I have installed a Linux something. Just an Linux Icon with nothing behind it. Inside features? Nope no Linux for Windows installed. Using a Linux subsystem inside a Windows environment is just a blasfemie. Did deinstall that package inside Powershell. But explorer sees it anyways. How do I get rid of that icon? Yes I know... Best advice; do a In-Place-Instalment. You know what??? you are right. I will do that. Thanks.

Bree don't worry. Some strange echo's from the Windows environments. I look under the hood. Some strange behavior I have seen that could no be explained, researching deep into the Engine that lives underneath. We are not the developers. Easy solution? In-Place-instalment. F* those two not reclaimable packages. It's not that important. You will free some KB stuff. The main thing is that everything inside the Component Store is healthy. People often forget that Windows needs some maintenance also. Just run SFC and DISM commands on a regular basis. Getting rid of old stuff inside the Temp directory's is also important. Old stuff inside the registry? Also important. People forget that when Windows starts up it mainly look inside the registry. If there is a lot of rubbish there it takes time. "My computer is so slow"..... Yes because you don't take care of your registry. MS doesn't do that. So other company's fill the gap. Like Windows Manger and IOBit Systemcare etc. are also capable to get rid of that all that rubbish left behind. Adobe? They are the polluters as we speak about the registry. Uninstalling? The stuff they left behind is more then hundred entry's inside the registry. It's important!. My system boots within 15 seconds. Yes it has to do with components and stuff, but also what it is inside your registry. The smaller it is the better.

I have a problem and you Bree also. We know what issues there are and know their solutions. We both want to help the people. I just want a free of charge blog that will explain things. I also spoke to people over and over again in individual threads. Gave them the same old solutions every times. Which works. There has to be a better way to do this... It's just not me. I stopped repeating myself. It's not about me. I am nothing. I can help. But repeating myself for many times at so many forums. It... Just take a lot of times. Will take every question seriously if I think I could give an answer. Sorry.... I don't have the time...

hader said:

I have some challenge for you to fix. (Don't know if your up to it... But surprise me....)

Click to expand...

Sorry, I don't do Sandbox or WSL.....

hader said:

...those two not reclaimable packages. It's not that important. You will free some KB stuff. The main thing is that everything inside the Component Store is healthy. People often forget that Windows needs some maintenance also. Just run SFC and DISM commands on a regular basis.

Click to expand...

I could reclaim a GB or so by cleaning out those packages. That may not seem much, but with as many machines as I have, and limited storage for their system images, every little helps.

I completely agree. SFC and DISM are part of my clean up routine after every CU.

Thanks Bree for the thumbs up. I am not not looking for it but it is much appreciated. We have both a deeper understanding what lives under the hood of Windows. Windows is just an OS. It's not the only one. I also look under the hood of Linux. Many Linux distributions that means serious business. Security. It it not ment to replace Windows so we can play games on it. F*!. For businesses? They only want a reliable and a stable version. They are trying!!! The latest what amazed me how far they can go is. Bazzsite. Just a Linux distribution which is simulate an Windows environment with Steamdeck crap. You want to install a modern game? Fail.... On the other hand a serious try to run games under a new OS. They are getting better at it. Yes. Linux is not ment for the mean stream people. Installing Mint. Great... But what Sudo means.... Have no clue... Yes I have maintaining many professional Unix and Linux systems. No GUI there. Only the prompt shell. Installed some crontab tasks to kick of some scripts written in Bash or Perl. I don't care. If it does what is is supposed to do? Great. Leave also a log behind so I can trace anything what your doing. When I get a call initiated by a script. It must be serous. I look and solve before the next day starts.... Problems solved. Anyone happy. But unaware of some problems lie underneath. We are the fixers and see things. Addressing the company's? Uhm sometimes they react we have a patch for it. But many times? We are clueless also. Wait till the next version. I have confronted them with some weird situations (and evidence). Yes a problem. We don't have an answer yet. The next patch will solve it and it did. They are listening but only to real complaints.....