ANAVEM
Reference
Languagefr
Install Hyper-V on Windows Server Using 3 Different Methods

Install Hyper-V on Windows Server Using 3 Different Methods

Install the Hyper-V role on Windows Server 2019/2022/2025 using Server Manager GUI, PowerShell (Install-WindowsFeature), or DISM — with prerequisites, post-install verification, and troubleshooting steps.

Emanuel DE ALMEIDA
3/14/2026 15 min 4
mediumhyper-v 6 steps 15 min

Overview

Hyper-V is Microsoft's native Type 1 hypervisor available in Windows Server 2019, 2022, and 2025. It requires a 64-bit processor with Second Level Address Translation (SLAT), minimum 4 GB RAM for production environments, and hardware virtualization enabled in BIOS/UEFI.

This tutorial covers three installation methods: (1) Server Manager GUI — Add Roles and Features wizard; (2) PowerShell — Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart; and (3) DISM — DISM /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V /All. All three methods require a system restart, and post-installation verification is included.

Implementation Guide

Full Procedure

01

Verify System Requirements and Enable Hardware Virtualization

Before installing Hyper-V, check that your system meets the hardware requirements and has virtualization enabled in BIOS/UEFI.

Open PowerShell as Administrator and run this command to check processor compatibility:

Get-ComputerInfo | Select-Object -Property "CsProcessors", "CsTotalPhysicalMemory", "WindowsProductName"

Verify hardware virtualization support:

Get-WmiObject -Class Win32_Processor | Select-Object Name, VirtualizationFirmwareEnabled, SecondLevelAddressTranslationExtensions

If virtualization shows as disabled, restart your server and access BIOS/UEFI settings. Look for options like "Intel VT-x", "AMD-V", or "Virtualization Technology" and enable them.

Warning: Without hardware virtualization enabled, Hyper-V installation will fail. This must be configured at the firmware level before proceeding.
02

Method 1 - Install Hyper-V Using Server Manager GUI

The Server Manager provides the most user-friendly approach for installing Hyper-V, especially for administrators who prefer graphical interfaces.

Launch Server Manager from the taskbar or Start menu. Click Manage in the top-right corner, then select Add Roles and Features.

In the Add Roles and Features Wizard:

  1. Select Role-based or feature-based installation and click Next
  2. Choose your destination server from the server pool and click Next
  3. On the Server Roles page, scroll down and check Hyper-V
  4. When prompted, click Add Features to include management tools
  5. Click Next through the Features page
  6. On the Hyper-V page, review the information and click Next
  7. Configure Virtual Switches by selecting your network adapter or skip for later configuration
  8. Set Virtual Machine Migration settings (typically leave default) and click Next
  9. Choose default store locations for virtual hard disks and configuration files
  10. Review your selections and click Install

The installation will take several minutes. When complete, click Restart the destination server automatically if required and then Close.

Pro tip: During virtual switch configuration, avoid selecting Wi-Fi adapters as they don't support external virtual switches reliably.
03

Method 2 - Install Hyper-V Using PowerShell Commands

PowerShell offers the fastest installation method and is ideal for automation or remote installations.

Open PowerShell as Administrator and run this single command to install Hyper-V with all management tools:

Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart

This command will:

  • Install the Hyper-V role
  • Include all management tools (Hyper-V Manager, PowerShell modules)
  • Automatically restart the server when installation completes

If you prefer to restart manually, use this command instead:

Install-WindowsFeature -Name Hyper-V -IncludeManagementTools

Then restart manually:

Restart-Computer -Force

For Server Core installations without GUI, install only the Hyper-V tools:

Install-WindowsFeature -Name Hyper-V-Tools -IncludeAllSubFeature
Pro tip: Use -WhatIf parameter to preview what will be installed without making changes: Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -WhatIf
04

Method 3 - Install Hyper-V Using DISM Commands

DISM (Deployment Image Servicing and Management) provides low-level feature management and works well for scripted deployments or offline installations.

Open Command Prompt or PowerShell as Administrator and run:

DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V

This enables all Hyper-V components. For more granular control, you can install specific components:

DISM /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V-All

To install only the Hyper-V platform without management tools:

DISM /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V

Add management tools separately:

DISM /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V-Management-PowerShell
DISM /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V-Management-Clients

After installation completes, restart the server:

shutdown /r /t 0

For offline installations (modifying a Windows image), mount the WIM file and use:

DISM /Image:C:\mount /Enable-Feature /FeatureName:Microsoft-Hyper-V /All
Warning: DISM commands are case-sensitive. Use exact feature names as shown, or the installation will fail silently.
05

Verify Hyper-V Installation and Configure Basic Settings

After the server restarts, verify that Hyper-V installed correctly using multiple verification methods.

Check installation status with PowerShell:

Get-WindowsFeature *Hyper-V*

You should see output showing Hyper-V features with "Install State" as "Installed". Verify the Hyper-V service is running:

Get-Service vmms

The Virtual Machine Management Service (vmms) should show Status as "Running".

Launch Hyper-V Manager from Server Manager Tools menu or run:

virtmgmt.msc

In Hyper-V Manager, you should see your server listed in the left pane. Right-click your server name and select Hyper-V Settings to configure:

  • Virtual Hard Disks: Default location for new VHD files
  • Virtual Machines: Default location for VM configuration files
  • Physical GPUs: Enable RemoteFX if supported
  • Enhanced Session Mode Policy: Allow enhanced connections

Create your first virtual switch by right-clicking your server and selecting Virtual Switch Manager. Choose External for production VMs that need network access.

Pro tip: Set up a dedicated drive or partition for VM storage. This improves performance and makes backup management easier.
06

Create and Test Your First Virtual Machine

Test your Hyper-V installation by creating a simple virtual machine to ensure everything works correctly.

In Hyper-V Manager, right-click your server and select New > Virtual Machine. The New Virtual Machine Wizard will open:

  1. Specify Name and Location: Enter a name like "Test-VM" and choose storage location
  2. Specify Generation: Choose Generation 2 for modern operating systems (supports UEFI and Secure Boot)
  3. Assign Memory: Allocate at least 2048 MB (2 GB) for Windows Server VMs
  4. Configure Networking: Select your virtual switch or "Not Connected" for testing
  5. Connect Virtual Hard Disk: Create new VHD with 40 GB minimum size
  6. Installation Options: Choose to install from ISO file or network later

After creating the VM, verify it appears in Hyper-V Manager. Right-click the VM and select Settings to review configuration.

Test VM functionality by starting it:

Start-VM -Name "Test-VM"

Check VM status:

Get-VM -Name "Test-VM" | Select-Object Name, State, Status

Connect to the VM console by double-clicking it in Hyper-V Manager or using:

vmconnect.exe localhost "Test-VM"

If the VM starts successfully and you can access the console, your Hyper-V installation is working correctly.

Warning: Generation 2 VMs require UEFI-compatible operating systems. Use Generation 1 for older OS versions or if you encounter boot issues.

Frequently Asked Questions

Can I install Hyper-V on Windows Server Core without GUI?+
Yes, you can install Hyper-V on Windows Server Core using PowerShell or DISM commands. Use 'Install-WindowsFeature -Name Hyper-V -IncludeManagementTools' in PowerShell or 'DISM /Online /Enable-Feature /FeatureName:Microsoft-Hyper-V /All' in Command Prompt. You'll manage VMs remotely using Hyper-V Manager from another machine or PowerShell cmdlets directly on the Core server.
What happens if hardware virtualization is not enabled in BIOS?+
Hyper-V installation will fail if hardware virtualization (Intel VT-x or AMD-V) is not enabled in BIOS/UEFI. You'll receive an error during installation or when trying to start VMs. You must restart the server, enter BIOS/UEFI settings, find virtualization options (often under CPU or Security settings), enable them, save changes, and reboot before attempting Hyper-V installation again.
Which Hyper-V installation method is fastest for multiple servers?+
PowerShell is the fastest method for multiple servers, especially when combined with remote execution. Use 'Invoke-Command -ComputerName Server1,Server2,Server3 -ScriptBlock {Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart}' to install on multiple servers simultaneously. DISM is also scriptable but requires more commands. Server Manager GUI is slowest and not suitable for bulk deployments.
Do I need to restart Windows Server after installing Hyper-V?+
Yes, a restart is mandatory after installing Hyper-V because it installs a hypervisor that runs beneath the Windows operating system. The restart loads the hypervisor and converts your Windows Server into a parent partition. Without restarting, Hyper-V services won't start properly and you cannot create or run virtual machines. All three installation methods require this restart.
Can I install Hyper-V on Windows Server 2025 Evaluation edition?+
Yes, Hyper-V is available on Windows Server 2025 Evaluation edition with full functionality for 180 days. The evaluation includes both Standard and Datacenter features, so you can test all Hyper-V capabilities including live migration, replica, and clustering. After evaluation expires, you can convert to licensed version using 'DISM /Online /Set-Edition' command with a valid product key without reinstalling.
Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...