Skip to content

Windows 11 clones park at the OOBE account screen: the clone's unattend has no AutoLogon #1092

Closed

Description

@Gerrrt

Symptom

After a domain rebuild, the two Windows 11 endpoints — carbuncle (154) and siren (155), cloned from template 911 — sit at the OOBE "set up a user account" screen and never reach a logon screen. The Server 2025 guests (DCs, titan, ramuh, from 912) are unaffected.

It is cosmetic, not a build failure

The rest of Setup completes and all automation runs; only the interactive OOBE front-end is stuck. On carbuncle, read through the guest agent while it was parked:

So the guest is fully domain-joined and reachable; what's wedged is the first-logon UX. It bites only when someone wants an interactive console/desktop on a Win11 endpoint (e.g. to run a collector locally) — there's no real user to log in as, and the parked page won't let you pick the built-in Administrator.

Root cause

scripts/sysprep.ps1 deliberately strips the build's autologon ("so nothing logs in on the generalised image"). The clone answer file packer/windows/unattend-oobe.xml.pkrtpl therefore has no <AutoLogon> — only HideLocalAccountScreen=true plus the enabled built-in Administrator.

On Windows 11 client, that is not enough to finish the OOBE account page: without an AutoLogon or a created local user, OOBE idles as defaultuser0. The build answer file (autounattend.xml.pkrtpl) completes precisely because it does carry <AutoLogon> (Administrator, LogonCount 1) — its own comment says "AutoLogon once is what runs bootstrap.ps1." Server 2025 OOBE proceeds to the logon screen without a user, so 912-based guests don't park.

Fix

Give the clone's oobeSystem a one-shot <AutoLogon> for Administrator (LogonCount 1), with FirstLogonCommands that turn autologon off and drop the plaintext DefaultPassword Setup writes to Winlogon. The generalised image still never autologins (sysprep.ps1 unchanged); only the clone's single OOBE pass does, then disables itself — mirroring the proven build path. Draft PR attached.

It needs a 911 template rebuild (packer build, ADR-0074) and a domain rebuild to take effect, which is the lab-pipeline flow's to run — hence the PR is a draft until a rebuilt 911 clone is seen landing at a normal logon screen.

Context: ADR-0074, #440, #774.

Found while trying to run a collector on carbuncle for #451.

Activity

  1. added
    bugSomething isn't working
    labstacks/lab on alexander (VLAN 30)
    on Oct 8, 2026
  2. Gerrrt commented on Oct 9, 2026

    @Gerrrt
    OwnerAuthor

    Verified on the rebuilt 911, 2026-10-09

    #1093 merged as ba39b65, and 911 was rebuilt from main (packer build -force, 1h15m). Then:

    • packer-smoke.sh 911 --keep: every check passed, including "Panther answer files scrubbed (Win clones leave the build password in plaintext at C:\Windows\Panther\unattend-original.xml, readable by Users #1099)".
    • The kept smoke clone (999), checked after first boot:
      • OOBEInProgress=0;
      • AutoAdminLogon=0;
      • no DefaultPassword in Winlogon;
      • defaultuser0 disabled;
      • Security log 4634 logoffs at 19:51:34–37Z;
      • quser: No User exists;
      • LogonUI is running and explorer isn't, so the console rests at the sign-in screen, not an unlocked desktop.
    • dot-windows (198), re-cloned from the new 911 with the targeted -replace: the same result on first boot, plus no Panther\unattend-original.xml.

    The chained single FirstLogonCommand (391863) is what ran. Closing.

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinglabstacks/lab on alexander (VLAN 30)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions