UnattendedWinstall is a free, open-source answer file that automates the debloating and optimization of Windows during installation. Download the autounattend.xml from the UnattendedWinstall GitHub page, add it to your Windows installation media, and install Windows normally — the answer file removes bloatware, disables telemetry, bypasses hardware requirements, and configures a clean, optimized system before you even reach the desktop.
Applies to: Windows 10 (22H2) and Windows 11 (23H2, 24H2, 25H2) — all editions | Last updated: April 2, 2026
Key Takeaways
- UnattendedWinstall is an answer file (autounattend.xml) that runs during a clean Windows install. It removes Edge, OneDrive, Copilot, Widgets, and pre-installed bloatware apps automatically — you get a clean desktop with a lower process count the moment you log in.
- The answer file works with official Windows ISO files downloaded directly from Microsoft. Nothing is modified in the ISO itself — the XML file just tells Windows Setup what to configure, making it completely safe and transparent.
- Four methods to use it: Winhance WIMUtil (recommended — also injects drivers), AnyBurn custom ISO, USB root directory, or Ventoy Auto Install plugin.
- The file is fully editable. Open it in any text editor to remove or add tweaks before installation. Use Ctrl+F to search for specific entries like “notepad” or “edge” and remove what you want to keep.
- If you already have Windows installed and want similar optimization without reinstalling, use the Chris Titus Tech Windows Utility instead — it applies the same types of tweaks to an existing installation.
Quick Steps
- Download autounattend.xml from the UnattendedWinstall GitHub page
- Add the XML file to your Windows installation media (USB root, custom ISO, or via Winhance WIMUtil)
- Boot from the installation media and install Windows normally
- The answer file runs automatically — scripts flash briefly during setup phases
- At the desktop, use the “Install Winhance” shortcut to set up your browser and additional software
In This Guide
This guide covers what UnattendedWinstall does, how the answer file works, and four methods to use it:
- What Is UnattendedWinstall? — How answer files work and what this one does
- Method 1: Winhance WIMUtil — Recommended. Creates a custom ISO with drivers and the answer file. (Recommended)
- Method 2: AnyBurn Custom ISO — Embed the XML into a Windows ISO file
- Method 3: USB Root Directory — Copy the XML to a bootable USB drive
- Method 4: Ventoy Auto Install Plugin — Auto-associate XMLs with ISOs on a Ventoy drive
What Is UnattendedWinstall?
UnattendedWinstall is an open-source project I created that provides a pre-configured Windows answer file — an XML file called autounattend.xml that automates and customizes the Windows installation process. Microsoft designed this feature for corporate environments to make mass deployments easier, but it works just as well for individual users who want a clean, debloated system without manual post-install tweaking.
The project has over 5,700 stars on GitHub and the launch video has over 1 million views — it clearly hit a nerve with people who are tired of the stock Windows experience. My motivation was to get an LTSC-like experience on the Pro and Home editions of Windows without needing an LTSC license.

What the Answer File Does
The answer file executes commands during three phases of Windows Setup:
- Windows PE (Pre-Installation) — Bypasses hardware requirements (TPM 2.0, Secure Boot, RAM, CPU, and storage checks) so you can install Windows 11 on unsupported hardware.
- Specialize Phase (First Boot) — This is where most of the work happens. Registry tweaks, PowerShell scripts, bloatware removal, telemetry disabling, and service optimization all run here. It includes some of the same scripts from the Chris Titus Tech Windows Utility.
- OOBE (Out-of-Box Experience) — Skips the Microsoft Account prompts, allows local account creation, and applies user-specific registry values. Some registry entries from the Specialize phase get reset when a new user profile loads, so this phase re-applies them.
During installation, you will see command prompt and PowerShell windows flash briefly — that is the answer file running its scripts. Leave the computer alone and let it finish. Your PC will restart a couple of times before reaching the desktop.
Why Use an Answer File Instead of a Custom ISO?
The answer file is added to the official Windows ISO downloaded directly from Microsoft — the Windows image itself is not modified. This means you can inspect every change before installation by reading the XML file, you are not downloading a custom ISO from an unknown source, and the process uses an official Microsoft feature designed for exactly this purpose. You can also edit the file to add or remove specific tweaks before using it.
Tip: The answer file is intentionally aggressive — it removes almost everything except Windows Security. The idea is to start with a blank canvas and add back what you need, rather than trying to remove things one by one. If you want to keep something (like Notepad or the Calculator), open the XML in a text editor, search for that entry with Ctrl+F, and delete the lines that remove it.
Method 1: Winhance WIMUtil (Recommended)
The best way to use UnattendedWinstall is through Winhance‘s WIMUtil feature. This creates a custom Windows ISO with the answer file embedded, and it also lets you inject system drivers into the image — which means Windows will detect all your hardware on first boot without needing to manually install drivers afterward.
- Open Winhance and navigate to Advanced Tools > WIMUtil
- In Step 1, select and extract a Windows ISO file
- In Step 2, click “Download UnattendedWinstall XML” to automatically download the latest version from GitHub (or generate a custom Winhance XML with your exact selections)
- Extract and add your system drivers to the image
- Create the new ISO file
- Copy the ISO to a Ventoy flash drive and boot from it to install
Winhance can also generate its own answer file based on your exact selections, which gives you more flexibility than editing the XML manually. For a detailed walkthrough of WIMUtil, see my clean Windows 11 install with WIMUtil guide.
Method 2: AnyBurn Custom ISO
If you want a simple approach without Winhance, you can embed the answer file directly into a Windows ISO using AnyBurn (free):
- Download the autounattend.xml from the UnattendedWinstall GitHub page
- Download your preferred Windows ISO from Microsoft (Windows 11 or Windows 10)
- Open AnyBurn and select “Edit Image File”
- Select the Windows ISO, click Add, and add the autounattend.xml file to the root
- Click Next > Create Now and overwrite the original ISO when prompted
- Use this modified ISO to install Windows — either via Ventoy, Rufus, or a virtual machine

Method 3: USB Root Directory
The simplest method if you already have a bootable Windows USB drive:
- Create a bootable Windows USB using Rufus or the Media Creation Tool
- Download the autounattend.xml from the UnattendedWinstall GitHub page
- Copy the XML file to the root of the USB drive (alongside the setup.exe and other files)
- Boot from the USB and install Windows normally — the answer file is detected and applied automatically
Warning: If you use Rufus, do NOT check any of the boxes in the “Customize Your Windows Experience” dialog — those create a separate answer file that will conflict with UnattendedWinstall. Leave all Rufus customization options unchecked.
For a detailed walkthrough of both the USB and AnyBurn methods, watch the full tutorial video below:
Method 4: Ventoy Auto Install Plugin
If you use Ventoy and keep multiple Windows ISOs on the same drive, you can set up the Auto Install Plugin to automatically associate answer files with specific ISOs. Create a folder structure like ISO\Windows\ for your ISOs and Templates\ for your XML files, then configure Ventoy’s plugin to link them. This is the most advanced method but saves time if you frequently install different Windows versions.
What to Expect During Installation
When you boot from the installation media, command prompt windows will flash briefly before the first setup screen — that is the Windows PE phase bypassing hardware requirements. Proceed through the normal installation prompts (select drive, choose edition, etc.).
After the initial file copy and reboot, you will see more PowerShell and command prompt windows during the Specialize phase. This is where the bulk of the debloating and optimization scripts run. Do not interrupt this — let it finish. Your computer will restart once or twice more.
During the OOBE phase, you will be prompted to create a local account (no Microsoft Account required). Select your region, keyboard layout, and username. After the final reboot, a script runs one more time to apply user-specific registry values, and then you are at the desktop.
The result is a clean Windows installation with no Edge, no OneDrive, no bloatware in the Start menu, telemetry disabled, and a significantly lower background process count. Since there is no browser installed, use the “Install Winhance” shortcut on the desktop to launch Winhance and install your browser and any other software you need.
How to Customize the Answer File
The answer file is intentionally over-tweaked — it removes almost everything. You can edit it before adding it to your installation media to keep specific features or apps.
Open autounattend.xml in any text editor (VS Code, Notepad++, or even the default Notepad). Use Ctrl+F to search for the name of whatever you want to keep — for example, searching “notepad” will show you the entries that remove it. Delete those lines and save the file.
If you want to create your own answer file from scratch with specific settings, I have a detailed guide on how to create an unattended answer file for Windows 10 and 11. You can also use the Schneegans unattend generator website to create a custom answer file with a visual interface.
Note: I do not provide support for custom modifications to the answer file. If you edit the XML and something breaks during installation, you will need to troubleshoot it yourself or revert to the original file.
Frequently Asked Questions
Is UnattendedWinstall safe to use?
Yes. The answer file is added to the official Windows ISO from Microsoft — the Windows image itself is not modified. You can read the entire XML file before using it to see exactly what changes it makes. The project is open source on GitHub with over 5,700 stars, and the code is publicly auditable.
Does this work on Windows 10 and Windows 11?
Yes, the answer file works on both Windows 10 (22H2) and Windows 11 (23H2, 24H2, 25H2). It has been tested on both Pro and Home editions. The hardware bypass section is only relevant for Windows 11 on unsupported hardware — on Windows 10 or supported Windows 11 hardware, those commands simply have no effect.
Why does it say “some settings are managed by your organization”?
This is normal and expected. The answer file applies some settings through Group Policy-style registry entries, which triggers that message in Windows Settings. It does not mean your PC is managed by anyone — it just means certain settings have been locked by the answer file’s registry tweaks.
What is the difference between UnattendedWinstall and the Chris Titus utility?
UnattendedWinstall runs during a fresh Windows installation — you start with a clean, optimized system from the beginning. The Chris Titus Tech Windows Utility optimizes an existing Windows installation where you already have your files and software. Use UnattendedWinstall for fresh installs and the Chris Titus utility for existing ones.
Can I undo the changes after installation?
Most changes can be reversed by reinstalling the removed apps from the Microsoft Store or re-enabling settings in Windows. However, there is no single “undo” button. If you want more control, edit the answer file before installation to only apply the tweaks you actually want.

I found your video and was very impressed that you liked and included part of Chris Titus Utility scripts.
I thought you should know that, in my case, I create a bootable usb drive with a Windows iso file with Rufus but, Windows would not allow me to “just drop the autounattended.xml onto the created Rufus usb drive. There is a report of “no space”.
I moved onto the Anyburn app and created my autounattended iso image per your instructions.
Thanks for your work on this, I greatly appreciated it.
how get the ikon that the answer file have
Just a heads up that Win11 IoT 2024 LTSC Enterprise REALLY didn’t like the autounattend.xml file here:
https://github.com/memstechtips/UnattendedWinstall/blob/main/autounattend.xml
Entirely possible that I missed a critical step somewhere, but when I pasted the error output to Claude, it responded with the following:
“Looking at the error log, the Windows installation is failing due to issues with your autounattend.xml file. The key errors are:
**Main Problems:**
1. **Duplicate settings**: “A component or non-list setting is specified more than once in the answer file”
2. **Namespace issues**: “Unable to find a component matching the given namespace” and “The same namespace should not appear twice in a single settings section”
3. **Validation failure**: Error code `0x8022001b during the specialize pass
**Common Causes:**
1. **Duplicate components** – You may have the same component (like `Microsoft-Windows-Shell-Setup`) appearing multiple times in the same configuration pass
2. **Wrong or duplicate namespaces** – Components might reference incorrect or duplicate XML namespaces
3. **Settings in wrong passes** – Some settings might be in both `oobeSystem` and `specialize` passes when they should only be in one
4. **Typos** – Component names or settings might have spelling errors
**To fix this, I’ll need to see your autounattend.xml file.** Can you share it? Then I can:
– Identify the duplicate components/settings
– Fix namespace issues
– Ensure settings are in the correct configuration passes
– Validate the XML structure
You can upload the file or paste its contents here, and I’ll help you create a corrected version.”
Once I used Claude’s corrected XML file, the install worked without any issues. Happy to provide more details if you want, but just thought you should know. Thx!
Hey there and thanks for reporting this, I will look into it.
Ehh im stuck on password which I don’t know
The install doesn’t use a password, if it asks for a password, it is one you set up yourself.