test-windows-installer

Install pwsh and run pwsh -NoProfile -File ./packaging/windows/test-install.ps1 from the repo root. The harness parses install.ps1, runs source guards, and executes child runs like -Help and -DryRun, printing PASS lines for each check.

Under irm | iex or scriptblock hosts, calling exit terminates the entire PowerShell window, not just the script. Fatal installer errors should use throw instead of exit so the host survives and the error remains visible.

Yes, the harness runs under pwsh on Linux. It isolates environment variables like LOCALAPPDATA and TEMP so Linux runs do not write under ~/Programs, and it handles empty $env:TEMP by falling back to TMP, TMPDIR, or GetTempPath.

With $ErrorActionPreference set to Stop, native stderr output such as a missing schtasks becomes a terminating error. Use an Invoke-Native wrapper that continues on error and checks $LASTEXITCODE instead.

It catches Die paths that use exit instead of throw, menu Bye paths that exit the host, shims that exit with $LASTEXITCODE, silent download failures from bad -BaseUrl values, and -Update runs that kill the harness on empty state.