Virtualized Intel VT-x/EPT is not supported on this platform

The error occurs because multiple virtualization stacks are competing for the same hardware virtualization extensions (Intel VT‑x/EPT). Hyper‑V and Hyper‑V–based security features (such as Memory Integrity / Core Isolation, Credential Guard, etc.) reserve VT‑x/EPT, so third‑party hypervisors like EVE‑NG, VMware, or VirtualBox cannot use them.

To run EVE‑NG with nested virtualization (for Palo Alto, Fortigate, etc.), all Hyper‑V and Hyper‑V–based features must be fully disabled so that VT‑x/EPT is exposed directly to the third‑party hypervisor. The context explains that third‑party virtualization apps and Hyper‑V cannot share the hardware virtualization extensions and that this behavior is by design.

Follow these steps in order (some may already have been tried, but all must be true at the same time):

1. Disable Hyper‑V and Hyper‑V–based features
   • Open Turn Windows features on or off.
   • Clear (uncheck) at least the following entries:
     • Hyper‑V (all sub‑components)
     • Virtual Machine Platform
   • Select OK and restart the PC.
2. Ensure virtualization is enabled only in firmware (UEFI/BIOS)
   • Virtualization (Intel VT‑x / AMD‑V) must be enabled in UEFI/BIOS so that Windows and hypervisors can see it.
   • Use the OEM‑specific instructions referenced in the “Enable Virtualization on Windows” article to confirm VT‑x is enabled in firmware. Only change the virtualization‑related setting; avoid other firmware changes.
3. Confirm no Microsoft hypervisor is active
   • After reboot, verify that Hyper‑V is not running. If any Hyper‑V–based feature is still active, third‑party virtualization will either fail to start VMs or fall back to slow emulation, as described in the “Virtualization applications don't work together with Hyper‑V and Hyper‑V-based features” article.
   • If Hyper‑V or Memory Integrity is re‑enabled later, the error about virtualized VT‑x/EPT will reappear.
4. Use nested virtualization only where supported
   • Nested virtualization (Hyper‑V inside a VM) is supported only for Hyper‑V guests. The documentation explicitly states that non‑Microsoft virtualization applications that require hardware virtualization extensions are not supported inside Hyper‑V VMs and are likely to fail.
   • Therefore, EVE‑NG and its nested firewalls must run either:
     • Directly on bare metal (with Hyper‑V fully disabled), or
     • In a Hyper‑V VM only if EVE‑NG does not require direct VT‑x/EPT (which is typically not the case for advanced firewall images).

If EVE‑NG is running inside a Hyper‑V VM and nested VT‑x/EPT is required, this configuration is unsupported according to the context: Hyper‑V does not support non‑Microsoft hypervisors inside its VMs when they need hardware virtualization extensions.

References:

• Virtualization applications don't work together with Hyper-V and Hyper-V-based features
• Enable Virtualization on Windows
• What is Nested Virtualization?
• Run Hyper-V in a Virtual Machine with Nested Virtualization