How To Enable Hyper-V | GUI, PowerShell & Server Role

Hyper-V is enabled through the Windows Features menu on Windows 11 and 10 or by installing the Hyper-V role on Windows Server, followed by a restart.

Enabling Hyper-V on a Windows machine takes one of two routes: turning on the Hyper-V feature on Windows 11 or 10, or installing the Hyper-V role on Windows Server. Both methods end with the same hypervisor ready to run virtual machines, but the steps differ depending on your operating system and whether you prefer a graphical interface or a command-line tool. This article covers the GUI path, the PowerShell and DISM commands, and the Windows Server role installation — along with the hardware requirements your system must meet before any of them work. If you need to know how to enable Hyper-V quickly, the GUI method on Windows 11 or 10 is the most approachable starting point.

What Your System Needs Before You Start

Hyper-V requires a 64-bit processor with Second Level Address Translation (SLAT), VM Monitor Mode extensions, and hardware-assisted virtualization enabled in the BIOS or UEFI firmware. Sufficient memory (at least 4 GB for the host, more for running VMs) is also required. If virtualization is disabled in the firmware, Hyper-V will not install or run, and a system lacking SLAT support will be incompatible no matter which method you try.

Enable Hyper-V On Windows 11 Or 10 (GUI Method)

On Windows 11 and 10, the most stable and approachable way to enable Hyper-V is through the Turn Windows features on or off menu. Open Control Panel, go to Programs > Programs and Features, click Turn Windows features on or off, scroll down to check Hyper-V, and click OK. A restart is required. Once the machine comes back up, Hyper-V Manager and related tools will appear in the Start menu.

Install Hyper-V Using PowerShell Or DISM

For systems where a GUI is not available or scripting is preferred, PowerShell or DISM can enable Hyper-V from an elevated command prompt. Microsoft’s official Hyper-V installation documentation provides the exact commands. In PowerShell running as Administrator, execute Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All and press Y to restart. Alternatively, using DISM in an elevated command prompt, run DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V and reboot. Both methods install the full Hyper-V platform including management tools.

Add The Hyper-V Role On Windows Server

On Windows Server, Hyper-V is installed as a server role through Server Manager rather than the Windows Features dialog. Open Server Manager, click Manage > Add Roles and Features, choose Role-based or feature-based installation, select your server, and check the Hyper-V role. Complete the wizard, confirm the installation, and restart the server. For a cmdlet-driven setup, run Install-WindowsFeature -Name Hyper-V -IncludeManagementTools in an elevated PowerShell session.

Comparison Of Hyper-V Enablement Methods

Method Command or Path Best For
Windows 11/10 GUI Control Panel > Programs > Turn Windows features on or off > Check Hyper-V Single desktop setup and visual users
Windows 11/10 PowerShell Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All Scripting and batch deployments
Windows 11/10 DISM DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V Offline image servicing and recovery environments
Windows Server GUI Server Manager > Add Roles and Features > Hyper-V Role Full server deployments with GUI
Windows Server PowerShell Install-WindowsFeature -Name Hyper-V -IncludeManagementTools Core mode or automated server provisioning

Running Windows 11 Inside Hyper-V

Installing Windows 11 as a guest VM requires a Generation 2 virtual machine with at least 4 GB of memory, 2 virtual processors, TPM, and Secure Boot enabled. Start by creating a new VM and selecting Generation 2 in the wizard. Set Startup memory to 4096 MB and configure the networking. Inside the VM settings, enable Secure Boot with the Microsoft UEFI Certificate Authority template and enable Trusted Platform Module. Windows 11 cannot boot or install correctly on a Generation 1 VM because it lacks the required security features.

Windows 11 VM Requirements In Hyper-V

Setting Required Value Notes
Virtual Machine Generation Generation 2 Required for TPM and Secure Boot support
Startup Memory 4096 MB (4 GB+) Minimum for Windows 11 guest performance
Virtual Processors 2 or more Matches Windows 11 hardware requirements
Secure Boot Enabled (Microsoft UEFI CA) Ensures boot integrity and OS compatibility
Trusted Platform Module Enabled Required for BitLocker and security features

Hyper-V Won’t Enable? Common Fixes

If the Hyper-V option is missing or the installation fails, the three most common culprits are virtualization disabled in the system firmware, a processor that lacks SLAT support, or a pending restart. Boot into your system’s BIOS or UEFI settings and confirm that virtualization (often labeled SVM on AMD or VT-x/VMX on Intel) is turned on. Use the System Information tool in Windows to check for Virtualization Enabled In Firmware. If SLAT is not supported by the CPU, the machine simply cannot run Hyper-V and an alternative hypervisor like VirtualBox may be required. Always restart the host after enabling the feature or role, as the Hyper-V hypervisor loads during the boot process.

Hyper-V Enablement Checklist

  • Verify the CPU supports SLAT, VM Monitor Mode extensions, and 64-bit architecture.
  • Turn on hardware virtualization in the BIOS or UEFI firmware.
  • Choose the correct enablement path for your OS: GUI, PowerShell, or Server Role.
  • Reboot the system to initialize the Hyper-V hypervisor.
  • For Windows 11 guest VMs, create a Generation 2 VM with TPM, Secure Boot, 4 GB+ RAM, and 2 vCPUs.

References & Sources