Symptom
After hermes-setup.exe --update on Windows, the Desktop app stays on CONNECTING. The update log shows ✓ Update complete! and exit code 0, then the Electron main process never reaches the dashboard.
Evidence what you'll see
logs\desktop.logrepeats[hermes] [boot] Desktop boot failed: Hermes backend did not become ready:andTimed out connecting to Hermes backend after 15000ms.- The web UI build runs
tsc -band fails with'tsc' is not recognized as an internal or external commandbecausetypescriptwas never installed. web/node_modulesis left partial (a few MB, only@nous-research/andglobals/, nopackage-lock.json).hermes-agent/node_modules/typescript/package.jsonis absent even thoughweb/package.jsonliststypescriptas adevDependency.
Why it happens
hermes_cli/main.py sets NODE_ENV=production early via env.setdefault("NODE_ENV", "production"). That value reaches the dashboard npm install. npm then omits devDependencies, so typescript and @vitejs/plugin-react are missing and tsc -b aborts. Each Desktop restart respawns dashboard, reruns npm install, and hits the 15s/45s timeout again.
Affected versions
Hermes Desktop v0.17.0, Windows 10/11, Node 24.13.0, npm 11.6.2, hermes-agent commit 67523fae7 at the time of the report.
Fix steps
0 of 2 done
Your check marks stay in this browser only.
How to check it worked
- After update, Desktop leaves CONNECTING and the UI loads.
web/node_modules/typescript/package.jsonexists, anddesktop.logdoes not repeatTimed out connecting to Hermes backend after 15000ms.
If it still fails
- A 20 Jul 2026 comment says to check whether
web/node_modules/typescript/package.jsonexists after a fresh Windows updater run. If CONNECTING still hangs and that file exists, the comment treats it as a different boot failure than omitteddevDependencies. - The closer on 23 Sep 2026 says this confirms main and pull request 38416, not availability in a released Windows installer package.
Sources and credit
Summarized in our own words from these public reports. Credit goes to their authors.
Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change
Hit an error we don't cover? Submit it