Should updates be integrated and an ISO created before modifying anything else?

Z

ZorkLVM

Member
Messages
47
Reaction score
4
This is specifically a question for nuhi, but everyone is welcome to offer their input and share what we learn.

It just occurred to me that a lot can change with install.wim after integrating updates. For example, maybe some new AppX packages are installed or different features are added, etc.

Would it be beneficial to first create an iso with updates integrated, and ONLY THEN proceed to create a second iso with further customizations?

Or is NTLite smart enough to consider changes made by updates when they're first loaded into the UI?

Many thanks.
-Z
 
Last edited:
Personally i believe that , and i am pretty sure many others here would agree, in making an iso first WITH the updates before removing things as sometimes an update will add that package back in. I personally create 1 'master' as such, which i update every CU, and trim off on a second
 
You should be covered from my post here
1. post and ask developer help not find out yourself what's be the problem.
Be my guest
 
I did a lot of searching before posting my question, believe me. I didn't think to search for the phrase ntlite windows updates logic, unfortunately. Thanks for the helpful link -- is your answer canonical or just a guess/based on experience?
 
If the update integrates new components, NTLite indicates them in "Placeholder" and it will be enough to uncheck this component and therefore these "new components" will be integrated via the update, then deleted
 
ZorkLVM said:
This is specifically a question for nuhi, but everyone is welcome to offer their input and share what we learn.

It just occurred to me that a lot can change with install.wim after integrating updates. For example, maybe some new AppX packages are installed or different features are added, etc.

Would it be beneficial to first create an iso with updates integrated, and ONLY THEN proceed to create a second iso with further customizations?

Or is NTLite smart enough to consider changes made by updates when they're first loaded into the UI?
Click to expand...
Windows is fairly smart with Cumulative Updates.

There are two types of UWP apps: default or "inbox" Apps, and Store Apps. Default Apps aren't really "apps", but core features packaged as apps in the install image. You can't download Client.CBS for example, from the Store.

Monthly CU's will patch default Apps because they're considered part of core Windows.

Store Apps are updated as standalone packages, via WU or by running the Store app. They're not bundled inside the CU for this reason.

Defender platform (engine) and signatures are both updated by WU. You get a base version in every Windows image, but it's expected to be out of date and one of WU's priorities is to immediately refresh them. NTLite's licensed Updates Downloader can find the latest versions to include as updates.

New Windows features are delivered as either enhanced replacements to existing components, or entirely new components.

NTLite processes changes in a specific order to reduce conflicts. Some patches are expected to patch a previous feature, and not just add other features. So a specific logical order is followed. Add to the base image, before removing anything. Then layer all the Settings (reg keys), Unattended mode and Post-Setup tasks afterwards.

These days, the only hard rule to follow is: If you need to add Language Packs, always apply them first to an image before proceeding with the rest of your normal changes.
 
You must log in or register to reply here.
Back
Top