Removing existing updates from ISO?

K

kosmo

Member
Messages
82
Reaction score
20
My ISO is "windows_10_iot_enterprise_ltsc_2021" which I chose because (a) it's seen as stable & reliable and (b) it's already had many of the anti-features (ie: Metro, Cortana) properly removed. But it also has a bunch of "Enterprise" stuff that I don't want or need. Looking at the list of updates that are already installed or are (if I understand correctly) "staged" to be integrated there are several that i'd like to remove.

But choosing "Remove" throws up this message:

Uninstall package? 'Active Directory Lightweight Directory Services'

Due to package handling complexity on Windows side, it is recommended instead to start from a fresh image and integrate only the required packages.
Click to expand...

OK I get the "complexity" and potential risk but I AM starting with a fresh image. Unless you go back to day one (2015) all Win ISO's are going to have a number of updates already installed. So how realistic is this advice?

Looking at the Installed / Staged list there are about 10 that i'd like to get rid of. Anyone like to offer odds on the ISO still working after removing 10 updates?

I also have 5 new updates that i'm sorta willing to install. Install new ones after uninstalling old ones or vice versa?
 
NTLite will sometimes create confusion for the user, in that the Updates list is the preferred way to remove all updates.

Existing packages lists four different Update types:
- Language Pack
- Update (KB file)
- Feature Pack (staged)
- OnDemand Pack (not staged)

From this list, only the normal Update type (KB file) should be removed from the Updates screen. For all other Update types, they should be removed by deleting the Components which match that Update's function.

For your example, to remove the AD LDS feature, we instead remove the component "Active Directory Lightweight Directory Service".

1718042557034.png

Obviously, this is a lot of work if you wanted to remove most of the Feature on Demand updates (Feature Pack & OnDemand Pack). nuhi has expressed a desire to rework the UI, to make this whole process less complicated. But for now, focus on removing unwanted Components and most of the matching FOD updates will naturally disappear after you've applied removals.
 
garlin
Thank You very much for your comprehensive reply! I like your suggestion much more than my (mistaken) idea to deletes updates
 
You're still allowed to remove Updates one by one. But there is no bulk method for removing multiple FOD packages, other than having Components do it as a byproduct of your cleanup.
 
garlin said:
You're still allowed to remove Updates one by one. But there is no bulk method for removing multiple FOD packages, other than having Components do it as a byproduct of your cleanup.
Click to expand...
Sorry for interfering, this was an interesting topic, but why on my setup I am not allowed to delete some updates ?
I get "Error [5] Access is denied. [update name]". I am the admin and run NTL as admin of course...
 
Are you trying to remove a KB update, or a Feature on Demand?
 
I was talking in general. Since in the Updates page there is a menu to Remove every update, and since NTL pretty stores every operation in Presets except this one, I simply judged more logical that even any removal of builtin updates could be stored in a Preset.

For example, I found the hard way that I have to remove the WFEP builtin update from the list, otherwise for some obscure reason I can't get rid of WFEP Component, despite I removed it. But every time I adjust my ISO basing on my current Preset, I must also remember to remove that update. As a solution, I had to generate an intermediate ISO with the WFEP update removed, and use that as starting ISO. So I think it was more convenient to store *every* operation on the ISO inside a Preset.
 
The core problem is NTLite can work on Features on Demand (FOD's) in one of two ways: Features as complete Update packages, or as Components (expanded from a parent Feature).

Integrated FOD packages are listed on the Updates page mostly for reference purposes. nuhi's has mentioned in previous conversations that the current paradigm of how it's exposed creates user confusion and frustration. Right now, the preferred way to remove a FOD is to search in Components for the equivalent feature, and remove it from that side.

When certain components are removed, their parent FOD's will eventually disappear. But in the current UI, there isn't a convenient mapping of Components <-> FOD's.

But there's more problems involved:
1. You can only remove one FOD update at a time, but can't do bulk removals.
2. Presets can't remember to remove FOD's as Updates.

This situation needs work. For now, you should DM nuhi and explain the WFEP situation. That can probably get resolved soon than waiting for a longer term redesign of the Updates workflow.
 
Thanks Garlin, what a mess !
Oh you mean 'PM' Nuhi I suppose lol... surely I will
Thanks for your explanation btw
 
Ps. I sent him a message thru the apposite form, still no replies, I hope he received it...
 
You must log in or register to reply here.
Back
Top