NTLite changes a Windows installation source before a computer runs Setup. It can open an ISO or Windows image, integrate drivers and updates, remove selected components, define setup answers, and save the result as a reusable image or bootable ISO. NTLite can also edit an installed Windows system, but that live mode changes the running installation rather than creating a clean deployment source. It does not capture an existing computer into a new WIM backup.
Images contain editions
A Windows ISO can contain several editions inside its install image. NTLite lists those editions and lets the user mount one for editing. ISO, WIM, ESD, and split SWM sources follow different storage rules. An ESD normally needs conversion to writable WIM form before editing, while SWM exists to divide a large image into parts that can fit media with a single-file size limit.
Dragging one standalone WIM into NTLite creates an Isolated entry. The edition can still accept suitable image work, but Create ISO remains unavailable because a bootable installer needs the rest of the setup files. Starting with the full ISO content avoids reaching the final page with no complete media tree to package.
Changes stay queued
NTLite collects work in a queue rather than altering the source after every click. An update, driver, registry change, component removal, or setup script remains pending until Apply starts processing. The final page exposes that list, which makes it the last place to catch a driver aimed at the wrong edition or a removal inherited from an old preset.
Presets make repeated deployments consistent, but they also repeat stale assumptions. Loading a preset built for another Windows release can select components or settings whose dependencies have changed. Compatibility options protect components needed by selected jobs, yet they cannot know every third-party program that a future machine will run.
Removal affects repair
The Components page marks removals and supports compatibility locks. Standard DISM app removal follows Windows servicing behavior. The DISM plus Custom mode removes extra traces, but NTLite warns that the deeper cleanup can also remove support needed to reinstall that application from Microsoft Store. A smaller image can therefore lose an ordinary recovery path.
Saving also has a destructive choice. Save the image retains other editions, while Save and trim editions deletes the editions not selected for the output. That reduces distribution size but cannot substitute for keeping an untouched source image. NTLite can revert a mounted edit to a reference image before saving; it cannot recreate an edition after the only source that contained it has been overwritten.
Setup can wipe disks
The Unattended page prepares answers for Windows Setup. It can choose an edition, create user details, handle regional settings, target a partition, and control out-of-box prompts. Disk automation deserves separate testing because the answer file can create, format, or wipe partitions without waiting for a person at the target computer.
NTLite documents an individual-partition path for installations that must leave other partitions intact: Wipe disk stays unchecked, Partition mode uses Modify, and the selected partition receives the install flag. A wrong disk or partition identifier can still destroy the wrong data. Testing the answer file in a virtual machine with the same disk layout catches that error before physical deployment.
Build the final media
NTLite can apply one job to several editions and then create an ISO. Updates that belong in the Windows servicing image go through the Updates page, while ordinary executable installers belong in Post-Setup. Mixing those package types can leave an expected runtime absent even though the build completes.
The resulting ISO needs a boot test and an installation test. Successful image processing proves that NTLite wrote the requested output; it does not prove that Setup can find storage, that networking starts, or that every removed dependency is unnecessary on the destination computer.
