| Previous | Next |
| ERROR_VMCOMPUTE_UNEXPECTED_EXIT | ERROR_VMCOMPUTE_CONNECT_FAILED |
ERROR_VMCOMPUTE_TERMINATED
Forced termination bypasses the guest’s orderly shutdown path
ERROR_VMCOMPUTE_TERMINATED records that the HCS compute system ended through a forceful termination path. This differs from HcsShutDownComputeSystem, which requests an orderly shutdown and gives the guest or container a chance to perform normal cleanup.
The result can be intentional—for example, after a management timeout—or secondary to another failure that caused the runtime to terminate the system. File-system consistency, buffered logs and application-level transactions may therefore need separate verification.
Evidence and corrective action
- Identify the process or management component that called
HcsTerminateComputeSystemor triggered equivalent policy. - Compare the termination timestamp with an earlier timeout, cancellation, health-check or service-stop event.
- Do not label the workload as crashed solely from this code when the host deliberately forced termination.
- Inspect persistent volumes and external state for incomplete writes before automatic restart.
- Use graceful shutdown first when the workload and operational deadline allow it.
References
- Microsoft: HcsTerminateComputeSystem
- Microsoft: HcsShutDownComputeSystem
- Microsoft: HCS lifecycle overview
Looking for a different code? Search another status or error code.