A normal Windows install answers questions for half an hour. A prepared install answers none — every answer was given in advance, on your desk, once. That preparation is the whole trick, and this guide explains both real methods honestly.
There is no magic installer that makes Windows set itself up in three minutes from nothing. What exists — and what the video demonstrates — is deployment: you do the slow thinking once, save it as a file or an image, and after that each install is just the machine copying and expanding files as fast as its SSD allows. On a modern NVMe drive, that copying phase genuinely can finish in a few minutes. This guide covers the two documented methods behind every fast install, what each one needs before the timer starts, and where the honest limits are — drivers, activation and updates do not disappear, they just move to a different stage.
A standard install USB already knows how to work unattended. When Windows Setup starts, it looks for a file named autounattend.xml in the root of the USB drive. If it finds one, it reads your pre-written answers instead of asking: language and keyboard, which disk to use and how to partition it, whether to skip the product key screen, and the first-run (OOBE) choices like account screens and privacy toggles.
The file is plain XML text. Microsoft builds it with the Windows System Image Manager from the free ADK toolkit, but a carefully written text file works the same. The honest part: writing and testing a good answer file takes a first evening, not three minutes. You pay that time once and recover it on every install afterwards.
The second route skips Setup almost entirely. You first build one perfect Windows on a reference PC — installed, updated, with the common apps your machines need — then capture its drive into a single image file. On each new PC you boot from USB, partition the disk, and expand that image onto it:
dism /Apply-Image /ImageFile:D:\install.wim /Index:1 /ApplyDir:C:\ — expands the image onto the target partitionbcdboot C:\Windows — writes the boot files so the machine starts from the new WindowsStep one is a straight file copy at SSD speed — this is the phase that fits inside a few minutes on fast hardware. There is no per-screen waiting because there are no screens.
A captured image cannot simply be a raw clone of your working PC. Every Windows installation carries machine-specific identity — a unique security ID, the computer name, hardware-specific setup state. Microsoft's supported way to prepare an image for other machines is Sysprep: run sysprep /generalize /oobe /shutdown from C:\Windows\System32\Sysprep before capturing. Generalize strips the machine-specific parts so each new PC generates its own identity on first boot.
Deploying an unprepared duplicate is the shortcut that causes the classic problems: identical machine identities on a network, odd update behaviour, and activation confusion. The video-class workflow done properly always includes this step.
Reaching the desktop quickly is not the same as a finished PC. After either route, three things still need their turn, and no honest guide skips them:
One PC, occasionally: the answer file is enough. It keeps the install 100 percent standard — Setup does everything, just without asking you questions — so there are no image-maintenance duties afterwards.
Same setup on many PCs, or repeated reinstalls: the image route wins. The preparation is heavier, but every deployment after the first is minutes of copying, with your apps already inside. Offices and technicians who reinstall weekly live on this route. The rest of this guide series takes each part — the honest timing, the answer file, sysprep, drivers, activation and upkeep — in depth.
The full fast deployment method — preparation and install — shown live, step by step.
▶ Watch Full VideoThe deployment phase is real: applying a prepared image to a fast NVMe SSD, or running Setup with a complete answer file, can reach the desktop in a few minutes. What the figure does not include is the one-time preparation — building the answer file or the golden image — nor the drivers, activation and updates that follow on each machine.
No. Both methods work with the standard Windows ISO from Microsoft. The speed comes from the answer file or the prepared image, not from a cut-down system. Modified ISOs from download sites are a security risk and are not needed for a fast deployment.
A properly generalized (sysprep) image boots on most hardware because Windows re-detects devices on first boot. Storage drivers are the main exception: if the target machine's disk controller has no driver in the image, it will not boot until that driver is added. Activation is always per machine, whatever the image contains.