Hyper-V client virtualization
Answer: Client Hyper-V can be enabled on Windows 10 or Windows 11 Pro and Enterprise; Windows Home is not a supported Hyper-V host edition.
Administrator playbook
Decide, verify, and document
Use the curated answer as a starting point, then prove the outcome against the target tenant or device.
What it means
- Hardware virtualization and second-level address translation are required
- Virtualization must be enabled in firmware
- Some Hyper-V capabilities have additional hardware requirements
What to check next
- Run Systeminfo and review the Hyper-V Requirements section
- Confirm the installed edition is Pro or Enterprise
- Check for conflicts with other virtualization or security requirements
Verify success
- Confirm the feature is present or enabled on the target edition and build.
- Test the intended workflow with a pilot device and least-privileged user.
- Confirm policy reports success from the actual management authority.
Escalate when
- The documented edition and hardware requirements are met but the feature is absent.
- Policy reports success while the user or device state is incorrect.
- Licensing or OEM terms—not technical prerequisites—control the outcome.
Copyable admin briefAnswer, next checks, source, and review date
Capture edition and build
Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,OsBuildNumber,OsArchitectureRead-only. Edition and exact build often control availability.
List optional feature state
Get-WindowsOptionalFeature -Online | Where-Object State -ne "Disabled" | Select-Object FeatureName,StateRead-only. Not every Windows capability is represented as an optional feature.
Evidence to preserve
- Windows edition, version, and build
- Hardware and firmware prerequisites
- Management authority and policy source
- Required user or device experience