Problem: Installing herdr on Windows via PowerShell fails (downloads get reset; download the binary directly instead) —— Trove problem library

What you will run into

On Windows you follow the official instructions and run the install command in PowerShell — the download gets reset or the script errors out, and herdr does not get installed. It looks like a broken network; in fact two factors stack up: PowerShell Web downloads handle GitHub releases poorly and get reset easily, and the old install path is still in circulation.

Why this happens

Conclusion first: the problem is the download channel, not herdr itself. The official installer was fixed on 2026-08-22 (issue #3131 avoids PowerShell web downloads; #3133 adds a local cmd installer bootstrap), yet issue #3232 (open, 2026-08-25) still has people hitting the old path — the fix exists, but old commands and old docs are still around.

Chain: PowerShell script -> Web download (Invoke-WebRequest class) -> GitHub release -> unpack/install. The break is usually step two: direct connections from mainland networks to GitHub releases are unstable, and the built-in PowerShell downloader handles redirects and large files less reliably than dedicated tools — "download reset / script error" is the usual shape.

Side-by-side measurement (2026-08-28, WSL Linux): download the binary through gh-proxy -> chmod +x -> --version works (cli-smoke v0.8.2). The Windows PowerShell path was not reproduced in this environment (stated honestly) — but the same mechanism applies: fetch the binary directly to bypass PowerShell downloads.

Conclusion: when a PowerShell install fails, do not retry the same command; switch channels (browser / download tool / gh-proxy direct binary), then verify the command works.

Step by step

1. Confirm it is the download layer — Required

Signature: the command hangs on downloading or gets reset — herdr itself never errors. Download the same file with a browser or download tool: if that works, it is the download layer.

2. Download the binary directly (bypassing PowerShell) — Required

Grab the Windows asset from the release page; add the gh-proxy prefix on mainland networks.

3. Upgrade to the fixed installer — By scenario

Installers published after 2026-08-22 avoid PowerShell web downloads (#3131/#3133); if you still use the old command, check the latest install method in the official docs.

4. Verify — Required

herdr --version prints a v0.8.2-class version number = success.

How to confirm it works

• herdr --version prints a version normally;
• the command surface (herdr / herdr server) is usable afterwards (see the herdr server start entry).

Other environments

• WSL / Linux: gh-proxy direct-binary download verified (2026-08-28);
• Corporate networks (proxy): downloads go through the system proxy; the gh-proxy path also works on proxy-less campus networks;
• Source material: herdrdev/herdr issues #3232 (open, 2026-08-25) / #3131 / #3133 (closed — installer fixed), anonymous retrieval on 2026-08-28.

Symptom

On Windows, running the official install command in PowerShell fails (downloads get reset or the script errors).

Cause

The built-in PowerShell Web download handles GitHub releases poorly and gets reset easily. The official installer was fixed on 2026-08-22 (issue #3131 avoids PowerShell web downloads; #3133 adds a local cmd installer bootstrap), but issue #3232 (open, 2026-08-25) shows people still hit the old path.

Solution

1. Upgrade to an installer containing the fix, or download the binary directly instead of downloading through PowerShell.
2. On mainland networks, accelerate the binary download with the gh-proxy prefix.