Hyper-V Not Showing in Windows Features – Fix Guide
Hyper-V missing from Windows Features? Usually the CPU doesn't support virtualization or it's disabled in BIOS. We'll fix both fast.
1. CPU Virtualization Is Disabled in BIOS
The culprit here is almost always the BIOS setting. Hyper-V needs Intel VT-x (or AMD-V) and SLAT (Second Level Address Translation) enabled. If they're off, Hyper-V won't even appear in Windows Features.
Check Your CPU
Open PowerShell or Command Prompt as admin and run:
systeminfo | findstr "Hyper-V"
Look for lines like "Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed." If you see "No" for any requirement, virtualization is off.
Enable Virtualization in BIOS
- Restart your PC and press the BIOS key (F2, Del, F10, Esc – depends on your motherboard).
- Find the virtualization setting – usually under Advanced > CPU Configuration or System Configuration.
- Look for Intel Virtualization Technology, VT-x, or AMD-V. Set it to Enabled.
- Also enable VT-d if you see it – not required but helps.
- Save and exit (usually F10).
Double-check: Some vendors (Lenovo, HP) bury this under Security or Virtualization Extensions. On Dell, it's often under Virtualization Support. On consumer boards, it might be labeled SVM Mode (AMD) or Virtu (some ASUS).
After rebooting, run systeminfo again. You should see all requirements marked "Yes".
2. Windows Update Is Blocking the Install
If virtualization is on but Hyper-V still doesn't show up, check for pending updates. Windows Features sometimes require a specific update (like KB3033929 for older builds). I've seen this a lot on Windows 10 1909 and 21H2.
Update Windows First
- Go to Settings > Update & Security > Windows Update.
- Click Check for updates and install everything.
- Reboot.
- Try turning on Hyper-V again via Control Panel > Programs and Features > Turn Windows features on or off.
If it still doesn't appear, run this command in PowerShell as admin:
DISM /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V /All
That command directly enables Hyper-V, bypassing the GUI list. If it fails with error 0x800F0922, you're missing a requirement – check the next section.
3. Incompatible Hardware or 32-bit
Hyper-V only works on 64-bit systems with SLAT support. If your CPU is old (Intel Core 2 series, AMD Phenom II), it likely lacks SLAT. Also, Hyper-V doesn't run on 32-bit Windows at all – no fix for that.
Check SLAT Support
Run this in PowerShell:
Get-ComputerInfo -Property "HyperV*"
If HyperVRequirementSLAT is False, your CPU can't run Hyper-V. No workaround. You'd need a newer processor (Intel Core i3/5/7/9 3rd gen or later, AMD Ryzen).
Also check RAM: Hyper-V needs at least 4GB of RAM, but 8GB minimum is realistic. Running out of memory won't hide the feature, but it will stop installation.
Don't bother installing third-party hypervisors like VirtualBox or VMware Workstation – they don't fix Hyper-V missing. They just run alongside, but they use different tech.
Quick-Reference Table
| Symptom | Most Likely Cause | Fix |
|---|---|---|
| Hyper-V not in Windows Features list | Virtualization disabled in BIOS | Enable VT-x/AMD-V in BIOS |
| "System does not support Hyper-V" error | Missing SLAT or 32-bit | Check CPU, upgrade hardware |
| Installation fails with 0x800F0922 | Pending updates or missing update | Run Windows Update, then DISM command |
| Hyper-V shows but won't start | Insufficient RAM or CPU | Add RAM or check CPU compat |
That's it. Most of the time, step 1 fixes it. If not, run the DISM command. If that still fails, your hardware's too old. Save yourself the headache – check CPU first.
Was this solution helpful?