Answer File Gotchas

1. Wrong file name or location

For boot media (USB/ISO), the file must be named exactly autounattend.xml and sit in the root of the drive — not in a folder, and not named unattend.xml (that name is used for a different stage, like Sysprep).

• E:\autounattend.xml — correct
• E:\Setup\autounattend.xml — ignored
• E:\Autounattend.xml.txt — ignored (watch for hidden file extensions in Explorer!)

2. Settings in the wrong configuration pass

Every setting in an answer file belongs to a specific configuration pass (windowsPE, specialize, oobeSystem, etc.), and Setup only reads a setting during its pass. A perfectly valid setting in the wrong pass is silently ignored.

• Disk partitioning, product key, image selection → windowsPE
• Computer name, most registry/system tweaks → specialize
• User accounts, auto-logon, OOBE/privacy screens → oobeSystem

If you use the Answer File Generator, settings are already placed in the correct passes — this gotcha mainly bites when hand-editing.

3. Wrong processor architecture attribute

Every component element carries a processorArchitecture attribute. Copy-pasted snippets from old forums often say x86, and ARM devices need arm64 — on a standard Intel/AMD machine every component must say amd64 or it is skipped without warning.

4. Password encoding surprises

Passwords in answer files are Base64 — but not of the password alone. The string is the password with a literal suffix appended before encoding:

• AdministratorPassword → Base64 of yourpassword + AdministratorPassword
• User account Password → Base64 of yourpassword + Password

Hand-encoding just the password produces a logon failure loop after install. Generators (including ours) handle this automatically — if you edit a password by hand, re-encode it with the suffix.

5. FAT32 broke your USB before Setup even started

Not strictly an answer-file problem, but it presents like one: modern install.wim files exceed FAT32’s 4GB limit, so a manually-built USB either fails the copy or boots with a broken sources folder — and the install never gets far enough to read your answer file.

Split the WIM with DISM as shown in the ISO Builder Guide.

6. Edition and image selection mismatches

If the answer file specifies an edition (via product key or InstallFrom metadata) that doesn’t exist in the image, Setup falls back to asking interactively. Two common causes:

• Media Creation Tool ISOs contain multiple editions — a generic Pro key selects Pro, but a typo’d key selects nothing
• Enterprise/Education editions aren’t in consumer ISOs at all

7. TPM/Secure Boot bypass keys in the wrong place

The popular registry bypasses (BypassTPMCheck, BypassSecureBootCheck, BypassRAMCheck) only work when they run in the windowsPE pass before Setup’s hardware compatibility check. Placed in specialize or as FirstLogonCommands, they do nothing — the install already refused to start.

8. How to actually debug an ignored answer file

When an install goes interactive instead of automated, check the Setup logs — they state whether an answer file was found and which one:

Skip the gotchas entirely

The Answer File Generator produces a correctly-structured autounattend.xml with valid passes, architecture attributes, and password encoding — and the Step-by-Step Deployment wizard walks the whole process end to end.