minute2win 0.1.2

Read first: a disposable-VM deployment has now booted end to end, but nothing has been run on physical hardware, with Secure Boot, or with an OEM key. See Status and #8.

Fixes

• Windows server: arming no longer fails. Saving state hit "Access is denied" on the directory sync, which left the server degraded and rejecting every arm. Windows now replaces the state file with a write-through move; Unix is unchanged. Arms still never survive a restart.
• UEFI network boots no longer fall back silently. The injected manifest is now named explicitly in iPXE, and the loader stops before installing if no manifest was injected, unless a static profile is selected with -Manifest.

New

• Linux x86_64 AppImage (minute2win-server-0.1.2-x86_64.AppImage): the server and manifests/ in one runnable file. Not code-signed; check it against SHA256SUMS.
• Documentation site and a rebuilt README, with console screenshots.
• Native Windows server tests in CI.

Verified

A disposable Proxmox UEFI VM network-booted through a Windows-hosted deployment server, verified the image, installed Windows 11 Pro, reached normal OOBE and completed the automatic first-boot bootstrap. A deployment took about 375 s from WinPE boot, so the one-minute goal is not yet met. Evidence: docs/validation/2026-10-11-windows-server.md.

Not verified

Secure Boot, OEM product keys, physical hardware, concurrent PXE load, and an initial image-checksum failure whose cause is still unexplained. The optional local-admin profile (oobe.adminUser) reached the desktop but its follow-up sign-in is unchecked (#8), so leave it null for now.

Assets

Linux amd64/arm64 tarballs, the AppImage, the Windows x64 zip (Authenticode-signed, see SIGNATURES.txt), the boot-files zip and SHA256SUMS.

minute2win 0.1.1

Draft: notes to follow.

minute2win 0.1.0

Read first: this release is unit-tested and adversarially reviewed but has never booted a machine. What is unverified, and three accepted risks, are listed concretely in #2.

minute2win deploys Windows with no one at the keyboard. A machine network-boots into WinPE, and minute2win wipes the first eligible internal disk (never USB), applies a verified Windows image and reboots into it. The name is the goal: boot to flashed Windows in about a minute, so every phase is timed.

What's in it

• Engine (PowerShell 5.1 in WinPE): manifest-driven, no disk prompt. Guards: a one-shot server arm per MAC, a WinPE-only check, an abort countdown. Checks that run before the wipe: image reachable, fits the staging partition, disk big enough, free drive letters.
• minute2win-server (Go, one static binary, htmx UI built in): arm a MAC from the page; iPXE gets a boot script that consumes the arm and fails closed; a live board shows each phase against a 60 s stopwatch.
• First-boot bootstrap, logs that survive the reboot (C:\Windows\Logs\minute2win), and a boot-files bundle to upload next to wimboot, boot.wim and install.wim.

Assets

minute2win-server-0.1.0-linux-{amd64,arm64}.tar.gz (server + manifests), minute2win-0.1.0-bootfiles.zip (the windows11/ tree), SHA256SUMS. Verified from this page: checksums match, the amd64 binary runs and serves the UI, an unarmed MAC gets exit 1.

Review

Five adversarial rounds (astra), every finding reproduced against source, logged in docs/dev-process.md. Round 1 found 12 real defects, including an iPXE command injection through the boot URL and a path that could wipe before a failing check; all are fixed.

Known issues

See #2.