Hyper-V is missing from Windows Features or cannot be enabled

Troubleshooting guideSources checked: 2026-09-05FaultNote editorial team

What to do first

Hyper-V is missing from Windows Features or cannot be enabled. The PC may run Home edition, lack a SLAT-capable CPU, have firmware virtualization disabled, or have hypervisor launch disabled in boot configuration. Record the current state before changing it, use only the supported Windows path described below, and verify the same operation again after any required restart.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product: Hyper-V
Versions and conditions: Windows 11 (confirm the edition and hardware requirements for the feature)
Error codes and identifiers: Hyper-V

Symptoms

Hyper-V is missing from Windows Features or cannot be enabled.
The same condition can persist after a retry or restart.

Causes and conditions

The PC may run Home edition, lack a SLAT-capable CPU, have firmware virtualization disabled, or have hypervisor launch disabled in boot configuration.

Before you start

Save open documents and allow time for a Windows restart if required.
Run administrative actions only on a personally managed PC or with administrator approval.
Save the diagnostic command output so the before and after states can be compared.

Precautions

Do not bulk-delete registry entries, system folders, credentials, or storage metadata.
Do not run unofficial scripts or unknown drivers with administrator rights.

Hyper-V troubleshooting sequence: Check the Windows edition; Check the state with systeminfo.exe; Repair through the supported path; Enable Hyper-V in Windows Features; Verify under the same conditions — Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

01
Check the Windows edition
#
Open Settings > System > About and read Windows specifications. A missing Hyper-V role on Home is expected. Supported editions also require CPU SLAT support and firmware virtualization.
02
Check the state with systeminfo.exe
#
Check the Windows edition and all four Hyper-V Requirements entries.
Command or path
```
systeminfo.exe
```
03
Repair through the supported path
#
On a supported Pro or Enterprise edition, enable firmware virtualization through the PC maker's model-specific procedure, select Hyper-V in Windows Features, and restart.
04
Enable Hyper-V in Windows Features
#
Search Start for Turn Windows features on or off and expand Hyper-V. Check whether Hyper-V Platform, as well as the management tools, is selectable. If it is greyed out, inspect the requirement shown. Enable it only on a supported system, then restart.
05
Verify under the same conditions
#
Run Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All and repeat the original operation once under the same conditions. If it succeeds, verify again after a restart and record the setting that changed.
Check that no new critical event with the same timestamp and component appears in Event Viewer.
Command or path
```
Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
```

Check the result

The feature starts, connects, or completes without the original error.
The verification command reports the expected enabled, healthy, or connected state.
The result remains correct after a Windows restart and no new matching critical event appears.

If the problem continues

If the same code persists, provide the full message, Windows build, command output, and occurrence time to the PC administrator or Microsoft Support.
If hardware requirements, organization policy, or server settings are responsible, ask the owner to make the change instead of bypassing it on the client.

Scope of this guide

Troubleshooting guide — Restore the feature so it starts, connects, or completes normally and passes the same verification after a Windows restart.

Frequently asked questions

Can Hyper-V run on Windows Home?

The Hyper-V role requires a supported Pro or Enterprise edition. A missing feature entry on Home is expected.

Why does systeminfo say a hypervisor was detected?

That message means a hypervisor is already running; individual requirement lines can be omitted, so also check feature state.

Official sources and dates

System requirements for Hyper-V on Windows and Windows Server ↗

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

← Search English guides