Windows ISO Build Toolchain

Keeping a standardised Windows image current is tedious and easy to get wrong. After each Patch Tuesday somebody has to work out which cumulative update, servicing-stack update and .NET update applies to which build, download them, mount the image, apply them in the right order, add drivers, and rebuild install media. Doing it by hand means either stale images or occasionally broken ones, and nothing is reproducible.

A restartable state machine that detects the target build from the ISO itself rather than assuming it, queries the public Microsoft Update Catalog for candidates, classifies each one as missed or already present, and reports only what is genuinely needed. Integration and driver injection happen through Microsoft’s own supported servicing commands against a copy of the source media, so the original ISO is never modified and a failed run can be diagnosed and resumed.

• Ten-phase orchestrator that is restartable through a persisted state file
• Target build detection read from the ISO rather than assumed
• Update discovery against the public Microsoft Update Catalog with missed-versus-present classification
• Explicit download step — nothing is downloaded implicitly during servicing
• Offline integration of cumulative, servicing-stack and .NET updates into the install image
• Driver injection into the install image
• Unattend and out-of-box-experience configuration generation
• Bootable ISO rebuild with versioned output naming
• WinForms front-end that streams the run log and confirms before any mutating phase
• A headless self-test mode for validating the wiring
• Reports directory containing a real run’s environment audit, ISO inventory and update manifest

• It requires an elevated PowerShell session, the Windows ADK Deployment Tools and roughly 40 GB of free disk space, so it is a specialist tool rather than something a casual user can run.
• No downloadable build: all twelve published releases carry no attached files, so the repository is the only entry point.
• No automated test suite and no CI workflow.
• No licence file is published.
• Servicing behaviour depends on Microsoft’s update catalogue and on DISM, both of which change over time.

• PowerShell
• DISM
• Windows ADK
• WinForms
• Microsoft Update Catalog