Generate Autounattend.xml for Windows 11, 10 & Server
Easily generate autounattend.xml and unattend.xml answer files to automate Windows 10, Windows 11, and Windows Server deployments. Configure local accounts, disk partitions, bloatware removal, and directly download the configuration as an .xml or bootable .iso file.
Target Windows Version
Selecting the version filters available Editions and hides irrelevant options (e.g., Taskbar Alignment hidden for Windows 10).
Quick Configuration
Region & Product
Licensing
Key: W269N-WFGWX-YVC9B-4J6C9-T83GX (Generic Volume License Key)
How to use autounattend.xml
Windows Setup automatically searches for answer files named autounattend.xml in the root of removable media. Using this file allows you to bypass the Out-of-Box Experience (OOBE), automate partitioning, and apply tweaks without modifying the original Windows image.
Method 1: Physical Hardware (USB)
- Configure your settings in the generator and click Download .xml.
- Create a standard bootable Windows USB installer (using Microsoft Media Creation Tool or Rufus).
- Copy the downloaded
autounattend.xmlfile to the root directory of that USB drive (e.g.,D:\autounattend.xml). - Boot the computer from the USB drive. Windows Setup will detect the file and proceed automatically.
Method 2: Virtual Machines
Simply click the Download ISO button to get an
autounattend.iso file. Mount this as a second CD/DVD drive in your VM alongside the Windows Installer ISO. VMware Workstation
- Create your VM, selecting "I will install the operating system later".
- Edit VM Settings. Put the standard Windows ISO in the first CD/DVD drive.
- Click Add... -> CD/DVD Drive.
- Select "Use ISO image file" and browse to your
autounattend.iso. - Power on the VM.
Oracle VirtualBox
- Create your VM. Important: Check "Skip Unattended Installation" in the summary to prevent VirtualBox from using its own defaults.
- Go to Settings -> Storage.
- Next to the Controller, click the Add Optical Drive icon.
- Select your
autounattend.iso. - Start the VM.
Proxmox VE
- Upload
autounattend.isoto your Proxmox ISO storage. - Create a VM. Attach the Windows ISO to the CD/DVD drive.
- After creation, go to Hardware -> Add -> CD/DVD Drive.
- Select your
autounattend.iso. - Ensure Boot Order prioritizes the Windows Installer, then start.
Hyper-V
- Create your VM (Generation 2 recommended).
- Go to Settings.
- Under SCSI Controller, select DVD Drive and click Add.
- Image file: Browse to
autounattend.iso. - Start the VM.
Parallels Desktop
- Create VM -> "Install Windows... from a DVD or image file".
- Uncheck "Express Installation" if prompted.
- Go to Hardware settings.
- Click (+) -> CD/DVD.
- Connect to
autounattend.iso.
Troubleshooting & Log Files
The answer file works with standard Microsoft ISOs (Windows 10/11, including 24H2). If the installation fails or stops unexpectedly, you can debug it by pressing Shift + F10 during setup to open a Command Prompt and checking these logs:
| Stage | File Path | Purpose |
|---|---|---|
| Boot (WinPE) | X:\Windows\setupact.log | Check this if your autounattend.xml is ignored entirely. |
| Disk/Partition | X:\diskpart.log | Contains output from the drive wiping/formatting script. |
| Installation | C:\Windows\Panther\setupact.log | Errors occurring after the first reboot (OOBE). |
| Custom Scripts | C:\Windows\Setup\Scripts\*.log | Output from your PowerShell scripts, user creation, and bloatware removal. |
 ) to prevent parsing errors. Reverting Customizations
Some "Advanced" tweaks modify the registry or scheduled tasks. To restore default Windows behavior, run the corresponding command in an Administrator PowerShell window.
Re-enable UAC (User Account Control)
Restore Win11 Modern Context Menu
Reset NumLock/Capslock Behavior
Reset Tray Icon Visibility
Enable 'Manage Devices' in Settings
Reset Execution Policy
Security Considerations
- Windows Setup caches the answer file to
C:\Windows\Panther\unattend.xml. - If you configured Wi-Fi, the profile is often stored at
C:\Windows\Setup\Scripts\Wifi.xml.
Our generator includes scripts to attempt deletion of these files, but you should verify they are gone before sharing the machine image.
