Superseded Updates (KB) removal - Question & Feature Request

SM03

SM03

Active Member
Hi,

After adding all the (CU+SSU+EP+WFEP etc) updates into the 20H1 base ISO (19041.1) & after creating an up-to-date 20H2.xxx ISO with all of the latest updates, this is the screenshot of 'existing packages list' from that updated/created ISO

1.png

Here, as you can see, most of the base (v19041.1) packages/components has been listed as a 'Superseded' because a more recent (newer) version of those components have been added via the integrated CU/SSU/EP/WFEP while making this ISO.

So, my Q is, should I remove those base (19041.1) version of those packages while modding the ISO? to trim (reduce) the ISO size? As those updates are already listed as 'Superseded' (replaced with the latest update package) so basically those are useless & not having any impact on the ISO/OS?

And One feature request for the dev nuhi for the future build of NTL

Can you make those existing package removal option a bit faster by updating your app? In the current version of NTL, user can remove those components one-by-one, my suggestion is having a checklist in that section, so that user can select [check/tick] multiple components at a time that the user wishes to remove.

& nuhi can you (or anyone) confirm that removing those components from the source ISO, actually recorded in the current PRESET file? So, that we can apply the same preset next time, & those components will be removed from the ISO automatically? Or this function doesn't register in PRESET & every time, the user has to manually select & remove those components from source ISO?

Tagging AeonX Clanger Kasual Windows 10 User
 
SM03 said:
Hi,

After adding all the (CU+SSU+EP+WFEP etc) updates into the 20H1 base ISO (19041.1) & after creating an up-to-date 20H2.xxx ISO with all of the latest updates, this is the screenshot of 'existing packages list' from that updated/created ISO

View attachment 4424

Here, as you can see, most of the base (v19041.1) packages/components has been listed as a 'Superseded' because a more recent (newer) version of those components have been added via the integrated CU/SSU/EP/WFEP while making this ISO.

So, my Q is, should I remove those base (19041.1) version of those packages while modding the ISO? to trim (reduce) the ISO size? As those updates are already listed as 'Superseded' (replaced with the latest update package) so basically those are useless & not having any impact on the ISO/OS?

And One feature request for the dev nuhi for the future build of NTL

Can you make those existing package removal option a bit faster by updating your app? In the current version of NTL, user can remove those components one-by-one, my suggestion is having a checklist in that section, so that user can select [check/tick] multiple components at a time that the user wishes to remove.

& nuhi can you (or anyone) confirm that removing those components from the source ISO, actually recorded in the current PRESET file? So, that we can apply the same preset next time, & those components will be removed from the ISO automatically? Or this function doesn't register in PRESET & every time, the user has to manually select & remove those components from source ISO?

Tagging AeonX Clanger Kasual Windows 10 User
Click to expand...

I also request that feature and want the preset to register which packages to remove so that one doesn't have to remove one by one or even to select some for removal assuming that feature is added in the future. Regarding what you first said, I also integrated the latest updates but the packages aren't duplicate (I only have 10.0.19041.1 ones) and I also wanted to know if removing some may reduce the ISO size.
 
Last edited:
SM03 said:
Hi,

Here, as you can see, most of the base (v19041.1) packages/components has been listed as a 'Superseded' because a more recent (newer) version of those components have been added via the integrated CU/SSU/EP/WFEP while making this ISO.

So, my Q is, should I remove those base (19041.1) version of those packages while modding the ISO? to trim (reduce) the ISO size? As those updates are already listed as 'Superseded' (replaced with the latest update package) so basically those are useless & not having any impact on the ISO/OS?

& nuhi can you (or anyone) confirm that removing those components from the source ISO, actually recorded in the current PRESET file? So, that we can apply the same preset next time, & those components will be removed from the ISO automatically? Or this function doesn't register in PRESET & every time, the user has to manually select & remove those components from source ISO?
Click to expand...
There are some packages that looks superseded but must be kept (I started creating scripts for superseded but changed my mind).

What I have done in the last 2 months is:
Integrated everything.
Make a backup.
Uncheck all in Compatibility.
Uncheck Winsxs in Components page.
Select Clean Up in Updates page.
In apply page select Stop before saving image.
Make a Winsxs folder backup and unload image without saving.

Process the same image in any way I like without checking Winsxs (needed for driver integration), once finished, replace the remaining winsxs folder with the Winsxs backed up.

I like to get rid of later updates (Winsxs keeps packages for compatibility on future updates), because i don't like kind of BSOD surprises.

Only what NTLite removes is saved in presets. Make your script, run it every time you do integrations on clean sources (integrate, stop before saving image, run your script and unload saving changes by checking the box for "Save changes...").
 
Kasual & Windows 10 User things ain't the same what I initially thought about this

this is the SS of the 'existing packages' from the unmodified base 20H1 (19041.1) ISO. all 23 packages existed (base version v19041.1) installed
1.png

& This is the SS of the same 'existing packages' section, after adding all the latest CU+SSU+DotNet+20H2 EP+WFEP to that base 19041.1 ISO to make it 19042.782 without deleting any 'existing packages' while making/modding the ISO

2.png

But, in my another testing, when I removed all those 'existing packages' components [with base version] that's listed as 'Superseded' in the above (2nd) SS here, presuming all those 'Superseded' packages will be added with its latest version via all the CU/SSU/EP/DotNet & WFEP integration into the ISO while modding, I deleted all those 'Superseded' [15 out of the 23 total, see 1st SS] components from the base ISO, then made another 19042.782 ISO following the same process, i.e. adding all the latest CU+SSU+DotNet+20H2 EP+WFEP, & here's the SS of the ISO from the same 'existing packages' section
3.png

Here, you can see that, all those 15 components, which I deleted, hasn't been added. So my presumption was wrong. & Kasual here I understand that what you wrote in your post, ("There are some packages that look superseded but must be kept "), is true.

So, as this testing goes, you must not remove all of those components from the base/source ISO which you intend to keep & wanna use inside the installed W10 OS. The only component you not gonna use, only that you can delete from there.

Now, I feel like I should've tested this first before posting this thread here. Anyway. just to share this with you guys, am posting this now. lemme know about your thought.
 
Last edited:
Windows 10 User said:
I also request that feature and want the preset to register which packages to remove so that one doesn't have to remove one by one or even to select some for removal assuming that feature is added in the future. Regarding what you first said, I also integrated the latest updates but the packages aren't duplicate and I also wanted to know if removing some may reduce the ISO size.
Click to expand...

About saving/recording those 'existing packages' removing operation in PRESET, as Kasual already said/confirmed in his comment that 'Only what NTLite removes is saved in presets.' so I believe, NTL preset don't actually register those changes in the PRESET. Although I think, it should be implemented along with the multiple removal option which I suggested in the main OP, & only the dev nuhi can do this if he considers this as a feasible suggestion.

As you wrote that you '...also request that feature...' so presuming you already had some discussion with the dev, would like to know, what he said about this?

& About the reduction in size that I mentioned earlier & you also asked, After my testing, here, I see a 317MB reduction in ISO size (from 5.33GB to 5.02GB) after removing all those 15 'Superseded' components from the BASE ISO.
4.png


Deleting IE11 leads to a very minimal/negligible size-reduction difference (~1MB calculated), so I'd not be bothering about that, to say

5.png
 
Last edited:
SM03 said:
About saving/recording those 'existing packages' removing operation in PRESET, as Kasual already said/confirmed in his comment that 'Only what NTLite removes is saved in presets.' so I believe, NTL preset don't actually register those changes in the PRESET. Although I think, it should be implemented along with the multiple removal option which I suggested in the main OP, & only the dev nuhi can do this if he considers this as a feasible suggestion.

As you wrote that you '...also request that feature...' so presuming you already had some discussion with the dev, would like to know, what he said about this?

& About the reduction in size that I mentioned earlier & you also asked, After my testing, here, I see a 317MB reduction in ISO size (from 5.33GB to 5.02GB) after removing all those 15 'Superseded' components from the BASE ISO.
View attachment 4430


Deleting IE11 leads to a very minimal/negligible size-reduction difference (~1MB calculated), so I'd not be bothering about that, to say

View attachment 4431
Click to expand...

Thanks. Could you tell me what he said, then?
 
SM03 said:
About saving/recording those 'existing packages' removing operation in PRESET, as Kasual already said/confirmed in his comment that 'Only what NTLite removes is saved in presets.' so I believe, NTL preset don't actually register those changes in the PRESET. Although I think, it should be implemented along with the multiple removal option which I suggested in the main OP, & only the dev nuhi can do this if he considers this as a feasible suggestion.

As you wrote that you '...also request that feature...' so presuming you already had some discussion with the dev, would like to know, what he said about this?
Click to expand...
Superseded packages are needed for windows update compatibility, that is why you can find "removed" packages in winsxs folder. Always saw windows update complains about CU not being installed and if I'm right, Remove reinstalls is now found in NTLite because CU returns packages removed by NTLite.
 
Windows 10 User said:
Thanks. Could you tell me what he said, then?
Click to expand...
Who told me what? I didn't ask/discuss this matter with nuhi or anyone else in private. You seem to be misunderstood my earlier comment. Read again. As you said in your first comment (here) that you '... request that feature...' so I am asking that to whom you requested? preferably the dev, so I just wanna know what you guys discussed & what he said about this if you asked him via pm.
 
SM03 said:
Who told me what? I didn't ask/discuss this matter with nuhi or anyone else in private. You seem to be misunderstood my earlier comment. Read again. As you said in your first comment (here) that you '... request that feature...' so I am asking that to whom you requested? preferably the dev, so I just wanna know what you guys discussed & what he said about this if you asked him via pm.
Click to expand...

Never mind. I misunderstood what you said.
 
SM03 said:
Yeah, you misunderstood my Q which I already figured & replied accordingly, but you still didn't answer the main Q what I asked here in 2nd paragraph.
Click to expand...

I didn't talk to nuhi. When I said that I also requested the feature what I meant was that I supported what you said, not that I speak to him.
 
Apologies for the delay. You can simply use the clean update backup custom that NTLite will remove these superseded packages :)

2021-02-14 04_25_17.png

2021-02-14 04_27_40.png
 
You must log in or register to reply here.
Back
Top