| Previous | Next |
| ERROR_VMCOMPUTE_IMAGE_MISMATCH | ERROR_VMCOMPUTE_OPERATION_PENDING |
ERROR_VMCOMPUTE_HYPERV_NOT_INSTALLED
The requested compute-system type depends on the Windows hypervisor stack
ERROR_VMCOMPUTE_HYPERV_NOT_INSTALLED is returned when HCS needs Hyper-V facilities but the required Windows feature or active hypervisor is unavailable. Hardware virtualization support alone is insufficient: firmware settings, optional Windows components and the boot configuration must result in a running Microsoft hypervisor.
This commonly matters for Hyper-V-isolated Windows containers and virtual-machine compute systems. Process-isolated containers have a different execution model, so the same host can sometimes run one isolation type while rejecting another.
Evidence and corrective action
- Verify that the required Hyper-V components are installed for the host edition and role being used.
- Confirm virtualization is enabled in firmware and that the hypervisor was launched during the current boot.
- Record the requested compute-system type and container isolation mode from the HCS configuration JSON.
- Check for conflicts with another virtualization stack or boot option that prevents the Microsoft hypervisor from starting.
- Restart after feature or firmware changes; merely restarting the container service cannot activate a missing hypervisor.
References
Looking for a different code? Search another status or error code.