Building a Windows 11 24H2 Golden Image: Sysprep Wins, Ghost Quirks, and an OOBE Curveball
This Sysprep session took the wind out of me today.
Building a generalized Windows 11 24H2 Enterprise golden image for cross-model Dell OptiPlex deployments sounds straightforward on paper until security baselines, legacy serial hardware, and modern consumer provisioning collide. Today's bench session focused on sealing a clean Symantec Ghost (.gho) master image capable of booting hands-free into production with satellite and RFID serial bindings intact.
Most of the heavy engineering went right, a few classic WinPE quirks tried to trip up the capture, and Windows 11 saved one last OOBE curveball for the first test boot.
Clearing 0x80073cf2 and Locking In Serial Persistence
Getting sysprep.exe past its initial validation phase on 24H2 meant cleaning up package state drift before touching the capture media. Once the audit pass finished, the core image came together cleanly:
- Eliminating Sysprep Blockers: Cleared
0x80073cf2Appx provisioning mismatches by stripping lingering consumer packages (Edge, Winget, and Widgets) and resettingCleanupStateandGeneralizationStateunderSysprepStatusso/generalize /oobevalidated on the first pass with zero errors. - Automating COM Port & Satellite Comms: Wired
SetupComplete.cmdto trigger a PowerShell provisioning script on boot that disablessermouse, evicts Intel AMT Serial-over-LAN fromCOM3, binds the Iridium RUDICS modem toCOM3with initialization stringAT+CBST=71,0,1, reservesCOM4for the SAVI reader, and preserves system-widerasphone.pbkdial-up profiles alongside custom 16:9 headless display branding. - Sanitizing the Bench State: Worked around
PSReadLinebracketed paste freezing multi-line cleanup blocks on line one in Windows Terminal by running the sanitization pass from a local.ps1script onC:\, deleting the file, clearing the Recycle Bin, and purgingConsoleHost_history.txtacross all user profiles withSaveNothingset before shutdown.
Ghost64 and the Missing File Extension
With Sysprep generalized and the OptiPlex powered down, I booted into WinPE off USB to capture the internal SATA SSD onto an external NVMe drive using Ghost64. Starting from a SATA source keeps the storage stack flexible so Windows 11's native stornvme driver can boot newer NVMe OptiPlex targets once BIOS storage is switched from RAID On to AHCI/NVMe.
When the capture hit 100% and I opened Ghost's integrity check, the image file appeared to be missing. Switching the file filter to *.* showed the multi-gigabyte archive sitting right where I saved it, stripped of its .gho extension. Because my destination path used numbered folder names containing periods, Ghost64's legacy path parser spotted a dot in the directory string, assumed I had already supplied a custom extension, and skipped appending .gho.
Fixing the filename inside modern WinPE added one more wrinkle: Microsoft removed wmic.exe from newer WinPE builds, and Ghost64 displayed the external NVMe drive as E: while WinPE mounted it at L:. Running list volume in diskpart exposed the real drive letter so I could append .gho from cmd.exe, pass a 100% Ghost integrity check, and flush the NTFS write cache cleanly via wpeutil shutdown.
The OOBE Curveball: When Windows 11 Ignores unattend.xml
Pulling both USB sticks and powering the rig back on proved the answer file worked almost end-to-end. Windows breezed past the Region, Keyboard, Network, and EULA prompts untouched, then stopped cold at the interactive local account creation screen.
Even with pre-staged local accounts already configured on disk, Windows 11 24H2 Client ignores HideLocalAccountScreen inside Microsoft-Windows-Shell-Setup. That directive only suppresses account creation on Windows Server. Microsoft's documentation marks SkipMachineOOBE and SkipUserOOBE as deprecated, yet client golden images with pre-existing local accounts still need those two legacy flags (or a self-deleting temporary account block) to bypass the prompt in a single pass.
Parking the Build for Live Field Triage
Before I could restore the image into WinPE and patch C:\Windows\Panther\unattend.xml offline, a remote read station running on a ZTE cellular hotspot puck dropped offline again. With a full week of scheduled PMCS ahead and upcoming travel, getting ADB diagnostics and keep-alive rules onto that ZTE puck takes priority over OOBE polish, so the bench OptiPlex is pivoting back into a scratch test rig tonight.
The good news is that none of today's baseline work is lost. The generalized, sanitized 2611 .gho image is verified and stored safely on my field NVMe drive. Once I'm back at the workbench, restoring that image offline in WinPE, dropping <SkipMachineOOBE> and <SkipUserOOBE> straight into Panther\unattend.xml, and re-capturing will unlock true zero-touch deployments without running Sysprep a second time.