Windows launcher locking during update process
Cluster 88078 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #90192 on 19 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #90192. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items relate to a problem where Windows launchers become locked and interfere with the update process. The group includes a reported issue and two fixes targeting this specific Windows update/launcher locking behavior.
Open issues0
Open PRs0
Fixes on record
-
#90192 fix(update): stop Windows updates from locking their own launcher
files:
gateway/slash_commands.py,hermes_cli/_install_repair.py,hermes_cli/main.py,hermes_cli/subcommands/update.py,hermes_constants.py,scripts/desktop-update/windows.ps1,tests/hermes_cli/test_update_concurrent_quarantine.py,tests/hermes_cli/test_update_shim_self_lock.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#88121 fix(updater): stop locked Windows launchers from breaking updates · superseded by another PR →
#90192,#89970
Closed issues · 1
- Closed#88078The command line cannot be updated normally
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.67: 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 LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #90192
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Aug 2026