# NousResearch/hermes-agent · Windows WMI scan hangs hermes update indefinitely

## Open now

- Nothing open on GitHub.

A bug where a slow or unresponsive WMI process scan could cause 'hermes update' to hang forever on Windows, due to an unbounded communicate() call after timeout. The cluster covers the bug report and associated fix attempts.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #87707. Verify it addresses your case.
- **Recommended:** read PR #87707 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-87707`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #87134: \[Bug\]: hermes update hangs forever on Windows when the gateway PID scan exceeds its timeout (unbounded post-timeout communicate() in _scan_gateway_pids)

## Prior & competing PRs

- **#87707: fix(cli): bound Windows process-scan probes so a slow WMI scan cannot wedge hermes update (salvage #87144)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/_subprocess_compat.py`, `hermes_cli/claw.py`, `hermes_cli/dashboard_procs.py`, `hermes_cli/gateway.py`, `tests/hermes_cli/test_bounded_probe_run.py`, `tests/hermes_cli/test_update_stale_dashboard.py`
- **#87144: fix(cli): bound the Windows process-scan probes so a slow WMI scan cannot wedge hermes update**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#87707`, `#87134`

## Fix status

- Merged to main in PR #87707 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-16`.