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

jaseuk said:

@Bree I ran your command from post #59 and it removed the two reclaimable packages. However I now notice the 190MB Windows Update Clean-up is back in Disk clean-up. Are the two related?

Click to expand...

Ignore my last, a restart of the PC seems to have fixed it.

Make things easy.
(This is only meant for Windows 11, 24H2 Build 26100.xxxx installations!!. It will fail anyways because the package name is unique)

I made a script that removes those 2 unreclaimable packages automatically. It removes 1 major package only if it's there and there are still 2 (or 1) unreclaimable packages. In case of any other condition; the script will end. Place both files; RunPS.txt and DelPack.ps1 inside a directory of your choosing. Rename RunPS.txt into RunPS.cmd. (Can't upload a .cmd file) Change the variable $MyPath inside the DelPack.ps1 script; Line 3 to reflect the directory where you placed these 2 scripts.

Start cmd as admin, go to the directory and issue the command RunPS DelPack. (If Windows complains that it can't execute a Powershell script see RunPS.cmd how to solve that) If this test run completes with an error (did not remove the package, so "The cleanup action failed") than remove the remark '#' in front of line 54 and rerun RunPS DelPack again to remove the package and watch on screen if the action is successful.

This script has run with succes on several VM installations. But as always as advice; Make a backup of your C-drive first.

A year and a Few Months Later, e are 25H2 and these 2 rogue packages still exist.
And I did a Repair install from the latest ISO. This Problem seems to be back AGAIN after the June Patch Tuesday.

ChrisJ50 said:

A year and a Few Months Later, e are 25H2 and these 2 rogue packages still exist.

Click to expand...

Welcome to Eleven Forum.

That's because 24H2 and 25H2 share a common set of system files. All the new features for 25H2 were delivered in the 24H2 cumulative updates, but were dormant until the 25H2 Enablement Package was installed. The 26H2 Feature Update is going to be another enablement package, so they will exist for at least another year.

Bree said:

Welcome to Eleven Forum.

That's because 24H2 and 25H2 share a common set of system files. All the new features for 25H2 were delivered in the 24H2 cumulative updates, but were dormant until the 25H2 Enablement Package was installed. The 26H2 Feature Update is going to be another enablement package, so they will exist for at least another year.

View attachment 174048

Click to expand...

I hope they at least refresh the wim package and the bootloaders.
They seem really lazy not to do that.

ChrisJ50 said:

I hope they at least refresh the wim package and the bootloaders.
They seem really lazy not to do that.

Click to expand...

They screwed up the boot.wim in all the latest insider ISO files and the ones created by MCT for public builds 26200.8457 and latest one for 26200.8653.
The only way to work around this problem is by creating the ISO files from uup-dump instead of using the official Microsoft ones.
Luckily the ISO files created from uup-dump don't have the changes that added this bug in boot.wim and for that reason they still work as they should.
Note the difference on the size of the boot.wim in the 2 cases.

This is the 26200.8655 created from UUP-dump:



This is the one created by latest Microsoft MCT, 26200.8653:

There’s nothing screwed up there. Just some vague reference to a screw up in boot.wim, then the person shows the details of one image in install.wim. Malarkey.