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

hader · Apr 2, 2026

FrancoDT said:
Nope, many of us learned the hard way those two unreclaimable packages are there for a reason and need to be left alone. They contain files for future Windows updates and you can get installation errors the next update if you remove them. Leave them be.

Yes I can agree. Have deleted those 2 in the past only to see that they can hampering updates. And it is only a visible issue. Only AnalyzeComponentStore says so you must cleanup the component Store... Which it does not. Deleting by hand? Only 2 packages are removed. So it's total drops from 74 down to 72. Big deal..... Tried to remove them all and... That ended in disaster....

(This command shows 0 with 26H1. Don't know this will be the case if new updates arrive for it.....)

Told MS many times to adjust their checks to see those 2 but report 0. Ignored.... Version 26100.1742 is the version of the initial release of 24H2 and it will be their until a new basic version will come out. This will change to 28000.1719 with 26H1 where 28000.1 looks like it's the real base version. 1719 will likely be the "new" 1742. 26100.1742 is still there because this is a backup base version. The reason for being there is a bit of a mystery. The current version but also the base version can be damaged beyond repair. If you apply an In-Place-Installment everything (new version will be deleted) and a fresh new 26100.1742 version will be placed inside the Component Store. After that has been done An update will placed the latest version alongside 1742 to be updated till the latest version.

As I said earlier 25H2 is a BS version. In real life the 24H2 basic engine is still there. That's why we see updates arriving as wel for 26100.8117 and 26200.8117. They are basically the same. It gives MS the feeling that they has released a new version called 25H2. There will be minor changes (Winver is adapted for it to show 25H2) between them but the basic engine inside the Component Store are still the same.....

Looking at the current build distribution inside the Component Store I see the following; (All build versions starts with 26100. So 26100.8117 etc. 26100.1 is a separate one, left over from the real basic engine. Anything other number than .1 lies on top of it. The same applies for 26H1.)

Loadout (26100.8117) 25H2 Component Store
-----------------------------------------------------
8117 Update contains 8 different build versions.
-----------------------------------------------------
74x 1742
17x 26100.1
1x 6717
1x 7824
1x 8037
1x 8112
75x 8117
1x 9325
==================================================
Total number of packages found: 171.

Loadout (28000.1719) 26H1 Component Store
-----------------------------------------------------
1719 Update contains 7 different build versions.
-----------------------------------------------------
1x 1575
1x 1638
1x 1643
1x 1706
56x 1719
72x 28000.1
1x 9325
==================================================
Total number of packages found: 133.

Bree · Apr 2, 2026

hader said:
Version 26100.1742 is the version of the initial release of 24H2 and it will be their until a new basic version will come out. This will change to 28000.1719 with 26H1 where 28000.1 looks like it's the real base version.

Unfortunately 26H1 is only intended for Copilot+ devices with the latest Arm processors. The rest of us should get an enablement package for 26H2 in due course - so 24H2 will still be the base build.

Windows 11, version 26H1 is a targeted release that supports some of the new device innovations coming in 2026. That means that this release is not being made available through broad channels but is only intended for those who purchase these new devices. At this time, Qualcomm Snapdragon® X2 Series processors will come with Windows 11, version 26H1.

What to know about Windows 11 version 26H1

Scannerman · Apr 2, 2026

Still happily running with 23H2 on the X99 build. The X299 is running 25H2 and for some reason I thought for sure that I had turned off the automatic updates. I would have been happy to stay with 24H2. As most folks here know, I'm not big on AI. I really have to say that staying with 23H2 has resulted in a delay in getting on with my X299 build. It's still sitting on the bench! I can't stress what a relief it is to be free from Windows updates messing me up. I dread to think of all the work I'll have waiting for me when I finally turn my laptop back on. Think I'll just wait for 26H2 to come out first.

hader · Apr 3, 2026

Bree said:
Unfortunately 26H1 is only intended for Copilot+ devices with the latest Arm processors. The rest of us should get an enablement package for 26H2 in due course - so 24H2 will still be the base build.

What to know about Windows 11 version 26H1

The reality says otherwise. 26H1 is initial intended for ARM Qualcomm Snapdragon CPU's. It seems that MS is wanting to address this market also. They tried earlier with 24H2 and 25H2 but that seemed not be so an succes. Make no mistake. Windows (see's it's past) will release a new Windows version every so years. I already have 26H1 28000.1340, 1575 and 1719 for AMD/Intel platforms running on a VM. (There will be no updates for these standalone releases until 26H2 will be released, see document.) It would be real stupid if they keep up going with 25H2 and with 26H2 ignore their AMD/Intel market??

It seems to me that MS is now (yet again) pushing people towards ARM. Like they already did in the past with the introduction of 24H2; TMP2.0 and a recent AMD/Intel CPU. An other attempt to manipulate the market so everybody runs to the shops in order to buy new hardware. A total failure because people could work arround those demands. (Rufus) And Copilot+ devices. Also an attempt. 26H1 runs fine on a machine without it. Much of it all is Manipulating and Marketing BS.

In that document (from MS) it is stated: "At this time, devices with Qualcomm Snapdragon® X2 Series processors will come with Windows 11, version 26H1." At this time yes. But i am sure that MS will announce that there will be a 26H2 version released for AMD/Intel on a later date. MS already announced it in their document "next annual feature update in the second half of 2026" So expect the release of 26H2 with support for AMD/Intel CPU's.

If 26H2 would be only for Qualcomm Snapdragon devices. That would be a marketing failure of the century.... What will AMD/Intel people get then? A release that is not even in development then? Windows 12?

(MS makes profit not on the licenses but what it can gather data from us all) 25H2 or I must say 24H2 has reached their end. 25H2 with al those bugs and fixes seems a worse product than even 24H2. Time for a total overhaul. Maybe 26H2 will be a better and stable product than 25H2. Time will tell. Seen the version inside the Component Store it seems to be a redesign. No more 26100 stuff..... (And yes that AnalyzeComponentStore gives now finally a Zero.....)

Scannerman · Apr 3, 2026

hader said:
If 26H2 would be only for Qualcomm Snapdragon devices. That would be a marketing failure of the century.... What will AMD/Intel people get then? A release that is not even in development then? Windows 12? (MS makes profit not on the licenses but what it can gather data from us all) 25H2 or I must say 24H2 has reached their end. 25H2 with al those bugs and fixes seems a worse product than even 24H2. Time for a total overhaul. Maybe 26H2 will be a better and stable product than 25H2. Time will tell. Seen the version inside the Component Store it seems to be a redesign. No more 26100 stuff..... (And yes that AnalyzeComponentStore gives now finally a Zero.....)

Oh, you are so right! Partly why the X299 still sits on the test bench. I have no idea what drives I want to keep or what I want for a "permanent" Win OS anymore. One thing I'm learning about Win 11 is that it never fails to disappoint. So let's give them marks for consistency. I so miss the old style MS Paint. 25H2 has left me shaking my head. I hardly even use Word anymore because it keeps throwing relentless distractions my way. We can all hope 26H2 will be an improvement but I'm not holding my breath. Yup yup it's all about Co-Pilot and AI compatibility these days. Qualcomm reminds me of my "gloom and doomer" prophetic comments about how the Big Boys want us all on glorified word processors while the real work is being done on someone else's server because that's where most of our data will be going anyway. The Consortium is real people. I didn't call it that. That is a name they chose for themselves.

pseymour · Apr 3, 2026

hader said:
Unfortunately 26H1 is only intended for Copilot+ devices with the latest Arm processors. The rest of us should get an enablement package for 26H2 in due course - so 24H2 will still be the base build.

Click to expand...

The reality says otherwise. 26H1 is initial intended for ARM Qualcomm Snapdragon CPU's. Make no mistake. Windows (see's it's past) will release a new Windows version every so years.

The reality does not say otherwise. Microsoft spells out clearly that 26H1 is for these newer Arm chips. Yes, there is a 26H1 for Intel/AMD devices, but there is nothing new in it for those devices. And nobody said there wouldn't be a new version in the second half of 26. It won't be for these new Arm-based devices targeted by 26H1 though.

hader said:
I already have 26H1 28000.1340, 1575 and 1719 for AMD/Intel platforms running on a VM. (There will be no updates for these standalone releases until 26H2 will be released, see document.) It would be real stupid if they keep up going with 25H2 and with 26H2 ignore their AMD/Intel market??

You say "see document," but "document" says, "Devices running Windows 11, version 26H1 will not be able to update to the next annual feature update in the second half of 2026." (emphasis mine)

hader said:
In that document (from MS) it is stated: "At this time, devices with Qualcomm Snapdragon® X2 Series processors will come with Windows 11, version 26H1." At this time yes. But i am sure that MS will announce that there will be a 26H2 version released for AMD/Intel on a later date. MS already announced it in their document "next annual feature update in the second half of 2026" So expect the release of 26H2 with support for AMD/Intel CPU's.

Nobody said there would not be a 26H2.

hader said:
If 26H2 would be only for Qualcomm Snapdragon devices. That would be a marketing failure of the century.... What will AMD/Intel people get then? A release that is not even in development then? Windows 12?

Again, no one said that. You do realize 26H1 and 26H2 are different versions?

hader · Apr 3, 2026

pseymour said:
Again, no one said that. You do realize 26H1 and 26H2 are different versions?

26H1 is the name now during it development stages. It's not suited for release; they are still developing. That's why no updates will be available for it. The final release will come at the end of the year. It will then be called 26H2. H1 and H2. This same numbering MS already used in the past 21H2 - 25H2 is still a version because it final release came out in the last 6 months of the year. Later this year 26H2 will be released as the final version. It will get a different number 26300 in stead of 28000. 26H2 will in the end be available for ARM and AMD/Intels devices. I do have an 26H1 version with 28000 running on a normal PC with and Intel CPU while you are saying this can't be true?...... This is an release from the Canary channel B.T.W. SO both versions exits!! If 26H1 was intended for ARM only why is there also an 26H1 AMD/Intel version then?

Windows 11 version history - Wikipedia

en.wikipedia.org

You may think what you want and keep arguing but 26H2 for AMD/Intel will be released in the final last 6 months of this year. It wil have 2 tastes ARM and AMD/Intel.

pseymour · Apr 3, 2026

hader said:
26H1 is the name now during it development stages. It's not suited for release; they are still developing. That's why no updates will be available for it.

It is released, for the devices for which it was intended. And there are updates for it, along with updated ISO images.

Windows 11, version 26H1 update history - Microsoft Support

support.microsoft.com

View attachment 167683

hader said:
The final release will come at the end of the year. It will then be called 26H2. H1 and H2.

Regarding 26H1 becoming 26H2... Wrong. "Devices running Windows 11, version 26H1 will not be able to update to the next annual feature update in the second half of 2026. This is because Windows 11, version 26H1 is based on a different Windows core than Windows 11, versions 24H2 and 25H2, and the upcoming feature update. These devices will have a path to update in a future Windows release." So, they may merge back together at some point, and likely will, but not this year.

hader said:
I do have an 26H1 version with 28000 running on a normal PC with and Intel CPU while you are saying this can't be true?...... This is an release from the Canary channel B.T.W. SO both versions exits!! If 26H1 was intended for ARM only why is there also an 26H1 AMD/Intel version then?

I specifically said, "Yes, there is a 26H1 for Intel/AMD devices, but there is nothing new in it for those devices." I know that editions exist for Intel/AMD, because I have access to them (see screenshot).

hader said:
You may think what you want and keep arguing but 26H2 for AMD/Intel will be released in the final last 6 months of this year. It wil have 2 tastes ARM and AMD/Intel.

I never said otherwise. If you're going to respond to what I said, try reading it and respond to what I actually said.

hader · Apr 4, 2026

pseymour said:
It is released, for the devices for which it was intended. And there are updates for it, along with updated ISO images.

Windows 11, version 26H1 update history - Microsoft Support

support.microsoft.com

Regarding 26H1 becoming 26H2... Wrong. "Devices running Windows 11, version 26H1 will not be able to update to the next annual feature update in the second half of 2026. This is because Windows 11, version 26H1 is based on a different Windows core than Windows 11, versions 24H2 and 25H2, and the upcoming feature update. These devices will have a path to update in a future Windows release." So, they may merge back together at some point, and likely will, but not this year.

I specifically said, "Yes, there is a 26H1 for Intel/AMD devices, but there is nothing new in it for those devices." I know that editions exist for Intel/AMD, because I have access to them (see screenshot).

I never said otherwise. If you're going to respond to what I said, try reading it and respond to what I actually said.

I am not repeating myself. What I have said is going happen. 26H1 is still under contruction. The next annual update will be in the last 5-6 months of this year. Than updating will be possible. 26H1 is just a working title. Later on 26H2 will be available for 2 products ARM and AMD/Intel. Why keep the name 26H1 then while in the past they never did with 21-25H2. Other people find this diffenence also strange; What to know about Windows 11, version 26H1 - Windows IT Pro Blog

You ignoring the fact that there are ADM/Intel versions of 26H1 available though the Canary channel. You keep us reminding us that this can't be true. Surprise.... I am stopping this senseless conversation. It's like talking to a wall.

Scannerman · Apr 4, 2026

hader said:
I am not repeating myself. What I have said is going happen. 26H1 is still under contruction. The next annual update will be in the last 5-6 months of this year. Than updating will be possible. 26H1 is just a working title. Later on 26H2 will be available for 2 products ARM and AMD/Intel. Why keep the name 26H1 then while in the past they never did with 21-25H2. Other people find this diffenence also strange; What to know about Windows 11, version 26H1 - Windows IT Pro Blog

You ignoring the fact that there are ADM/Intel versions of 26H1 available though the Canary channel. You keep us reminding us that this can't be true. Surprise.... I am stopping this senseless conversation. It's like talking to a wall.

@hader

I don't doubt a word of what you state. That aside there are different policies allocated by MS for different regions. I understand that you are in Europe so you could have inside information that others do not. MS says all sorts of outrageous things as well and then suddenly changes their position without warning. I'm not trying to muddy the waters here but it certainly makes sense that they would make a "special" version of 26H1 for Snapdragon in addition to a more standardized version for AMD/Intel. Even then MS has been known to change its mind on a dime. e.g. Co Pilot is for entertainment purposes only. These guys will mince words and fudge definitions however it pleases them because they can. Just like Windows 10 was going to be the final OS. They waffled their way out of that one too. Professional rubber lippers.

Bree · Apr 4, 2026

hader said:
I am not repeating myself. What I have said is going happen. 26H1 is still under contruction. The next annual update will be in the last 5-6 months of this year. Then updating will be possible. 26H1 is just a working title.

26H1 (the 28000 build series) is no more 'under construction' than the RTM 25H2 build is. It is a fully validated production release, a 'scoped release for specific silicon' in the words of Microsoft. It is what OEMs supply on Copilot+ PCs that have the latest generation of Snapdragon X2 processors.

The 26300 series, currently an Insider Dev Channel build, is the one that's under construction and intended to become 26H2. 26H1 can never upgrade to 26H2 because 26H2 will be a lower build number than 26H1.

The 29000 series, a Canary Channel build at present, is the one intended for future developments for Intel/AMD x64 (and ARM) machines and may appear as 27H1/27H2 eventually. Only when the General Availability channel has a build higher than 28000 could a 26H1 machine get a upgrade from the GA channel and end this 'parallel release' anomaly.

hader · Apr 4, 2026

Bree said:
26H1 (the 28000 build series) is no more 'under construction' than the RTM 25H2 build is. It is a fully validated production release, a 'scoped release for specific silicon' in the words of Microsoft. It is what OEMs supply on Copilot+ PCs that have the latest generation of Snapdragon X2 processors.

Still curious why a 26H1 28000 series for x64 exits then..... (checked if VMWare is emulating ARM on a x64 Intel CPU; No. It could do it but the system will be worthless very slow. Emulation every Core instruction...) I would expect 26300... (under construction) For now 26H1 can't be upgraded until the annual release of 26H1 later this year. This version must be upgradable as well in the end. Can't image that a version is in it's final state never needs upgrading. As the new cores like Snapdragon Version 2 CPU's are new devices I can't image that MS will have a version that never has to be upgraded.... Their trackrecord on normal standard device is not very good as 25H2 has many bugs and fixes that are plaguing this version.
Can't image that with 26Hx there will be two versions 26H1 for ARM and 26H2 for x64. Why confuse the matter then more? Even 25H2 has one RTM for ARM and x64 also. Just call everything 26H2 later on. If you download the version for ARM if will have a 28000 series engine and for x64 26300 series engine. No big deal.

I suspect that 26H1 for ARM has a higher priority because that new Snapdragon Version 2 CPU can be found into device sold at the beginning of 2026. (Their Surface products..) Personally I find it to early because it can't update until a newer version will be released later this year. I would wait until that version arrives. Don't want to be a guineapig if MS screws up security wise in these early stages. A curious decision.... I think by this pressure MS can't call this version 26H2 because it is released in the first 6 months of 2026. We wil see what's 26Hx is called later on in this year......

Scannerman · Apr 8, 2026

hader said:
We wil see what's 26Hx is called later on in this year......

Maybe they'll call it MS MINT

ChrisJ50 · Thursday at 9:43 PM

I can confirm that those two pesky unreclaimable packages are still there.
I did a repair Install of the May 2026 Update due to another unrelated problem, Then I installed A few dotnet updates and other patches for Visual Studio that Were released since the May ISO, then the June Patch via Windows Update, the pesky packages seem to be back to haunt me again.

Bree · Thursday at 9:51 PM

ChrisJ50 said:
I can confirm that those two pesky unreclaimable packages are still there.
I did a repair Install of the May 2026 Update due to another unrelated problem, Then I installed A few dotnet updates and other patches for Visual Studio that Were released since the May ISO, then the June Patch via Windows Update, the pesky packages seem to be back to haunt me again.

A repair install will always restore them, whether that's using 24H2 or 25H2 media.

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 main difference between 24H2 install media and 25H2 is that the 25H2 one includes and installs the 25H2 Enablement Package.

The 26H2 Feature Update is going to be another enablement package, so they will exist for at least another year.

Josey Wales · Thursday at 10:08 PM

FrancoDT said:
Here's a detailed Co-pilot explanation for you

Why You Shouldn’t Remove Un‑Reclaimable Component Store Packages

Un‑reclaimable packages are marked that way because Windows still needs them. They may include:

Core system libraries

Servicing stack components

Security components

Features that appear unused but are tied to dependencies

Removing them can break Windows in subtle or catastrophic ways.

Windows Update relies on the Component Store to:

Apply cumulative updates

Roll back failed updates

Perform DISM repairs

Enable or disable optional features

If you remove these packages, you may find that:

Updates fail

DISM /restorehealth can’t repair the system

SFC /scannow can’t restore missing files

Feature updates refuse to install

Even if a package looks old or unused, Windows may need it to:

Roll back to a previous version

Support side-by-side assemblies

Maintain compatibility with drivers or apps

Removing these can cause:

Random app crashes

Driver failures

Boot issues

Many people try to shrink WinSxS because it looks huge. But:

Much of the size is hard links, not actual disk usage

Windows already reclaims what it safely can

The “un‑reclaimable” portion is usually small and essential

Trying to manually remove it rarely saves meaningful space.

Microsoft explicitly warns that:

Deleting WinSxS files manually

Using third‑party “cleanup” tools

Removing packages not marked as reclaimable

…can corrupt the OS in ways that cannot be repaired.

This often leads to:

In-place upgrade repairs

Full reinstall

Data loss if the system becomes unbootable

The bottom line
Un‑reclaimable packages are not bloat — they’re the backbone of Windows servicing. Removing them is almost guaranteed to cause problems down the line, even if the system seems fine at first.

AI can and does make mistakes. I have had zero issues.

FrancoDT · Thursday at 10:46 PM

Josey Wales said:
AI can and does make mistakes. I have had zero issues.

I on the other hand had major issues with WU errors the few times I removed those packages and had to resort to repair installs to get the updates. Of course not every system will be effected or be effected right away but the risk is indeed real. Even the author of the command to remove those Un-reclaimable packages had issues on certain PC's with certain builds so remove at your own risk. That AI summery was used because it explained and broke it down simply and concisely. There are other more detailed sources if you you search for them.

garlin · Thursday at 10:49 PM

FrancoDT said:
I on the other hand had major issues with WU errors the few times I removed those packages and had to resort to repair installs to get the updates. Of course not every system will be effected or be effected right away but the risk is indeed real. Even the author of the command to remove those Un-reclaimable packages had issues on certain PC's with certain builds so remove at your own risk. That AI summery was used because it explained and broke it down simply and concisely. There are other more detailed sources if you you search for them.

Just curious, did you ever enable any Optional Features (ie. WMIC, VBScript) or added any Language support?

Those two packages relate to Feature on Demand metadata.

FrancoDT · Thursday at 10:50 PM

garlin said:
Just curious, did you ever enable any Optional Features (ie. WMIC, VBScript) or added any Language support?

Those two packages relate to Feature on Demand metadata.

No, didn't enable anything like that.

ChrisJ50 · Thursday at 11:04 PM

garlin said:
Just curious, did you ever enable any Optional Features (ie. WMIC, VBScript) or added any Language support?

Those two packages relate to Feature on Demand metadata.

Yeah, I did Install All 3 of those things, Because I use them. There is someones software I use that he insists on Using VB Script.
And I Also use languages other than English.

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

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

putting the mental back in experimental

My Computer

Well-known member

My Computer

putting the mental back in experimental

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

New member

My Computer

Well-known member

My Computers

Endeavor to Persevere

Why You Shouldn’t Remove Un‑Reclaimable Component Store Packages​

​

​

​

​

​

The bottom line​

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

New member

My Computer

Why You Shouldn’t Remove Un‑Reclaimable Component Store Packages

The bottom line