[SOLVED] [EX-100 - v2.4.2.0] [20H2] New removing engine inefficient?

The size of my ISO is more than 120MB gigger than with v2.4.0.0 - same Windows, same wccf.

Hell Hanyo

Is it possible to send me your two wccf by email at [You must be registered and logged in to see this link.]... I'm interested to check this ... because, with my extreme wccf I haven't found such difference (0Mb with the same updated ISO (20H2.572) and 10Mb with a more recent updated ISO (from 20H2.572 to 20H2.610).

Thanks for the report !

Thank you, winterstorm, for your quick reply. I will gladly send you my wccf if necessary. However, I suspect (the test is currently running) that this is due to unchecked "experimental" items. Is that possible? For example, will no more accessories be removed if the check mark is not set? That would be an explanation.

No, this is not possible, the two systems are independent ... but a bug is still possible ... and in the experimental list, all categories do not have components in them.

Just a thought, have you updated your ISO with a new monthly update ?

I made a test with an updated 20H2-ISO and with a not updated: Same result. I will send you my wccf now.

Maybe the error is caused by the fact that my old wccf had to be adapted to the new structure? I had loaded my old wccf and saved it again (that's what I send you). At least because the language items moved to the "experimental" area, the structure must have changed. Possible?

EDIT: As predicted by winterstorm, my test with checkmarks set in the experimental area does not lead to any other result, thus also to a much too large ISO.

I had lost the overview. The 120MB smaller version was actually a 20H1. So the increase in size is not caused by the changed winreducer version, but by the change to the 20H2. Sorry.

My Win10_20H2_German_x64.iso is 0,83GB bigger than my Win10_2004_German_x64.iso.
My updated and cleaned 20H2 ISO is 0,53GB bigger than my 20H1 ISO.
My winreduced 20H2 ISO is 0,12GB bigger than my 20H1 ISO.

Does anyone know why this is so? Which advantages of the 20H2 justify this increase? As long as winreducer doesn't take it out again, I'll stay with the 20H1.

Hello Hanyo

Are you removing Edge Chronium ?

If yes, this is Edge Chronium which is not correctly removed in 20H2 ... this issue will be adressed in v2.4.2.1 [VIP) and v2.4.3.0 [ALL] which will be available as usual this week-end.

Yes, I remove Edge and everything related to Edge. Now I have hope again to switch to 20H2 after all :-)

SOLVED in v2.4.2.1 [VIP] and v2.4.3.0 [ALL] !

Yes, you will be able to switch to 20H2, if the only trouble you have, is the edge removing size bug

Thanks for your report and your tests

Also with 2.4.3.0 I have the same too big size :-(

Hello Hanyo

Could you please send me your wccf here or by email or forum pm ... and which windows 10 version and edition you are using. Thanks my friend.

Hi winterstorm,

I send you my wccf already with email, but here it is again: Klick

I use Win10 Pro. In a first step I integrate all updates from the winreducer update catalouge and delete all unneeded editions, nothing else. In a second step I run 

Dism /Image:D:\WinReducer\WinReducerEX100_x64\WORK\MOUNT\TEMP_Windows /Cleanup-Image /StartComponentCleanup /ResetBase.

In a third step I use the wccf above.

Hanyo,

Thank you for the wccf

I've tested it, and I confirm the 100Mb differences from 20H1 and 20H2 ... this difference is also present in an updated 20H1 and 20H2 ... one thing you can do, if possible, is to remove the "Services - Windows Font Cache Service" which will be a first step to reduce the final size.

Thank you, winterstorm, I will try this. But that doesn't explain the difference, does it?

Hello carlese,

Not entirely, because it will reduce the size by 25% of the 100Mb ... you know each time MS is adding new stuff or changing part of the system, and this happened everytime they release a new Windows 10 version ... each time the ISO is bigger ... so I will have a look at this as usual to try to reduce even more the windows installation without breaking it, which is the purpose of the WinReducer Project

PS : with my extreme preset I have a lighter difference, 20Mb but I remove almost all components

Hi winterstorm,
I have been working with a very similar wccf for years and I have never had such a significant jump in size. The reason is clearly MS, because the initial ISO is also much larger. However, I don't have the impression that I'm getting more for it, so I'll stick with the 20H1.