How do I check Windows Server Hyper-V prerequisites on a dedicated server?
Hyper-V requires a supported 64-bit processor, hardware virtualization and the other platform capabilities specified for the target Windows Server release. Second Level Address Translation and firmware configuration matter; enough RAM is needed for both the host and planned guests. Hardware readiness does not by itself settle operating-system or application licensing requirements.
Before you start
- Authorised PowerShell access on the target Windows Server host.
Instructions
1. Read the hardware requirements report
Run systeminfo on the intended Windows Server host. Review the Hyper-V requirements section and compare the result with Microsoft’s requirements for the installed release.
systeminfo.exeIf a hypervisor is already running, the output can state that a hypervisor was detected instead of listing each requirement. Protect product and machine identifiers when sharing the report.
2. Inspect the server role state
Use the ServerManager module on Windows Server to determine whether the Hyper-V role is already installed. This is a status query, not role installation.
Get-WindowsFeature -Name Hyper-VReview Install State. Installation and host networking changes need a separate maintenance plan, including any required restart and guest resource allocation.
Check the result
- The target Windows Server release and hardware are supported, required firmware settings are enabled, and the role’s current state is understood before deployment.
Troubleshooting
- Get-WindowsFeature is unavailable
- Confirm that the command is running on Windows Server with ServerManager available; Windows client editions use different feature tools.
- Firmware virtualization is reported disabled
- Arrange a model-specific firmware change and planned restart through the console.
- Requirements pass but a VM cannot start
- Review its configuration, available resources and Hyper-V event logs rather than repeating the CPU check alone.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.