| Previous | Next |
| STATUS_HV_INVALID_VTL_STATE | STATUS_HV_INVALID_DEVICE_ID |
STATUS_HV_NX_NOT_DETECTED
The required execute-disable capability is not available to Hyper-V
STATUS_HV_NX_NOT_DETECTED points to the processor execute-disable feature commonly named NX or XD. Hyper-V and virtualization-based security rely on processor memory-protection features, and some paths cannot proceed when execute-disable support is missing or disabled by firmware.
Do not treat this as a guest page-permission problem. It is a host capability/configuration status. The guest may never reach the point where its own kernel can run because the hypervisor cannot establish the required protection model.
What to inspect
- BIOS/UEFI settings for No-Execute Memory Protection, Execute Disable Bit, NX, or XD.
- Whether hardware virtualization, SLAT, and related security features are enabled together.
- Recent firmware reset, BIOS update, security baseline change, or migration to different hardware.
- Host event logs that report hypervisor launch or VBS initialization failures.
Useful distinction
STATUS_HV_NX_NOT_DETECTED is about a platform feature needed by Hyper-V. It is different from STATUS_HV_PAGE_REQUEST_INVALID, which is about a particular device page request that violates guest permissions.
References
- Microsoft: Hyper-V architecture
- Microsoft: Hyper-V feature discovery
- Linux kernel documentation: Hyper-V overview
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.