Hyper-V is built into Windows 11 Pro, so you don’t need to download anything. It’s just switched off by default. Turn the role on, reboot, and you have a type-1 hypervisor that runs Windows and Linux VMs straight from your desktop — the same engine that powers servers and Azure, scaled down to your laptop.
There are three ways to enable it: the Optional Features dialog, a single PowerShell command, or DISM from a command prompt. They all do the same thing. The GUI is fine for a one-off, PowerShell is faster, and DISM is handy when you’re scripting a build or working in a recovery environment.
Before any of that, two things have to be true: you’re on the right edition, and your hardware supports virtualization. Get those sorted first and the rest takes about five minutes plus a restart.
Check the requirements first
Hyper-V is picky about three things. Miss one and the checkbox stays greyed out or the role fails to start after reboot.
Hyper-V requirements on Windows 11
| Edition | Windows 11 Pro, Enterprise, or Education (not Home) |
|---|---|
| CPU | 64-bit with SLAT (Second Level Address Translation) |
| CPU features | VM Monitor Mode Extensions (VT-x on Intel, AMD-V on AMD) |
| Firmware | Hardware virtualization enabled in BIOS/UEFI |
| RAM | 4 GB minimum; more if you want to run real workloads |
The edition check is the one people miss. Hyper-V simply isn’t in Windows 11 Home — there’s no entry to tick. Open Settings → System → About and look at the Windows edition. If it says Home, you’ll need to move to Pro before any of this works.
For the hardware side, Microsoft ships a quick check. Open an elevated PowerShell window and run:
systeminfoScroll to the bottom, to the Hyper-V Requirements section. You want all four lines — VM Monitor Mode Extensions, Virtualization Enabled In Firmware, Second Level Address Translation, and Data Execution Prevention Available — to read Yes.
If firmware virtualization shows as disabled, reboot into your BIOS/UEFI (usually Del, F2, or F10 at the splash screen) and turn on Intel Virtualization Technology / VT-x or SVM Mode on AMD. Save, exit, and recheck before continuing.
Method 1: Optional Features (the GUI way)
This is the click-through method, good when you’re enabling Hyper-V once on your own machine.
- Press
Win + R, typeoptionalfeatures, and press Enter. - In the Windows Features dialog, find Hyper-V.
- Tick the Hyper-V box. Expand it and confirm both Hyper-V Platform and Hyper-V Management Tools are checked.
- Click OK. Windows installs the components.
- Click Restart now when prompted.
That’s it. After the reboot, Hyper-V Manager shows up in the Start menu.
Method 2: PowerShell (one command)
If you’d rather not click through dialogs, PowerShell does the whole thing in one line. Open PowerShell as Administrator and run:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -AllThe -All switch pulls in every dependency, including the management tools and the virtual switch components. When it finishes, it asks whether to restart — answer Y, or reboot yourself later.
To confirm the role is actually enabled after the reboot:
Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V | Select-Object FeatureName, StateA State of Enabled means you’re done.
Method 3: DISM (for scripts and recovery)
DISM works from an elevated Command Prompt or PowerShell and is the go-to when you’re building images, automating deployments, or running outside a normal desktop session. The feature name is slightly different from the PowerShell cmdlet:
DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V/Online targets the running OS, and /All enables the parent features Hyper-V depends on. Reboot when it completes.
Here’s how the three methods line up so you can pick one:
Which install method to use
| optionalfeatures (GUI) | One-off setup on your own machine; you want to see the checkboxes |
|---|---|
| Enable-WindowsOptionalFeature | Fast, scriptable, and easy to verify with Get-WindowsOptionalFeature |
| DISM /Enable-Feature | Build scripts, imaging, or a recovery/offline environment |
All three need a restart, and all three end in the same place: the hypervisor loaded at boot and Hyper-V Manager available.
Verify the install and open Hyper-V Manager
After the reboot, check that the hypervisor is actually running, not just installed:
Get-ComputerInfo -Property "HyperVisorPresent"If it returns True, the hypervisor launched at boot. Now open the console — press Start and type Hyper-V Manager, or run virtmgmt.msc. Your computer name appears in the left pane.
Post-install checklist
- Reboot completed after enabling the role
- Get-ComputerInfo shows HyperVisorPresent = True
- Hyper-V Manager opens and lists your machine
- A virtual switch exists (create one before building network-connected VMs)
- Default VM storage path set to a drive with free space
One thing the install doesn’t do is give your VMs network access. Hyper-V on Windows 11 ships with a Default Switch (NAT-based) that works out of the box, but for VMs that need to look like real machines on your LAN you’ll want to build an external switch. That’s a short job on its own — see how to create an external virtual switch in Hyper-V.
Build your first VM
With the role on, creating a VM is quick. In Hyper-V Manager, click Action → New → Virtual Machine, or use PowerShell:
New-VM -Name "Lab-VM01" -MemoryStartupBytes 4GB -Generation 2 -NewVHDPath "D:\VMs\Lab-VM01.vhdx" -NewVHDSizeBytes 60GB -SwitchName "Default Switch"A few notes on those values:
- Generation 2 is the modern default — UEFI firmware, Secure Boot, and support for current Windows and most recent Linux distros. Stick with it unless you’re booting something old that needs legacy BIOS. If you’re unsure, read up on Generation 1 vs Generation 2 VMs.
- MemoryStartupBytes is the starting RAM. You can enable Dynamic Memory later so the VM only uses what it needs.
- SwitchName connects the VM to a network. The built-in Default Switch gives NAT-based internet immediately.
Attach an ISO and start the VM:
Add-VMDvdDrive -VMName "Lab-VM01" -Path "D:\ISOs\windows11.iso"
Start-VM -Name "Lab-VM01"Then connect to its console with vmconnect or by double-clicking the VM in Hyper-V Manager.
Wrapping up
Installing Hyper-V on Windows 11 Pro comes down to two checks and one switch: confirm you’re on Pro (or Enterprise/Education), confirm the CPU has SLAT with virtualization enabled in firmware, then flip the role on through Optional Features, Enable-WindowsOptionalFeature, or DISM. Reboot, and Hyper-V Manager is ready.
From there, build a Generation 2 VM, point it at the Default Switch for instant networking, and you’ve got a clean lab to test Windows builds, try Linux distros, or stage a server config before it touches production. For more setup walkthroughs and fixes, browse the virtualization guides.
