| Previous | Next |
| ERROR_HV_NOT_ALLOWED_WITH_NESTED_VIRT_ACTIVE | ERROR_VID_DUPLICATE_HANDLER |
ERROR_HV_NOT_PRESENT
Installed virtualization components do not prove the hypervisor launched
ERROR_HV_NOT_PRESENT means the caller cannot communicate with a running Hyper-V hypervisor on the system. Windows features and management services may be installed while the hypervisor is disabled in boot configuration, blocked by missing hardware virtualization or NX support, or unavailable because the machine is itself an unsupported guest.
Check firmware virtualization and execute-disable settings, Hyper-V host requirements, boot configuration, and hypervisor-related system events. Use documented feature discovery rather than inferring presence from a service name. If this occurs inside a VM, determine whether nested virtualization is supported and exposed; installing Hyper-V in the guest alone does not create hardware virtualization extensions.
Presence checks in the correct order
- Hardware virtualization, SLAT, and NX/XD firmware state.
- Windows feature installation and hypervisor launch configuration.
- Hypervisor-present CPUID/interface discovery result.
- Physical-host versus nested-guest execution environment.
References
- Microsoft: Hyper-V host hardware requirements
- Microsoft TLFS: hypervisor presence and feature discovery
- Linux kernel: detecting and communicating with Hyper-V
Looking for a different code? Search another status or error code.