What Is Hyper-V? Setup, Use Cases and Hyper-V vs VMware

Updated: October 2026

If you run Windows servers, you already own a hypervisor. It ships inside Windows Server and inside the Pro and Enterprise editions of Windows 11, and turning it on takes one command. This guide explains what Hyper-V is, where it runs, how to set it up properly, and how it compares with VMware for a small IT team deciding where its virtual machines should live.

TL;DR

• Hyper-V is Microsoft's type-1 hypervisor. It's built into Windows Server and Windows 11 Pro, Enterprise and Education, with no separate download and no extra hypervisor licence.
• On a PC it's a test lab. On Windows Server it's a production platform with clustering, live migration and replication.
• Pick Generation 2 VMs unless something forces Generation 1. You can't change it later.
• Checkpoints roll a VM back. They're not backups.
• Windows Server Standard covers two Windows VMs per licence, Datacenter covers unlimited. That licence, not Hyper-V, is where the cost sits.
• After Broadcom's VMware changes, Hyper-V is the default shortlist entry for Windows-heavy shops. Moving still takes planning.

What Is Hyper-V?

Hyper-V is the virtualization layer Microsoft builds into Windows. It lets one physical machine run several virtual machines, each with its own operating system, CPU share, memory and disks. Microsoft describes it as a type-1 hypervisor, which means it runs directly on the hardware rather than as an app inside Windows.

That detail surprises people the first time they enable it. Once Hyper-V is on, the Windows you log into becomes a privileged partition sitting beside the VMs, not underneath them. Everything still looks the same on screen. Under the hood, the hypervisor now owns the CPU and hands out time to the host OS and each guest.

John Savill's overview walks through the architecture, and it's the clearest visual explanation of partitions we've seen.

Guests can be Windows, Linux or FreeBSD. The host keeps the management role: it runs Hyper-V Manager, the virtual switches and the drivers that talk to real hardware. If you want the wider picture of hypervisors and why companies virtualize at all, start with our what is virtualization explainer.

Where Hyper-V Runs: Windows 11, Windows Server and Azure Local

The same hypervisor shows up in three products, and they're built for different jobs.

Windows 10 Home and Windows 11 Home can't run the Hyper-V role at all. If a user on a Home laptop asks for VMs, the answer is an edition upgrade or a different hypervisor.

There used to be a fourth option: Hyper-V Server, a free, GUI-less edition that did nothing but host VMs. Microsoft still offers Hyper-V Server 2019 as a free download, and calls it "a free product that delivers enterprise-class virtualization". No newer version followed it. Windows Server 2019, the release it's built on, is supported until January 2029, so treat it as a lab option, not a place to start something new.

Azure Local is the product Microsoft's own docs still sometimes call Azure Stack HCI in older release notes. It's aimed at larger or regulated sites. For a 30-person office it's usually more platform than the problem needs.

How to Enable Hyper-V

Hyper-V is an optional Windows feature, so there's nothing to download. Check the hardware first. Microsoft lists a 64-bit processor with Second Level Address Translation (SLAT), CPU virtualization extensions and at least 4 GB of RAM.

The extensions also have to be switched on in firmware. On a lot of business laptops and desktops, Intel VT-x or AMD-V ships disabled. Our guide on how to enable virtualization in BIOS covers the setting names by vendor and how to push the change across a fleet.

On Windows 11, open an elevated PowerShell window and run:

powershell
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

DISM does the same job:

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

On Windows Server, install the role with the management tools and let it restart:

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

On Server Core, that command installs the PowerShell module but not Hyper-V Manager. Manage those hosts remotely from another machine.

One conflict catches techs out. Microsoft warns that other virtualization apps that rely on the same CPU features, such as VMware Workstation and VirtualBox, might not start their VMs or might run them unreliably while the Hyper-V hypervisor is running. If a developer's old VirtualBox lab breaks the day Hyper-V goes on, that's why.

Generation 1 vs Generation 2 VMs

Every Hyper-V VM is created as Generation 1 or Generation 2, and you can't change it afterwards. Microsoft recommends Generation 2 unless the guest OS, the boot method or an existing disk image forces Generation 1.

The Windows 11 row settles it for new builds. Windows 11 needs UEFI, Secure Boot and a TPM, and only Generation 2 offers all three.

Generation 1 still earns its place for old 32-bit guests and for VHD files built under legacy BIOS. For Linux guests with Secure Boot, pick the UEFI CA template when you create the VM, or the guest won't boot.

Virtual Switches: External, Internal and Private

VMs reach the network through a virtual switch, a software layer-2 switch that lives on the host. Hyper-V offers three types, and the wrong pick is behind a lot of "my VM has no internet" tickets.

An external switch binds to a physical network adapter, so VMs sit on the real network like any other machine. An internal switch connects VMs to each other and to the host, but not to the outside network. A private switch connects VMs only to each other, with no path to the host at all.

On a server, the usual pattern is one external switch for VM traffic, with "Allow management operating system to share this network adapter" decided deliberately. Sharing is convenient on a single-NIC box. On a host with spare ports, keeping management traffic on its own adapter is cleaner and easier to firewall.

Private switches are handy for malware analysis or testing a domain controller build, where nothing inside should reach the office network by accident.

Sizing a Hyper-V Host

Memory is usually the first thing a small host runs out of. CPU cores are shared well between VMs, but RAM given to a VM is RAM the host can't use for anything else.

Add up what each VM needs at its busy hour, then leave headroom for the management OS and for growth. Dynamic Memory helps here. It lets Hyper-V adjust a VM's allocation to what the workload uses, which suits file servers and Remote Desktop hosts that swing through the day. Keep it off for SQL Server and other apps that manage their own memory.

Storage is the second pinch point. Four VMs on one pair of spinning disks will feel slow long before the CPU is busy. SSD or NVMe for the VM volumes, with the host OS on its own disk, is the simple default for a small server.

If you plan a second host for Replica or clustering, size each host to carry every VM on its own. That spare capacity is what lets you patch one host while the other keeps the business running.

Checkpoints Are Not Backups

A checkpoint saves a VM's state so you can roll back after a bad update or config change. It's one of the best reasons to virtualize, and one of the easiest features to misuse.

Hyper-V has two kinds. Standard checkpoints capture the disk and the memory state, so applying one puts the VM back exactly where it was, open apps included. Production checkpoints use VSS inside Windows guests, or a file-system freeze on Linux, to take a data-consistent copy without the memory. Production is the default.

Microsoft's own wording is blunt about standard checkpoints: "A snapshot is not a full backup and can cause data consistency issues with systems that replicate data between different nodes such as Active Directory." Rolling a domain controller back with a standard checkpoint is how you get replication problems that take a day to untangle.

Checkpoints also live on the same storage as the VM, as .avhdx files beside the .vhdx. If the host's disks die, the checkpoints die with them. They grow as the VM changes, and deleting one triggers a merge. Never delete the .avhdx files by hand.

Use checkpoints for the hour around a change, then delete them. For real backups, use a tool that talks to Hyper-V through VSS and keeps copies off the host. Our guide on incremental vs differential backup covers how those chains work.

Then prove the copies restore. A backup that has never been restored is a guess, and our disaster recovery testing guide lays out five test types, from a single-file restore to a full failover.

Licensing: Hyper-V Is Free, Windows Guests Aren't

Hyper-V itself adds no licence cost. It comes with Windows Server and with the Pro and Enterprise editions of Windows. What you pay for is the right to run Windows inside the VMs.

Microsoft's Windows Server 2025 pricing page spells out the split. Standard edition covers "2 virtual machines, plus one Hyper-V host per license". Datacenter covers "unlimited virtual machines, plus one Hyper-V host per license".

In practice, a host with two or three Windows Server VMs often fits Standard. Stack Standard licences as the VM count grows, and at some point Datacenter works out cheaper. Linux guests don't need Windows Server licences at all, though they bring their own support terms.

This is where small environments drift. Someone spins up a "temporary" VM for a new app, then another, and the licence count never moves.

When Small Businesses Use Hyper-V

For a Windows-first office, Hyper-V is the obvious host for the usual handful of servers: a domain controller, a file server, a Remote Desktop host and one line-of-business app. The hypervisor is already paid for, the team already knows Windows, and Windows Admin Center gives a browser console without extra software.

The design question is how much resilience the business needs. One host with good backups is fine when a day of downtime is survivable. Two hosts with Hyper-V Replica add a warm standby: Microsoft says replication RPO can be as low as 30 seconds, and it runs over ordinary network links without a SAN. A failover cluster with shared storage adds automatic restart and live migration, and adds cost and complexity to match.

This r/sysadmin thread is a good snapshot of that trade-off. A tech with a 50-user client was quoted around CAD$143K for two servers and a SAN, for four VMs.

The top replies questioned whether four VMs needed high availability at all, and suggested two-node shared storage instead of a dedicated array. That's the right instinct. Size the design to what an hour of downtime costs the business, not to what the reference architecture looks like.

Hyper-V vs VMware After Broadcom

Broadcom's changes to VMware licensing sent a lot of teams looking at alternatives, and Hyper-V is usually on the list for anyone already paying for Windows Server Datacenter. Our separate guide to vSphere covers what changed on the VMware side.

The concepts map closely, so the learning curve is gentler than it looks:

The migration is where the real work sits. VMs need converting, drivers and leftover VMware tools need cleaning out, backup jobs need rebuilding, and monitoring needs repointing. This r/sysadmin post from a team that moved more than 15,000 VMs, landing on a mix of OpenShift and Hyper-V, puts the timeline at about 23 months.

A 20-VM shop won't need two years. It will still need an inventory, a test migration of the ugliest VM first, and a backup plan confirmed on the new platform before the old hosts are switched off.

Where VMware still wins is scale and ecosystem depth: large clusters, mature third-party integrations, and teams that already know it well. Where Hyper-V wins is cost for Windows-heavy estates and fewer moving parts to license.

Managing Hyper-V Day to Day

Hyper-V Manager handles single hosts and small labs. It's fine for creating VMs, editing settings and managing checkpoints.

For servers, Windows Admin Center is the better daily console. It runs in a browser, manages hosts and clusters, and Microsoft now offers a Virtualization Mode built specifically for Hyper-V fabric management. Large estates add System Center Virtual Machine Manager for templates, self-service and capacity planning.

PowerShell covers everything the consoles do and more. Get-VM, Checkpoint-VM and Get-VMCheckpoint answer the everyday questions, and PowerShell Direct lets you run commands inside a VM even when its network is broken. OpenFrame can run a check like Get-VMCheckpoint as a script across a client's hosts and collect the output in one place, which is a quick way to find checkpoints someone forgot to delete.

The Short Version

Hyper-V is a type-1 hypervisor that comes with Windows Server and Windows 11 Pro. Enable it with one command, pick Generation 2 VMs, choose the virtual switch type on purpose, and treat checkpoints as a rollback tool, not a backup. The licence you need to count is Windows Server's, not Hyper-V's.

For small Windows-first environments, it's the natural home for a handful of servers, and after Broadcom it's a serious VMware alternative. Next, read our what is virtualization guide for the bigger picture, or the Windows Admin Center guide for the console you'll manage it from.