Windows auto-update blocked by child process file locks
Cluster 98336. Data as of
Nothing open on GitHub. Fix merged in #100124 on 1 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #100124. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #99724. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address Windows update failures caused by hermes.exe being held open by child processes (serve, gateway, venv). The work involves deferral logic, process cleanup, and preflight checks to avoid dead-ends during the update flow.
Open issues0
Open PRs0
Fixes on record
-
#99724 fix(update): defer ledger-verified serve/dashboard venv holders to the updater (Windows os error 32)
files:
hermes_cli/_scan_venv_blockers.py,tests/hermes_cli/test_scan_venv_blockers.py,tests/hermes_cli/test_venv_holder_windows_live.py -
#100124 fix(desktop): Windows update-preflight family — deferral evidence, hindsight daemon reap, gateway stop/restore (salvage #98350/#75477/#76057)
files:
apps/desktop/electron/gateway-stop-before-update.test.ts,apps/desktop/electron/gateway-stop-before-update.ts,apps/desktop/electron/main.ts,apps/desktop/electron/venv-blocker-scan.test.ts,apps/desktop/electron/venv-holder-select.test.ts,apps/desktop/electron/venv-holder-select.ts,contributors/emails/[email protected],contributors/emails/[email protected],hermes_cli/_scan_venv_blockers.py,tests/hermes_cli/test_scan_venv_blockers.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#98350 fix(desktop): don't dead-end the update on ledgered manual serve blockers · done elsewhere →
#100124,#99724
Closed issues · 1
- Closed#98336Desktop auto-update fails on Windows when hermes serve / gateway child processes hold hermes.exe (os error 32)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab