Virtualization with Windows Server: Hyper-V Explained
Windows Server virtualises with Hyper-V. What it does, the features that matter (checkpoints, Replica, live migration), licensing in brief, and hardware.
3 min readBy Swati
Reviewed by the AmazingRDP technical team

Hyper-V needs real hardware. See our dedicated servers. See Cheap Dedicated Servers from $38.99
A note on the name first: this page's address mentions "Windows Server 2023", and there is no such version. Windows Server releases are named 2016, 2019, 2022 and 2025. What the page is about is the same in all of them: Hyper-V, the virtualisation built into Windows Server, which lets one physical machine run many separate virtual ones.
What Hyper-V is
Hyper-V is a hypervisor: a thin layer that runs directly on the hardware and shares processor, memory, disks and network between virtual machines. Each virtual machine has its own operating system and cannot see the others. Hyper-V is a role you add to Windows Server; a version of it is also in Windows 10 and 11 Pro. How hypervisors work in general is in how hypervisors power virtualisation.
Why virtualise
- Use the hardware fully. One strong server replaces several half-idle ones.
- Separate the jobs. A domain controller, a database and a web server each get their own system, so one's problem or restart does not touch the others.
- Recover quickly. A virtual machine is a set of files; it can be copied, backed up whole and started on other hardware.
- Test safely. Take a checkpoint, try the change, roll back if it fails.
The features that matter
| Feature | What it does |
|---|---|
| Generation 2 virtual machines | Modern virtual hardware with UEFI and Secure Boot; the right choice for current systems |
| Dynamic Memory | Gives a machine more or less memory as it needs it, within limits you set |
| Checkpoints | Save a machine's state to return to. "Production" checkpoints use the guest's backup mechanism and are safe for servers |
| Virtual switches | External (reaches the physical network), internal (host and machines) or private (machines only) |
| Live migration | Moves a running machine to another host without stopping it |
| Hyper-V Replica | Keeps a copy of a machine on a second host, updated every few minutes, for disaster recovery |
| Failover clustering | Restarts machines on another host automatically when one fails |
| Nested virtualisation | Runs Hyper-V inside a virtual machine, for labs and containers |
| Shielded machines and virtual TPM | Protect a machine's disks and state even from the host's administrators |
Storage for clusters without a separate storage system is the subject of Storage Spaces Direct.
What changed between versions
- Windows Server 2022 added nested virtualisation on AMD processors and many security defaults: see Windows Server 2022 features.
- Windows Server 2025 raised the limits for very large machines and added GPU partitioning, which shares one graphics card between several virtual machines: see what is new in Windows Server 2025.
Licensing, in brief
| Edition | Windows Server virtual machines covered |
|---|---|
| Standard | Two per fully licensed host; more by licensing the host's cores again |
| Datacenter | Unlimited on that host |
Licences are counted per physical processor core. Linux virtual machines need no Windows licence. The free, stand-alone "Hyper-V Server" product was last released for 2019. Licensing rules change and have many details; check Microsoft's current terms or ask a licensing partner before you plan a purchase around this table.
Turning it on
Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart
After the restart, open Hyper-V Manager, create a virtual switch, then New, Virtual Machine. The full walk-through with every screen is in enabling Hyper-V on Windows 11 and Windows Server 2022.
Get-VM
Checkpoint-VM -Name web01 -SnapshotName "before update"
Start-VM -Name web01
What the hardware must offer
- A 64-bit processor with virtualisation extensions (Intel VT-x or AMD-V) and second-level address translation, switched on in the firmware.
- Memory for the host (allow 4 GB) plus the sum of the virtual machines.
- Fast storage. Many machines on one slow disk is the usual cause of a sluggish host.
Can I run Hyper-V on a VPS?
Usually not. A VPS is already a virtual machine, and running Hyper-V inside it needs nested virtualisation to be passed through by the provider's host, which is commonly switched off. The Hyper-V role then refuses to install, or virtual machines will not start. For virtual machines of your own, rent a physical machine: on a dedicated server the processor's virtualisation features are yours. Ask support before ordering if Hyper-V is the purpose, so that the build and the Windows edition fit.
Smaller relatives
- Windows Sandbox is a throwaway desktop for trying a program: see installing Windows Sandbox.
- A lab on your own PC with Hyper-V or VirtualBox: setting up a virtual lab.
- Virtual desktops for staff build on the same technology: VDI vs DaaS.
When the management service hangs
If Hyper-V Manager stops responding or machines hang in "stopping", the management service is usually the cause: see fixing a frozen vmms.exe.
Questions
Is there a Windows Server 2023?
No. The versions are 2016, 2019, 2022 and 2025.
What is Hyper-V?
The hypervisor built into Windows Server. It runs several separate virtual machines on one physical server.
How many virtual machines does a Windows Server licence cover?
Standard covers two Windows Server virtual machines per fully licensed host; Datacenter covers unlimited. Check Microsoft's current terms.
Can I run Hyper-V on a VPS?
Usually not, because nested virtualisation is switched off. Use a dedicated server.