# NousResearch/hermes-agent · Windows self-lock loop fix during update process

## Open now

- Nothing open on GitHub.

These items address a bug where eager imports and premature deferral logic caused a circular self-lock loop on Windows during updates. The fixes involve lazy imports and conditional deferral tied to actual swap risk.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 2 merged PR(s), 0 PR(s) closed without merging.
- A fix was merged to main in PR #86857. Verify it addresses your case.
- **Recommended:** read PR #86857 (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-86782`. 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

- #86781: \[Bug\]: cryptography._rust.pyd loaded eagerly by main() — causes Windows self-lock loop on update (circular defer)

## Prior & competing PRs

- **#86782: fix(update): lazy-import secrets_cli + defer secret_sources registry — prevent Windows self-lock loop**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/env_loader.py`, `hermes_cli/main.py`, `hermes_cli/secrets_cli.py`, `tests/test_lazy_secrets_dispatch.py`, `tests/test_lazy_secrets_import.py`
- **#86857: fix(update): self-lock deferral fires only when the swap is actually at risk**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/main.py`, `hermes_cli/update_cmd.py`, `tests/hermes_cli/test_update_self_lock.py`

## Fix status

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