Documentation

Components
This page contains a list of detected removable Windows components for the loaded image.
To queue a component for removal, uncheck the checkbox on the left.
Most of the components are color-coded, indicating a member of the template in the menu.

Templates
Menu in the toolbar, unchecks sets of components for each level (Privacy -> Gaming -> Lite), Lite removing the most.
Component checkbox color labels reflect each of the template:
Green – Privacy
Blue – Gaming
Orange – Lite
Red – Not recommended to remove

Compatibility
Opened from the toolbar, these options help you protect the needed components from the removal, for a given feature set.
Enable those that you want protected, that will automatically lock the tied components from unchecking, thus and removal. Especially useful in combination with Templates.

Features
This page contains a list of configurable Windows features for the loaded image, same as would be in the Optional Features of your current installation’s Settings or Control Panel.
Green titles are already enabled on the image, simplifying the pending state change overview. State of each feature can also be read on the right.

Features On Demand (FOD)
Once any features is enabled, if not already existing, it will prompt the update cache location for the FOD CAB cache.
For example in the case of Windows 11, the FOD cache subdirectory 11.21H2.x64.FOD is under the Update Cache (see in File – Settings).
Take the correct FOD ISO for the loaded image, in this example: Windows 11 Language and Optional Features LoF ISO, copy its directory ‘LanguagesAndOptionalFeatures’ content to the FOD cache. Then you can enable those features.

Display language integration
For language packs, take the appropriate CAB file from FOD ISO, e.g. Microsoft-Windows-Client-Language-Pack_x64_de-de.cab for 64-bit German, and add it to the Updates page as a normal update.
All the language display packs start with ‘Microsoft-Windows-Client-Language-Pack’.

For other official FOD ISO links, see this post.

Settings
This page contains a list of various settings, tweaks and policies.
Change the option by either double-clicking it, or selecting the value from the drop-down on the right for a given row, or press the first letter of the value.

Services
This page contains a list of services, same as would be in Computer Management – Services.
Tied component for a selected service can be seen in the service description on the bottom.
If a tied component is queued for removal, or a service is known to break installation if misconfigured, the given service row will be disabled.

Extra Services
This page contains a list of driver and hidden services, these are not normally listed in Windows UI and should not be changed unless you know exactly what you’re doing.
It’s here mostly for completion and a general overview of driver payloads.

Unattended
This page automates setup choices for an image, so that the installation can be fully or partially automated.
First enable the page on the upper-left, check the extra options in the toolbar, then set the remaining options on the main list.
All options are queued to be executed on deployment of the loaded image.

Autofill
Set and overwrite available entries with the host machine data, where available, speeding up the process of setting up full automation.

All – fills the entire page and prompts for the first user creation

Windows PE – fills just the boot portion of the setup, leaving the OOBE prompts as set

Reset – resets the whole page back to defaults

Add local account
Create a local user account. Also has the option to enable the built-in Administrator account, and to auto-logon a user.

Join network
Join a network domain or a workgroup.

Configure disk
Easily setup disk partition layout with the recommended BIOS and UEFI presets with templates, or setup individual disk partitions.

‘Disk Template’
When wiping an entire disk, it is recommended to use the disk templates.
Select disk type by clicking on that row, depending if using an UEFI or BIOS machine.
If using a specific disk size, in gigabytes, move recovery image before or after it, button as a green arrow is on the right.
Disk size can also be extended, to use all available space. There is a yellow extend button on the right of the ‘Operating system’ partition.
If main partition is extended, recovery partition can only be before it. To switch back, enter any size for the Operating system partition.
Type 0 for size to remove a recovery partition.

‘Individual partition’
To format, or only automatically install to a particular partition without wiping the entire drive, it is possible with the ‘Individual partition’ option.
Make sure ‘Wipe disk’ is unchecked, set Partition mode to ‘Modify’ instead of ‘Create’.
Under ‘Format’ choose if you want to format it, and check ‘Install to this partition’ if you want to deploy to that one.
One partition has to be selected as the deployment target, or the setup will prompt for partition selection and automation will be lost.
Double check the main Unattended screen by typing in the filter ‘Wipe’, all of those should be set to ‘false’ already.

To restart the disk configuration, select the “Disk Configuration” element and choose Remove from the toolbar.

Be very careful when configuring formatting or wiping, that the disk and partition IDs are correct, maybe even pre-test in a virtual machine configured with the same disk layout.

OEM SetupComplete
When using an OEM product key in Windows 8 and newer, SetupComplete.cmd is normally not executed. Enable this option to include SetupComplete.cmd in the Unattended-RunSynchronous commands to be executed at the end of setup.
This cmd file is also used by the Post-Setup functionality, described below.

Copy to install image
Copy the answer file directly to the final image location (%WINDIR%\Panther\unattend.xml). Use only if directly deploying an image to a partition, without Windows setup.

Copy to boot image
Copy the answer file directly to the setup boot image. Can help machines which otherwise do not apply Unattended settings on booting up this image.

Dual architecture
If using a 64-bit image, this also saves the 32-bit automation entries, and vice-versa. This is helpful when building multiple-architecture, All-In-One images, otherwise not necessary.
This also enables prompting the list of all editions on the image during the setup boot-up, otherwise setup will automatically pick the last configured edition.

Computer Name
Type or select ‘[Prompt]’ to enable changing the computer name through a prompt during Windows setup. Note that this option needs to be applied to each edition on the image, in case you are not installing the loaded/configured one.
Type or select ‘%SERIAL%’ to dynamically insert a computer serial number in its name during install. It can be combined with other letters, e.g. PREFIXHERE-%SERIAL%

On this page Updates, Drivers and Registry

Updates
This page integrates updates to an image, or installs updates to the currently installed system, depending what was loaded as the target on the Source page.
On the right is a list of existing packages in the target, those can be Updates, Language packs and Features.
Make sure to use the Analyze option from the toolbar after queuing all the updates, for any known missing dependencies or compatibility issues.
For EXE installers like .NET Framework or C++, use the Automate – Post Setup page instead, Updates page is just for truly integrate-able packages, extensions like MSU or CAB. Some EXE exceptions are Win7 SP1, WUAgent and IE11, those are supported by the Updates page.

Add – Latest Online Updates
More info.

Add – Templates – .NET Framework 3.5
In order to offline integrate .NET Framework 3.5 in Windows 10/11 images, use this option. It automatically pulls the needed package from the loaded image.

Language packs
More info.

Clean update backup
An option in the toolbar, used to remove the obsolete files, replaced by their updated versions.
It can be useful to significantly reduce the size of the updated target, to fit an image to the FAT32 4GB limit or to simply reduce the size of the installation. It removes the ability to uninstall current updates.
There are 3 modes of operation:
– DISM (Compatible) – in this mode it is using the Windows built-in function to clean updates. While it is the maximum compatible method, in terms of it having the least chances of breaking a future package installation, it can be quite slow and picky on its environment. If it denies to work in your particular target, try the Custom mode (not as compatible with future updates). DISM modes do not support Windows 7.
– DISM (ResetBase) – same as above, plus removes a bit more, with a higher risk of breaking updatability and Windows Reset of Win10 1903 and newer.
– Custom (Complete) – uses the custom engine for cleaning the old versions, while retaining the update compatibility in almost all of the cases. Report any issues and update with Host Refresh tool if stuck.

Update extraction
Depending on repeated sessions, available CPU cores and disk space, choose the integration performance improvement method:
– Standard – one by one update, extracted to temporary files (scratch dir), integrated, then temporary files gets deleted, the way it was done normally.
This requires the least disk space, but it is extracted and deleted on each update, slowest and wastes disk operations if you will use those updates again.
– Parallel extraction – extracts in parallel as many pending updates as CPU cores available (temp dir), because of that temporarily takes more disk space.
Space necessary is the same in total as the standard method, but it’s taken all at the same time to utilize the unused CPU cores.
Integrates one by one (parallel here not possible), then temporary files get deleted only on closing the tool.
The same updates will be reused from the temporary cache without re-extraction if the tool is not closed between sessions.
Cleanup of files is also in parallel for faster performance.
Faster than the standard method.
– Parallel extraction + Cache – same as above, with the differences that the extracted files are stored permanently in the Update extraction cache (File – Settings), and do not get deleted on closing the tool.
This enables much faster integration of the same updates between sessions, and much less wear on the drives.
Cache will be automatically maintained, if an entry from it is not accessed in 14 days, it gets automatically deleted on closing the tool.
To delete the entire cache, either do it manually or use the Erase button next to File – Settings – Update extraction cache.
Note the thousands of files in the cache, seems like a waste to delete reusable extracted packages for those integrating multiple times a month.

Recovery: if a future package installation breaks for any reason, on Windows 10 see up about Start – Tools – Host Refresh, to repair without a full reinstall.

Feature upgrades:
Windows images are designed such that existing image upgrades are only possible in these combinations:
1903 (build 18362) -> 1909 (build 18363)
2004 (build 19041) -> 2009 (build 19042) -> 21H1 (build 19043) -> 21H2 (19044) – and any combination in-between
The entire image package structure is different in that base image build jump from 18362 to 19041.
The offline/image upgrade from 1903/9 to 20H2/21H1/21H2 is not possible with update packages alone as they have a different base version, what you need to do is get the 2004, 2009 or 21H1 ISO.
Latest ISOs can be downloaded from Microsoft here for end users, if you have MSDN subscription, use that to get the oldest 2004 (20H2), then update it with latest updates and feature upgrade of choice.
Already deployed online/live installations follow the same rule, it’s just Windows Update downloads a new ISO in the background for those bigger jumps.
You can also use Host Refresh in that case to upgrade with an already adapted ISO.
Note that packages update images, while images cannot update images, they replace them.

Drivers
This page integrates drivers to an image, and can be used to check if all the needed drivers are covered for the loaded target.
Supported drivers are in the INF format, with the accompanying files in the folder as they came originally in the package.
You can import drivers from the host, or download from the internet.
If the driver is only available in the EXE format, extract it first – the method depends on the driver, sometimes just a switch, if you cannot find how, contact us.

Hardware list
Contained in an XML file which can be exported from any machine running the tool and using the File – Export Hardware List option.
To add another machine’s hardware list, use the Import button on the toolbar of the Drivers page, then select that machine from the drop-down.
This machine list is also reflected on the Components page, Compatibility list, to easily protect needed drivers for the targeted machine if removing components.

Reuse driver cache
An option in the toolbar, used to reduce the effective Windows size, utilizing NTFS links between identical driver files in cache and where deployed (e.g. System32). Most space saved when used on Live deployments with installed drivers.

Registry
This page applies registry (.reg) file content directly to an image, and provides an easy way to manually edit registry hives on the image.
It will automatically translate registry key paths to an appropriate location, just use it as a normal reg file.
HKEY_CURRENT_USER subkeys will be applied to all users.

Post-Setup
This page automates execution of apps and scripts at the end of an image installation, or directly after processing if used live.
Use the Add drop-down in the toolbar to add files, commands or see existing templates.
A file can be an installer, or a passive file, type of each can be seen in the Type column.
There are two boxes and toolbar tabs on the page, Machine and User. Machine entries run at the end of setup, before users are created, while User entries are ran on the first user logon.
It is recommended to use the User box, unless needed differently.
Machine tasks are ran elevated, and User tasks will also be elevated if the logged on user is an admin.
Note that if using an OEM product key, and Machine list does not run by default.
You can then enable the Unattended page – toolbar – OEM SetupComplete option.

Installers will be automatically copied and executed during deployment, then deleted from the temporary location.
Make sure all the installers have their correct silent switches set in the Parameters box, otherwise the installation will hang at the login screen if using a Machine list.
If installers have prompts, or require an existing user, use the User install queue instead (the lower box on the page, also as a User tab in the toolbar).

Registry (.REG) files will be automatically copied and applied at the end of setup.
While at first seems the same as Integrate – Registry, the difference is the real integration puts it directly in the image registry hives, while this one is delayed-applied at the end of Windows setup.
Reason being there are certain rare registry keys that are either reset during setup, or break the setup.

Passive files will not be executed, just copied and deleted after all the installers are done.
You can use passive files in the installer parameters, syntax listed on the passive file’s Parameters box as read-only ready for copying.

Common
Directory subscription
Each of these pages have the option to Add – Directory containing relevant files, or Subscribe to such a directory.
While adding a directory once adds the files from it, he Subscribe option adds the link to the folder itself instead.
Such subscription refreshes the file list in that directory on preset reload or pressing Refresh on the toolbar for that page.
This can be useful when maintaining your own list of update, drivers or tweaks in a directory structure, or using NTLite in a script to reduce the need to adapt presets to new integration steps.

To see the list of subscribed directories, position the mouse over the Refresh button to see the tooltip.

To unsubscribe from a directory, right-click on any file from the said directory and choose Remove directory.
Remove directory will also remove any other files from that directory.
You can also manually edit the preset file before loading it and remove or change the relevant Directory elements.

Apply
This page contains the final image processing options, the full list of pending changes, and the Process button to start applying all the queued changes to the loaded target.
Before actually pressing the Process button, review the pending changes on the right, and do some final choices on this page.

Saving mode
Choose between:
– Save the image, just saves the changes to the loaded edition, keeps the other ones.
– Save the image and trim editions, saves the changes and deletes other editions on the image, this can save a lot of space on the actual image if you don’t need other editions.
– Stop before saving the image, this applies the changes to the mount directory only, changes will not be saved to the actual image until you unload and tick save changes, or reapply in another session.
This is useful when doing multiple sessions to not need to wait for saving and remounting each time.

Remove non-essential editions
Provides the ability to manually select which editions to remove. You can also manually remove editions on the Source page directly by right-clicking it and choosing Delete.

Image format
When saving an image, choose the format.

Image process queue
With this option, selected current tasks can be multiplied to the other editions on the loaded image, not needing to manually do so for each edition.
For example you can select to integrate a driver to install.wim and also to boot.wim, or the same updates for Home and Pro edition, in one session.

Options
Create ISO option automates ISO creation at the end of the process. By ticking the checkbox you will be asked for a file destination.