🛡️

Windows Server 2025 Unattended Install: What Changed

Server 2025 quietly changed the unattended-install rules: HideLocalAccountScreen is now required, ProtectYourPC changed values, the image name format is different, and domains need functional level 10.

Answer files that deployed Server 2019 and 2022 flawlessly can stall or go interactive on Server 2025 — Microsoft changed several unattended-setup requirements without much fanfare. Here’s each change, the symptom it causes, and the fix. (Our Server Build Wizard applies all of these automatically when you select 2025.)

1. HideLocalAccountScreen is now required

Symptom: the install runs unattended right up to OOBE, then stops and waits at the local administrator account screen.

On Server 2022 this OOBE setting was optional; on Server 2025 the account screen appears even when the administrator password is fully specified in the answer file — unless you explicitly hide it.

oobeSystem pass — Microsoft-Windows-Shell-Setup

<OOBE>
    <HideEULAPage>true</HideEULAPage>
    <HideLocalAccountScreen>true</HideLocalAccountScreen>
    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
    <ProtectYourPC>1</ProtectYourPC>
</OOBE>

2. ProtectYourPC changed from 3 to 1

The privacy/express-settings value that worked on 2019/2022 (3) can cause OOBE to prompt on 2025. Use 1 (express settings, recommended defaults) in the 2025 answer file — see the XML above.

3. The install image name format changed

Symptom: setup can’t find the specified image and asks which edition to install.

If your answer file selects the image by name, the 2025 media names it differently:

Server 2022: Windows Server 2022 SERVERSTANDARD (or select by index)
Server 2025: Windows Server 2025 Standard (Desktop Experience)

Match the string exactly — including “(Desktop Experience)” for GUI installs. Selecting by index instead of name also sidesteps the rename entirely.

4. New forests and domains: functional level 10

Promoting a 2025 domain controller into a new forest uses domain/forest functional level 10 (Windows Server 2025). The WinThreshold value used in 2016–2022 promotion scripts still works only for mixed environments — for a clean 2025-only build, specify 10:

Install-ADDSForest excerpt

$ForestLevel = "10"   # Windows Server 2025 (use "WinThreshold" for 2016-2022)
$DomainLevel = "10"

Install-ADDSForest `
    -DomainName $DomainName `
    -ForestMode $ForestLevel `
    -DomainMode $DomainLevel `
    -InstallDns `
    -SafeModeAdministratorPassword $SafeModePassword `
    -Force

Functional level 10 is one-way

A forest at level 10 only accepts Server 2025 domain controllers. If you still need 2019/2022 DCs in the same domain, promote at WinThreshold instead and raise the level later.

Skip the archaeology

The Server Build Wizard generates the full 2025-compatible package — answer file with the required OOBE section and image name, plus the domain-promotion scripts with the right functional levels — from a five-step form. Select 2019 or 2022 and it generates the older formats instead.

Open the Server Build Wizard

Tools used in this guide

💻

Windows Server Build Wizard

Guided wizard for automated Windows Server 2019/2022/2025 deployments. Generates answer files, PowerShell configuration scripts, and a ready-to-use ZIP package.

📄

Answer File Generator

Create customized autounattend.xml files for automated Windows 11 installations. Configure privacy, remove bloatware, and customize the interface.