Herdr Windows Install Fails with “Failed Verification”? It’s Probably a Missing VCRUNTIME140.dll

TL;DR: If the Herdr Windows preview installer throws Downloaded Herdr command failed verification, the message is misleading. In most cases it has nothing to do with a corrupted download, a broken signature, or antivirus interference. The installer is actually running herdr.exe --version as a sanity check, and that command is silently crashing because Windows can’t find VCRUNTIME140.dll. Install the Visual C++ x64 Redistributable, re-run the install script, and the error goes away.

The Error

Running the official Herdr install command on Windows:

irm https://herdr.dev/install.ps1 | iex

completes the download step, then fails at the very last stage with something like this:

==> Fetching Herdr preview manifest
==> Installing Herdr 0.8.0-preview.2026-08-04-d78e3d3b5126 for x86_64-pc-windows-msvc
==> Downloading Herdr
Downloaded Herdr command failed verification: C:\Users\xxx\.herdr\packages\standalone\releases\.staging.0.8.0-preview.2026-08-04-d78e3d3b5126-x86_64-pc-windows-msvc.6424\herdr.exe --version

The PowerShell FullyQualifiedErrorId reports a generic RuntimeException, and the phrase “failed verification” naturally reads as a signature check or hash check failure. That framing sends most people down the wrong troubleshooting path — checking for a corrupted download, blaming antivirus software, or assuming the preview build itself is broken.

What “Verification” Actually Means Here

Herdr’s installer doesn’t do a traditional cryptographic signature or checksum comparison after downloading herdr.exe. Instead, it treats a successful run of herdr.exe --version as proof that the binary is usable. If that command doesn’t return a clean version string — because the process crashes, exits with a non-zero code, or is missing a runtime dependency — the installer marks the whole staging directory as a failed verification and throws the error above.

That’s a reasonable design, but the error message doesn’t surface the underlying failure. It just says “failed verification,” which is technically true but practically unhelpful.

How to Find the Real Cause: Run the Staged Binary Yourself

Right after the install script fails, the staging folder is still on disk for a short window. Instead of guessing, run the exact command the installer just ran:

& "C:\Users\xxx\.herdr\packages\standalone\releases\.staging.0.8.0-preview.2026-08-04-d78e3d3b5126-x86_64-pc-windows-msvc.6424\herdr.exe" --version

This immediately surfaces the real Windows error as a native dialog box:

herdr.exe - System Error
The code execution cannot proceed because VCRUNTIME140.dll was not found.
Reinstalling the program may fix this problem.

That’s the actual root cause: it has nothing to do with signatures, checksums, or network integrity. The machine is simply missing the Visual C++ runtime. This particular Windows preview build depends on VCRUNTIME140.dll being present on the system — a DLL that ships with the Microsoft Visual C++ Redistributable, not with a clean Windows install. If you’ve never installed Visual Studio, the VS Build Tools, or any other software that bundles the MSVC runtime, there’s a good chance your machine doesn’t have it.

Why This Error Is Easy to Misdiagnose

The disconnect between the error text (“failed verification”) and the actual cause (“missing runtime dependency”) pulls people toward several plausible-but-wrong theories:

  • 🍂
    “The preview build is broken.” Herdr’s own docs note that preview releases are manually published pre-release builds that “can regress,” which makes this a tempting first suspect.
  • 🍂
    “Windows Defender or SmartScreen quarantined it.” Also plausible — Herdr’s Windows beta documentation explicitly lists unsigned binaries as a known limitation (“Signed binary / SmartScreen avoidance: unsupported”).
  • 🍂
    “The download got corrupted or intercepted.” Reasonable on a corporate network or behind a proxy/VPN.

All three are worth ruling out in general, but in this specific case none of them were the problem. The fastest way to cut through the guessing is to skip the theories and just execute the binary that failed. Let Windows’ own error dialog tell you what’s wrong instead of reverse-engineering it from an exit code.

The Fix

  1. Download Microsoft’s official Visual C++ x64 Redistributable:
    https://aka.ms/vs/17/release/vc_redist.x64.exe
  2. Run the installer. It typically doesn’t require a reboot — but if the error persists afterward, restart your machine once.
  3. Re-run the Herdr install command:

    irm https://herdr.dev/install.ps1 | iex

    The installer’s internal herdr.exe --version check will now pass.

General Debugging Takeaway

When an install script fails with a vague “verification failed” or “check failed” message, this sequence tends to converge on the answer fastest:

  1. Understand what “verification” actually means for that script. Is it a cryptographic signature check, a hash comparison, or — like Herdr — literally just running the binary and checking whether it works? That distinction determines how much you can trust the error text.
  2. Replay the exact failing command by hand. If the check is “run it and see,” the script has almost certainly swallowed or oversimplified the real error. Running it yourself usually surfaces the operating system’s native, specific error message.
  3. Separate “file integrity” problems from “runtime dependency” problems. A bad signature, hash mismatch, or truncated download means the file itself is untrustworthy or incomplete. A missing DLL or wrong runtime version means the file is fine but the environment it’s running in isn’t ready for it. These need completely different fixes.
  4. Don’t stop at the first plausible theory. An unsigned binary getting flagged by Defender, or a preview build being unstable, are both reasonable-sounding explanations — but without actually verifying them, it’s easy to burn time chasing the wrong fix.

Bottom line: this “failed verification” error had nothing to do with Herdr’s stability or security posture. It was a missing, generic Visual C++ runtime file on the local machine — installing it resolves the issue completely.

Keywords: Herdr Windows install error, Herdr failed verification, VCRUNTIME140.dll missing, herdr.exe system error, Herdr preview installer troubleshooting, Visual C++ Redistributable missing DLL fix.