Customizing your windows installation: A guide to NTLite and more

Modifying the installation image is not "hacking," but rather a supported option by the manufacturer. Without this capability, it would be impossible to provide custom drivers and OEM applications. You can modify using the OEM Adaptive Tool, the Windows AIK package, or by directly interacting with the DISM program.

However, there is also an unofficial but highly advanced and effective tool called NTLite, which allows you to achieve a comparable outcome. NTLite internally uses the system DISM and automatically implements solutions for many errors, uncommon behaviours, and limitations of the Windows servicing stack. This makes it an excellent tool for personal use.

Preparing your installation media primarily involves integrating drivers and removing unwanted applications. The next step involves creating a preliminary default configuration for many settings. Two tasks are no longer necessary today: integrating the product key (as this should no longer be required) and answering questions during the OOBE phase, which is the first-time setup.

Before Windows 10, all questions regarding advertising identifiers, store settings, updates, privacy, and speech and handwriting recognition could be addressed in the unattended phase. Today it is unsupported—the technical capability still exists, but it can sometimes have side effects that make it impossible to log in.

The first step in preparing your image is downloading an installation ISO file for Windows. As we know, Microsoft recommends the Media Creation Tool for this purpose. However, you can obtain direct links to download the ISO file by using the User-Agent Switcher and Manager extension in your web browser and presenting yourself as a Mac. The downloaded image should be unpacked, and the install.wim file found in the directory should be hooked up to NTLite. Here, you can select the edition of the system you are using, for example, Pro. The selected edition is then mounted.

The next stage is integrating updates. NTLite allows you to integrate the latest system updates and those of the installer itself, making the installation process faster and more stable, shortening first logins and requiring fewer restarts. NTLite downloads the required updates from the Windows Update catalogue when we use the "Latest updates online" option.

After integrating updates, it's time to integrate drivers. At this stage, two aspects are important: whether you are creating the USB drive for the same computer you are working and whether the hardware manufacturer provides drivers in an accessible form.

The driver installation view displays a list of devices in the computer for which there are no drivers in the Windows installation image. You should ignore Bluetooth-paired devices, VirtualBox virtual network adapters, VPN clients, and... graphic cards. Unfortunately, their drivers do not integrate well and are best installed separately.

NTLite does not directly allow for simply copying drivers from the system to the image. This option is a premium feature. With caution, it can be overridden by exporting the drivers yourself. The folder with the exported drivers should then be added, in its entirety, to the Driver Queue section. However, several unwanted items will appear on the list that you need to remove on your own.

If you prefer not to rely on intuition, drivers should be downloaded from the manufacturer. Sometimes, this is very easy—for instance, Lenovo provides an "SCCM package," which is an archive with drivers formatted for integration. Conversely, Gigabyte only offers EXE installers, which must be manually unpacked.

After driver integration, it's time to remove components. Windows offers a component-based approach to the installation image, but removing components expected by Windows Update will make it impossible to update the system. However, there is one component that is serviced separately: APPX applications. In the Components section and the "Applications" subsection (not "System Applications"!), you will find a list of elements whose removal will significantly speed up the first login and reduce the time needed for background updates performed by the system Store.

Here, you can remove often unused and replaced applications, such as Clipchamp, Outlook, Mail, Xbox tools (Game Bar, TCUI, Identity Provider, Xbox App), Office ads, News, Photos, Teams, Weather, Power Automate, Solitaire, and Alarms. Although removing Defender and system applications is possible, doing so will prevent the system from updating and may lead to unpredictable and poorly understood compatibility issues. This NTLite feature is intended for preparing test images, with specific purposes.

The final steps in preparing your own installation USB drive involve integrating custom configurations. You can enable frequently used features post-installation (such as Hyper-V and WSL) and disable unwanted and outdated ones, like PowerShell 2.0. At this stage, you can also fully disable the Recall feature—although it is disabled by default and only offered on computers with ARM processors and an NPU.

One of the most commonly used adaptations was configuring UAC and responding to OOBE questions. Today, however, applying these settings is discouraged—therefore, UAC should be configured immediately after installation. However, you can configure the Taskbar and Updates, and also add a local administrative user—which means you won't need to work on a Microsoft account with administrative privileges.

Since entering a product key is no longer necessary, enabling unattended settings is unnecessary. However, if you wish to add a key just in case, as well as configure keyboard layouts and language, it will be necessary. After completing the above steps, you can proceed to the Apply section and reduce the image by removing unused editions—leaving Boot and WinRE images intact is recommended. Selecting "Create ISO" will give you your customized installation image in about fifteen minutes.

The Media Creation Tool can't apply such an image anymore. In this case, you need to use the Rufus program. It prepares an installer compatible with UEFI, bypasses the need to split the WIM file into parts by smart partition manipulation, and allows you to apply workarounds for TPM and Microsoft account requirements. These may, however, conflict with settings applied by NTLite.

In conclusion, it's worth noting that if the laptop manufacturer provides its recovery and reinstallation mechanism, it might be worth using it instead of formatting the drive. The era of manufacturer bloatware has ended—built-in recovery partitions use the same tools and imaging mechanisms as the actual installer while also containing an integrated set of drivers adapted to the hardware.