Hugo

For managed Windows deployments of Hugo, pick the edition deliberately before packaging: the official release assets include standard, extended, and extended_withdeploy Windows ZIP builds such as hugo_extended_*_windows-amd64.zip. The extended builds are the safer default when teams have existing sites that depend on Hugo Extended features; Hugo documentation notes that Dart Sass is the preferred Sass path going forward and works with any edition.

Hugo is a portable executable rather than a traditional MSI on the GitHub release page. A predictable enterprise package can extract hugo.exe into a fixed directory such as %ProgramFiles%\Hugo\bin, add that directory to the machine PATH if needed, and validate the installed binary with hugo version. Hugo’s Windows documentation also lists command-line package-manager examples for the extended edition and removal, but packaged deployments should still record which edition and ZIP asset were staged.

Sources: official Hugo releases and Hugo Windows installation documentation.