Windows update can leave Hermes gateways stopped
On Windows, updating Hermes to 0.17.0 can leave the gateway stopped after the update finishes. The problem happens when a fails and Hermes falls back to the .
A direct ZIP update already restarts paused at the end, but the ZIP path after a git failure missed that same cleanup step. This means the update can succeed while the user’s Windows gateway stays paused.
fixes this by applying the same gateway resume behavior to the path. The change is still open and not merged, but the same fix can be applied temporarily.
Key points
- Hermes 0.17.0 can leave a Windows gateway stopped after updating.
- The issue appears when a fails and falls back to the .
- Direct ZIP updates already resume paused correctly.
- adds the same resume step to the path.
- Until it is merged, check and resume the gateway manually after updating.