Hyper-V cannot be installed because virtualization support is not enabled in the BIOS

Jorge Araujo 20 Reputation points
2025-07-31T15:18:35.51+00:00

I am trying to enable Hyper-V on an Azure VM E4as_v6 running Windows Server 2025 Datacenter Azure Edition.

The spec sheet found at https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/memory-optimized/easv6-series?tabs=sizebasic indicates nested virtualization is supported.

The VM is provisioned with a Security Type of Standard.

When I use the server manager to enable Hyper-V I receive an error message that reads: Hyper-V cannot be installed because virtualization support is not enabled in the BIOS

What steps do I need to take in order to enable Hyper-V?

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.

0 comments No comments

Answer accepted by question author
Jose Benjamin Solis Nolasco 11,541 Reputation points Volunteer Moderator
2025-07-31T15:32:57.7666667+00:00

Hi Jorge,

Thanks for your question. Welcome Microsoft Q&A

You're absolutely right — the E4as_v6 VM does support nested virtualization, but by default, this feature is not enabled on newly created VMs in Azure. The error you’re seeing:

"Hyper-V cannot be installed because virtualization support is not enabled in the BIOS"

…means nested virtualization hasn't yet been explicitly turned on for the VM.

  1. Nested virtualization only works with VMs using a hypervisor-compatible image, such as Windows Server Datacenter editions.
  2. Ensure the VM SKU (like E4as_v6) and Gen 2 VM settings are in place. Gen 2 is required for some advanced scenarios.

Try first this script in a test machine:

Azure CLI


az vm stop \
  --resource-group <YourResourceGroup> \
  --name <YourVMName>

az vm update \
  --resource-group <YourResourceGroup> \
  --name <YourVMName> \
  --set hyperVGeneration=V2 \
  --set additionalCapabilities.enableNestedVirtualization=true

az vm start \
  --resource-group <YourResourceGroup> \
  --name <YourVMName>

💡 Replace <YourResourceGroup> and <YourVMName> with your actual values.

😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.