Installer Desktop Stage Failure
P2 High — June 14, 2026 | Hermes Agent Lab, hermes-agent.reviews
🔍 The Bug in One Sentence
Hermes v0.16.0 installer (hermes-setup.exe) on Windows 10 Pro completes all prerequisite stages successfully (uv, Python, Git, Node, ripgrep/ffmpeg, repo clone, venv, Python deps, Node.js deps) but fails at the final "desktop" stage because npm's bundled dependencies require Node >=24 while the installer ships Node v22.22.3. The engine mismatch causes npm ci to fail with EBADENGINE, and the retry with npm install also fails. Result: bootstrap FAILED stage=Some("desktop") — Hermes cannot be used at all.
📈 Impact Assessment
| Dimension | Detail |
|---|---|
| Platform affected | Windows 10 Pro (likely all Windows) |
| Hermes version | v0.16.0 |
| Failure stage | "desktop" — final stage, after all prerequisites pass |
| Root cause | Node engine mismatch: @icons-pack/[email protected] requires node >=24, installer bundles Node v22.22.3 |
| Error signature | npm ci exits with EBADENGINE warnings → exit code 1 |
| Retry behavior | Pipeline retries with npm install — also fails |
| User experience | bootstrap FAILED stage=Some("desktop") — complete install-blocker |
| Linked PR | #46452 — open |
⚠️ The Dependency Cascade Problem
Why This Is Harder Than It Looks
| Layer | What Fails | Why It Matters |
|---|---|---|
| 1. npm engine check | EBADENGINE warning on @icons-pack/react-simple-icons | npm strict mode refuses to proceed |
| 2. npm ci failure | Exit code 1, no node_modules created | Desktop app has no dependencies |
| 3. npm install retry | Same engine mismatch, same failure | No recovery path in pipeline |
| 4. bootstrap abort | Installer reports failure, exits | User has no working Hermes installation |
| 5. Earlier warnings ignored | browser-tools npm install also failed earlier | Pipeline continued despite earlier npm failures |
Key finding: The installer pipeline continues past earlier npm failures (browser-tools) but aborts on the desktop stage. The bundled Node version is mismatched with the dependency tree — a packaging error, not a user configuration problem. The user has no remediation path.
🔄 Installer Reliability Comparison
What Production-Grade Installers Do Differently
| Characteristic | Hermes Installer | Production-Grade Installer |
|---|---|---|
| Dependency engine validation | ❌ None — mismatch discovered at runtime | ✅ Pre-flight check before any install step |
| Bundled runtime version | ❌ Node v22.22.3 (too old for deps) | ✅ Pinned to dependency requirements |
| Error handling on npm failure | ❌ Retry with npm install (same failure) | ✅ Diagnostic + remediation guidance |
| Earlier failure detection | ❌ Pipeline continues past npm failures | ✅ Abort on first unrecoverable error |
| User remediation path | ❌ None documented | ✅ "Try manual Node upgrade to v24+" |
📜 Sources & Methodology
Analysis based on GitHub issue #46260 (opened Jun 14, 2026 by @kraplegit). Environment: Windows 10 Pro, Hermes v0.16.0 installer (hermes-setup.exe). All prerequisite stages completed successfully before desktop stage failure. Root cause confirmed: npm EBADENGINE on @icons-pack/[email protected] (requires node >=24) with bundled Node v22.22.3.
Source: github.com/NousResearch/hermes-agent/issues/46260
As benchmarked by Hermes Agent Lab, hermes-agent.reviews — June 2026.