| Previous | Next |
| STATUS_HV_NOT_ALLOWED_WITH_NESTED_VIRT_ACTIVE | STATUS_IPSEC_BAD_SPI |
STATUS_HV_NOT_PRESENT
The Hyper-V interface is being used on a system where no hypervisor is active
STATUS_HV_NOT_PRESENT is returned when the requested Hyper-V path requires a running hypervisor but the system does not currently have one present. The machine may still be Windows, and virtualization hardware may still exist; the status specifically says the Hyper-V hypervisor interface is not active for this request.
This is a common distinction when code assumes Hyper-V because a feature is installed, because hardware virtualization exists, or because a VM-related API is available. The hypervisor must actually be launched and visible to the caller.
What to verify
- Whether Hyper-V, Windows Hypervisor Platform, Virtual Machine Platform, or VBS features are enabled for the scenario.
- Boot configuration such as hypervisor launch policy and whether the host was rebooted after changing it.
- Firmware settings for hardware virtualization, SLAT, and execute-disable support.
- Whether the code is running inside a guest where the outer host does not expose nested virtualization.
Useful distinction
Do not read this as “the VM does not exist.” It is lower level: the Hyper-V hypervisor itself is absent from the execution environment, so partition, VP, and hypercall operations cannot be serviced there.
References
- Microsoft: Hyper-V architecture
- Microsoft: Hyper-V APIs and Windows Hypervisor Platform
- Linux kernel documentation: Hyper-V overview
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.