Windows Server 2025 / How to Install Hyper-V
Hyper-V on Windows Server 2025 requires supported hardware virtualization and sufficient host resources. Install the role, restart, and verify the hypervisor and management services before configuring virtual networks and guest machines.
Separate the host from its guests
The host provides physical resources and manages virtual machines (VMs); each guest runs inside one VM. Host failure or storage exhaustion can affect several guests simultaneously.
Use a separate Windows Server 2025 host named HV1. Do not add the role casually to DC1 or FS1. If Hyper-V already hosts the course VMs, inspect that existing host rather than reinstalling. Running HV1 inside another hypervisor requires a separately supported nested-virtualization design.
Production hosts need management, update, and backup plans before workloads. Installing Hyper-V and obtaining guest OS use rights are separate issues.
Check hardware and resource budgets
- Verify a compatible 64-bit CPU, Second Level Address Translation (SLAT), and VM monitor extensions.
- Check enabled firmware virtualization and data execution prevention support.
- Budget host memory as well as simultaneous guest startup allocations.
- Allow storage for VMs, updates, checkpoints, growth, and exports.
systeminfo
Read systeminfo’s Hyper-V requirements. If a hypervisor is already detected, individual capability lines may be replaced by that notice. Review Hyper-V requirements and feature-specific additions. Minimum memory is not a capacity plan for several server guests. For missing firmware options, consult the hardware vendor and actual hosting environment.
Install through Server Manager
- Retain console or independent management access and prepare for restart.
- Open Manage → Add Roles and Features.
- Choose role-based installation and verify target HV1.
- Select Hyper-V and supported management tools.
- Defer physical-adapter switch creation if networking is not yet planned.
- Review default configuration and virtual disk storage paths.
- Install, inspect the result, and restart in the planned window.
An external switch can interrupt host networking. Do not combine it with remote-only installation without recovery access. Changing a default storage path does not move existing VM files.
Use PowerShell as an alternative
On HV1 in elevated Windows PowerShell, follow Microsoft’s installation procedure. Omit automatic -Restart to control its timing, and do not repeat installation after the GUI method:
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools Get-WindowsFeature -Name Hyper-V,Hyper-V-Tools,Hyper-V-PowerShell
Check Success and Restart Needed before rebooting. Tools installed on a management PC are not the same as a host running the hypervisor. For failures, correlate installation messages, events, firmware settings, and available resources.
Verify after restart
Get-WindowsFeature -Name Hyper-V Get-Service -Name vmms Get-VMHost | Select-Object ComputerName,VirtualMachinePath,VirtualHardDiskPath Get-VM
Confirm Installed role state, running Virtual Machine Management service (vmms), and an error-free management connection to HV1. An empty Get-VM list is expected before guests exist. Opening the console alone does not prove a guest can start; verify that with a separate test VM later.
For guest startup failures, record the time and message and inspect memory and hypervisor state. Before removing the role, inventory VMs and plan their backup or relocation. Role removal is not a VM backup.
