The first four sections of Winhance fix a machine after Windows is installed. Advanced Tools is about never having to. WIMUtil customizes an installation image, and the autounattend generator writes a setup answer file from the same toggles you would otherwise click one at a time.
Together they turn "three hours per laptop" into "put the stick in, come back later". Here is my build process, and the parts that took me two attempts to get right.
Why bother
If you set up one machine a year, do not bother. The break-even point is somewhere around the fourth identical install. Below that, clicking through the app is faster than building an image.
Above it, the math changes fast — and more importantly, the result becomes consistent. Every machine from the same image has the same settings, the same missing bloat and the same drivers. When something behaves oddly, "is this one different?" stops being a question you have to answer.
Sourcing the base image
Start from a genuine, current Microsoft ISO. Not a "pre-debloated" image from a forum, not a torrent, not something a YouTube description linked to. You are about to base every machine you touch on this file; provenance is the entire point.
Get-FileHash against Microsoft's published value before you use it. It takes thirty seconds and it is the only step in this whole process that protects you from a compromised base.Use the most recent feature update available. Building on an older image means every deployed machine immediately pulls a multi-gigabyte upgrade, which defeats most of the time saving.
Driver injection
This is the step that makes fleet deployment actually work. WIMUtil can integrate drivers into the image so that network and storage work at first boot rather than after a manual hunt.
My approach: export the driver store from a known-good machine of the same model, prune it, and inject only what is needed — chipset, network, storage controller. Graphics and peripheral drivers are better left to Windows Update, because injected GPU drivers age badly.
# Export third-party drivers from a working reference machine
Export-WindowsDriver -Online -Destination D:\Drivers\ThinkPad-T14Keep one folder per model. Mixing models into one driver pile produces images that boot everywhere and are clean nowhere.
The answer file
The autounattend generator writes an autounattend.xml based on your current selections in Winhance. That is the clever bit — you configure a machine the way you like it, in the interface, and then export the configuration as something Windows Setup can apply during installation.
What it removes from the process: the out-of-box experience questions, the region and keyboard prompts, the online account requirement dance, and the initial round of privacy toggles. What it does not remove: your responsibility to check what is in the file before you deploy it. Open it in a text editor. It is XML, it is readable, and reading it once teaches you more about Windows Setup than any guide.
Building and testing
Assemble the image
Base ISO in, drivers injected, answer file placed at the root of the media. WIMUtil handles the image format conversion and the bootable ISO creation.
Boot it in a VM first
Every single time. A virtual machine costs you nothing and catches the answer file syntax error that would otherwise strand you at a setup prompt on real hardware.
Watch the whole first install
Sit through it once. You are looking for prompts that still appear, which tells you which sections of the answer file are not doing what you assumed.
Then test on the real model
VMs do not surface driver problems, secure boot quirks, or the OEM partition layout. Test on the actual laptop before you build twelve.
Write the build date on the stick
Sounds trivial. Six months later, when there are three USB sticks in the drawer, it is the difference between a deployment and an archaeology session.
Gotchas that cost me an evening
- Answer file location. It must be at the root of the installation media for Setup to find it automatically. I put it in a subfolder the first time and spent forty minutes wondering why setup was asking me questions.
- Secure Boot and unsigned injected drivers. If an injected driver is not properly signed, the install may complete and the device may then be dead on arrival. Signed drivers only.
- ISO size and FAT32. Large install images exceed the 4 GB per-file limit on FAT32 sticks. Either split the WIM or format the stick appropriately.
- Image staleness. Rebuild quarterly. An image that installs a nine-month-old build is an hour of updates waiting to happen on every machine.
What still has to be done by hand
Honestly, less than I expected — but not nothing. Per-machine naming, joining whatever network or account structure applies, licensing checks, and the physical stuff: BIOS settings, firmware updates, and confirming the battery is not swollen, which no answer file will do for you.
The tool's own documentation covers its individual options in more detail than I do here. This post is the workflow around it — the order, the tests and the mistakes.
Written by Joseph Savastano. Measurements come from my own machines and are not a promise about yours. Corrections are welcome and get published — send one.