| Previous | Next |
| ERROR_VID_VTL_ACCESS_DENIED | ERROR_VMCOMPUTE_IMAGE_MISMATCH |
ERROR_VMCOMPUTE_TERMINATED_DURING_START
Startup crossed the create boundary but never reached a usable running state
ERROR_VMCOMPUTE_TERMINATED_DURING_START belongs to the Host Compute System lifecycle used for Windows containers and virtual machines. Creation, configuration and startup are distinct phases. This result means the compute system was instantiated far enough for startup to begin, but it exited before the caller obtained a stable running system.
The useful evidence is therefore the asynchronous HCS operation result and its JSON error record, not only the immediate return from HcsStartComputeSystem. A malformed configuration is more likely to fail during creation, while an early guest boot failure, inaccessible runtime file, invalid device configuration or immediately terminating init process can surface during start.
Evidence and corrective action
- Preserve the complete result document returned by
HcsWaitForOperationResultorHcsGetOperationResult. - Record whether creation completed successfully and whether the failure is reproducible only at
HcsStartComputeSystem. - Collect Host Compute Service and Hyper-V worker events for the same compute-system identifier and timestamp.
- For containers, inspect the configured command and image layer chain rather than treating the code as a generic Docker networking failure.
- Do not reuse the stopped HCS handle as though the compute system were still alive; open or create a new instance after fixing the cause.
References
- Microsoft: Host Compute System overview
- Microsoft: HcsStartComputeSystem
- Microsoft: HCS operation completion
Looking for a different code? Search another status or error code.