AUTOUNATTEND.XML GENERATOR
A system ready
from the first minute.
Tick the settings you need and AutoWin builds the answer file that Windows reads during installation. Telemetry, interface, services and the account are configured before you ever see the desktop.
CONFIGURATION
selected 0
Account and installation
Windows cannot accept an encrypted password: the answer file stores it in plain text. The file stays both on the drive and in the installed system — if the password matters, wipe the drive and delete C:\Windows\Panther\unattend.xml.
Hardware requirements
Language and computer name
Privacy
Ads and recommendations
File Explorer
Taskbar and appearance
Performance
Components and services
Network
Security — for the experienced
These settings strip out protection built into Windows. Switch them on only if you understand the consequences and know what you will protect yourself with instead.
Ready to build
The file is built right in your browser. Nothing is sent to a server — your settings never leave the computer.
WINDOWS IMAGES (x64)
Windows 10
Original Microsoft imageSHA-2562a7c440c984eb018f513901e8ed96405213d237938c410c5089c0fac7ba01898
Windows 11
Original Microsoft imageSHA-256e1efe78f43a1e059912fc600bbcecac349a33f8bb7b1562b0a2966c31e9674bc
The images are published unchanged. To make sure, compute the checksum with certutil -hashfile file.iso SHA256 and compare it with the one given. If it does not match, the file was damaged during the download; get it again.
How to use it
Take the original image
Only a clean ISO from Microsoft will do. Third-party builds carry answer files of their own that will conflict with ours. After downloading, check the checksum.
Write the flash drive
Use Rufus to write the image to a drive of 8 GB or more. Partition scheme GPT, file system NTFS.
When Rufus offers to apply its own settings, clear every box. Otherwise it puts its own answer file on the drive and ours stops being read.
Put the file in the root of the drive
The downloaded autounattend.xml has to sit at the top level of the drive, next to setup.exe. Not in the sources folder and not in boot — the installer looks for it only in the root.
Test on a virtual machine first
Before putting the system on a working computer, run the installation through VirtualBox or VMware. That way you see the result of your settings while risking nothing.
Installation
Boot from the drive through the Boot Menu — usually F8, F11 or F12 at power-on. The installer will still ask about the disk layout: we deliberately do not automate that step, to rule out deleting data by accident. The rest goes by itself.