Clearing Windows 11 ARM Spurious Reclaimables

Clearing Windows 11 ARM Spurious Reclaimables

I’ve got a new laptop in from Lenovo. It’s a peachy-keen ThinkPad T14s (which I’ll describe in tomorrow’s post, so hold on for those deets). Today, what I care about is its Qualcomm Snapdragon X1-E78-100 CPU, which uses ARM64 not AMD64 architecture. This makes a difference, as I learned in clearing Windows 11 AM spurious reclaimables.

“What is a spurious reclaimable?” I hear you ask. It’s a Windows package in the component store (aka WinSxS) that sticks around, even after you run

DISM /Online /Cleanup-Image /StartComponentCleanup

to have it clean up reclaimable packages in said store. I blogged about this in March, when I explained how a single DISM /Remove-Package command could clear up two (2) spurious reclaimables seeingly built into Windows 11 24H2. This came courtesy of VIP expert @Bree at ElevenForum.com.

How-to: Clearing Windows 11 ARM Spurious Reclaimables

It turns out that those spurious packages for ARM64 are more or less the same as those for AMD64. But the names are slightly different for one of them. Unlike AMD64 a single /Remove-PackageĀ does NOT suffice to clear up both spurious reclaimables. Instead each package must be removed individually, as follows:

1. The initial syntax for each command line is the same: DISM /Remove-Package /Packagename:

2. The first package name replaces the “AMD64” with “ARM64” in its name with no further changes — namely Package_for_RollupFix~31bf3856ad364e35~arm64~~26100.1742.1.10

3. The second package name does the same substitution, but drops the minor version numbers from the end, too — namely Microsoft-Windows-FodMetadataServicing-Desktop-Metadata-Package~31bf3856ad364e35~arm64~~10.0.26100.1742

If you build up the entire command strings with the common stuff from item 1 above plus the bold text in item 2 (1st command) and item 3 (2nd command) you’ll clear out both spurious packages for Windows 11 24H2 ARM. Just a little bit different, but it does the trick.

Cheers!

 

Facebooklinkedin
Facebooklinkedin

Leave a Reply

Your email address will not be published. Required fields are marked *