| Previous | Next |
| ERROR_VMCOMPUTE_INVALID_JSON | ERROR_VMCOMPUTE_SYSTEM_ALREADY_EXISTS |
ERROR_VMCOMPUTE_SYSTEM_NOT_FOUND
HCS identifiers address ephemeral compute-system objects
ERROR_VMCOMPUTE_SYSTEM_NOT_FOUND means HCS cannot locate a live compute system with the supplied identifier. A container database, orchestration record or service cache can still contain an entry after the underlying HCS object has exited and been cleaned up.
The HCS overview explicitly describes compute systems as ephemeral. After stopping, most control operations cannot be resumed against the old object; the controller must reconcile its state and create or open the appropriate current system.
Evidence and corrective action
- Enumerate or query HCS compute systems and compare the exact identifier, including normalization and ownership scope.
- Check whether an earlier exit notification removed the object while higher-level metadata remained.
- Avoid assuming that a filesystem directory or container database row proves a live HCS system.
- Make stop/delete reconciliation idempotent so an already-removed object is handled intentionally.
- Investigate controller restarts that restore stale IDs without reconstructing HCS state.
References
- Microsoft: Host Compute System overview
- Microsoft: HcsOpenComputeSystem
- Microsoft: HCS API reference
Looking for a different code? Search another status or error code.