24H2 - how to remove the two (un)reclaimable that always show in DISM

[MOoD90s 0]

In 24H2 the command Dism /Online /Cleanup-Image /AnalyzeComponentStore always shows that there are 2 reclaimable packages, and that a cleanup is recommended.

But they remain there after the cleanup command Dism /Online /Cleanup-Image /StartComponentCleanup

They are even present in a clean install.

Bree said:

As an experiment I did a clean install with a 26100.2033 USB made by the MCT. At no point did I let it connect to the internet. These two unreclaimable packages were already present. There is no possible way to avoid them, the fault is built into the install media!

Click to expand...

I am grateful to @hader who showed how to identify the offending packages.

hader said:

2 Packages are responsible for that;
- [Microsoft-Windows-FodMetadataServicing-Desktop-Metadata-Package~31bf3856ad364e35~amd64~~10.0.26100.1742]
- [Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10]

Both packages "is a top-level package and is deeply superseded".....

This info can be seen inside the C:\Windows\Logs\CBS\CBS.log file after a dism /online /cleanup-image /AnalyzeComponentStore command.

Click to expand...

I have found that if I uninstall just the Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10 package, in doing so the Microsoft-Windows-FodMetadataServicing-Desktop-Metadata-Package~31bf3856ad364e35~amd64~~10.0.26100.1742 package gets removed at the same time.

This one command removes both....
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10

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

A new cumulative update, KB5053656, gave me the opportunity to test that removing the packages did not interfere with further updates, and that the two (un)reclaimable packages did not return.

KB5053656 Windows 11 Cumulative Update Preview build 26100.3624 (24H2) - March 27 - post #22

These packages date back to build 26100.1742, the initial release of 24H2. They have long been superseded, removing them should do no harm, and means that DISM now reports correctly whether or not a cleanup is recommended.