| Previous | Next |
| ERROR_VMCOMPUTE_TIMEOUT | ERROR_VMCOMPUTE_UNKNOWN_MESSAGE |
ERROR_VMCOMPUTE_CONNECTION_CLOSED
An existing control session ended before the operation completed
ERROR_VMCOMPUTE_CONNECTION_CLOSED differs from an initial connection failure: a host/guest compute-service channel existed and was then closed. This can follow utility-VM shutdown, a guest compute service crash, forced termination, host servicing or a protocol-level abort.
The first event in the timeline matters. A connection-closed result is often secondary evidence after an earlier guest failure, so restarting the management client alone may erase the relationship without correcting the underlying compute system.
Evidence and corrective action
- Review the event sequence for guest exit, service termination or host-initiated shutdown immediately before the closure.
- Check whether all operations on the same utility VM failed together or only one container request was affected.
- Preserve the HCS result JSON and guest service logs before the utility VM is discarded.
- Treat the old connection and compute-system handles as suspect after an exit notification.
- Compare host updates and component versions when closures began after servicing.
References
- Microsoft: Host Compute System overview
- Microsoft: HCS event callback sample
- Microsoft: hcsshim project
Looking for a different code? Search another status or error code.