Windows Workstation Deployment

Preparing a workstation consistently means installing and updating a long list of prerequisites. Doing it by hand invites drift between machines, and downloading installers from the first search result is a genuine supply-chain risk. When something goes wrong, there is usually no record of what ran or which version was installed.

A deployment engine in which every package comes from the vendor’s own page or official release, and every downloaded file is verified against a SHA-256 manifest before execution. Installers run with their documented silent switches, the standard Windows installer exit codes are interpreted so that “reboot required” is distinguished from failure, and each run writes a timestamped CSV report.

• Downloads taken only from official vendor pages and official releases — no third-party mirrors
• SHA-256 checksum verification of every downloaded file against a manifest
• Driver refresh that probes official hardware-vendor portals and records hashes
• Confirmation required before the driver step continues
• Interactive selection of a single package or a comma-separated list
• Documented silent installation arguments per package
• Standard Windows installer exit-code handling, distinguishing success, reboot-required and reboot-initiated
• Timestamped CSV deployment report per run
• Skip-already-installed detection

• The repository bundles third-party application and endpoint-protection installers for its own deployment use. Redistribution rights for those binaries were not verified, so they are deliberately not offered for download from this site.
• No versioned release and no published build.
• No automated test suite and no CI workflow.
• No licence file is published.
• Automating third-party software installation is inherently supply-chain sensitive; checksum verification is the control, and it depends on the manifest being maintained correctly.

• PowerShell
• SHA-256 verification
• Windows installer exit codes