This guide covers different methods to install Hyper-V on Windows Server. The Hyper-V role can be installed on a server using PowerShell, Server Manager, or DISM, and this guide provides detailed instructions for all these methods.
Hyper-V provides the services that you can use to create and manage virtual machines and their resources. Each virtual machine is a virtualized computer system that operates in an isolated execution environment. This allows you to run multiple operating systems simultaneously.
To create virtual machines (VMs), you must first enable the Hyper-V role on a Windows Server. Avoid installing the Hyper-V role on a Windows Server that functions as a domain controller. As a best practice, use a dedicated server specifically for enabling the Hyper-V role.

Server Requirements for installing Hyper-V
Hyper-V has specific hardware and operating system requirements. Whereas some Hyper-V features have other requirements. Review the Hyper-V prerequisites documentation before planning the installation.
- Processor: A 64-bit processor with second-level address translation (SLAT).
- Virtual Machine: VM Monitor Mode extensions. Hyper-V can be installed on virtual machines and is fully supported.
- Memory: At least 4 GB of RAM. You need enough memory for the host and all virtual machines that you want to run at the same time.
- Client Operating Systems: Windows 10 Pro /Enterprise, Windows 11 Pro/Enterprise.
- Server Operating Systems: Windows Server 2025, Windows Server 2022, Windows Server 2019.
- BIOS: Virtualization support turned on in the BIOS or UEFI.
- Hardware-enforced Data Execution Prevention (DEP) must be available and enabled.
- Hardware-assisted virtualization must be enabled. This feature is available for processors with Intel Virtualization Technology (Intel VT) or AMD Virtualization (AMD-V) technology.
Check for Hyper-V Requirements
You can quickly determine whether you can install a Hyper-V role on the Windows server. Open Windows PowerShell or a command prompt and type SystemInfo.exe.
Review the Hyper-V requirements section in the report. If all listed requirements show “Yes,” your system supports the Hyper-V role. If any requirement shows “No,” you need to ensure it is installed or enabled.
Hyper-V Requirements: VM Monitor Mode Extensions: Yes
Virtualization Enabled In Firmware: Yes
Second Level Address Translation: Yes
Data Execution Prevention Available: Yes

Ways to Install Hyper-V on Windows Server
There are three methods covered in this guide for installing Hyper-V role on Windows Server. Each of these methods works on all the Server OS versions including Windows Server 2025, 2022, 2019 and 2016.
- Server Manager
- PowerShell
- DISM
1. Install Hyper-V on Windows Server using Server Manager
Launch the Server Manager on Windows Server. Click on Add Roles and Features. On the Select installation type, select Role-based or feature-based installation and click Next.

On the Server Roles page, select Hyper-V role. Selecting this will bring up another window that installs hyper-v management tools to manage this feature.
Hyper-V management tools: Hyper-V Module for Windows PowerShell, Hyper-V GUI Management Tools.
Note: You may choose to install these features on the same server or install it on another server.
In the below example, we’ve selected the management tools to be installed on the same server. Click Add Features and then click Next.

On the Features page, you don’t have to select any feature. Click Next.

Configure the virtual switches to enable Hyper-V virtual machines to communicate with other computers. Your active Ethernet adapter will be populated automatically. Select it and click Next.

Click Next on Virtual Machine Migration page.

Configure the default stores which Hyper-V service uses to store virtual hard disk files and VM configuration files. Click Next.

On the Confirmation page, review the Hyper-V install settings and click Install.

The Hyper-V role installation begins now. During this process, the selected services, tools, and features are installed. The message “Installation succeeded on ServerName” confirms that Hyper-V role installation is successful. You can now start creating virtual machines.

2. Install Hyper-V using PowerShell on Windows Server
The easiest and quickest way to install Hyper-V is using PowerShell. Login to your Windows Server and launch PowerShell with administrator privileges. Run the below PowerShell command to enable Hyper-V role feature on Windows Server.
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
The above command uses the following parameters.
- -Online: Targets the currently running operating system
- -FeatureName Microsoft-Hyper-V: Specifies Hyper-V feature
- -All: Installs all required dependencies
You may have to restart your server after running the above command. Type Y to reboot the computer.

After restarting, you can verify the Hyper-V role installation by running the following PowerShell command.
Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
Next, to verify if the Hyper-V services are running, open the PowerShell and run the below command.
Get-Service -Name *hyper*
3. Enable Hyper-V using DISM on Windows Server
DISM (Deployment Image Servicing and Management) is a command-line tool that can be used to enable Windows features, including Hyper-V. Here’s how to enable Hyper-V using DISM:
- Log in to the Windows Server.
- Launch the Command prompt as administrator.
- Run the following command to enable hyper-v with DISM
DISM /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V-All
This command enables all Hyper-V components, including:
- Hyper-V Platform
- Hyper-V Management Tools
- Hyper-V Services

After restarting, you can use DISM to verify that Hyper-V is installed by running the following command.
DISM /Online /Get-FeatureInfo /FeatureName:Microsoft-Hyper-V
Troubleshooting
If you encounter issues during the Hyper-V role installation on your server, the below points should help you.
- Ensure your hardware supports virtualization, and it’s enabled in BIOS/UEFI.
- Verify you’re using a compatible Windows edition.
- Check that you’re running the command with administrator privileges.
- If you see error code 0x800f0954, it might indicate that the source files couldn’t be found or GPO issues.
Still Need Help?
If you need further assistance on the above article or want to discuss other technical issues, check out some of these options.