What Is Hyper-V? Microsoft's Hypervisor Explained
- Level
- Beginner
- Reading time
- 27 min
- Concept
- Microsoft Hyper-V
- Last reviewed
- July 5, 2026
Table of contents
Hyper-V is Microsoft's built-in virtualization technology - the hypervisor that lets a single physical server run many isolated virtual machines, each with its own operating system. It's a Type 1, bare-metal hypervisor, which means it runs directly on the hardware rather than as an app inside Windows, even though it's tightly integrated with Windows. This explainer covers what Hyper-V is, how its architecture actually works, what it's used for, how it's licensed in 2026 now that the free standalone edition is gone, and how it stacks up against VMware after Broadcom's licensing overhaul.
Key takeaways
- Hyper-V is a Type 1 (bare-metal) hypervisor: it runs beneath Windows, and Windows becomes the privileged parent partition.
- Its architecture centers on a thin hypervisor, a parent partition (drivers + management stack), child partitions (VMs), and the VMBus/VSP-VSC channel.
- It ships as a role in Windows Server (Standard/Datacenter) and on Windows client (Pro/Enterprise/Education) - no separate hypervisor purchase.
- The free standalone 'Microsoft Hyper-V Server' is discontinued (2019 was the last version); Hyper-V now comes inside a licensed Windows install.
- Common uses: server consolidation, dev/test, disaster recovery (Hyper-V Replica), legacy app support, and hybrid cloud via Azure Local.
Quick explanation
In simple terms
Hyper-V is Microsoft's technology for running several virtual computers (virtual machines) on one physical computer, keeping each one isolated with its own operating system and apps.
Technical definition
Hyper-V is a native, microkernelized Type 1 hypervisor for x64 Windows. It enforces isolation via partitions: a privileged parent/root partition hosts the virtualization stack and device drivers, while child partitions run guests that access hardware through synthetic devices over the VMBus, mediated by Virtualization Service Providers in the parent partition.
Analogy
Think of Hyper-V as an apartment-building manager. It allocates space and utilities (CPU, memory, storage, network) to each tenant (VM) and keeps them isolated from one another, so each tenant lives as if they had their own place - unaware they're sharing one building (the physical host).
Definition
Hyper-V is Microsoft's native Type 1 (bare-metal) hypervisor that creates and runs virtual machines on x64 Windows systems. It sits as a thin virtualization layer beneath the operating system, allowing multiple isolated guest operating systems to share one physical machine's CPU, memory, storage, and network.
Hyper-V is Microsoft's hardware virtualization technology for x64 versions of Windows. It is a Type 1 (bare-metal) hypervisor: when Hyper-V is enabled, a thin hypervisor takes control of the physical hardware and the Windows installation you were running becomes the privileged *parent partition* on top of it. From there, Hyper-V creates and runs *child partitions*, each hosting an isolated guest operating system - Windows, Linux, or other supported systems - that behaves as if it had its own dedicated computer.
Microsoft describes Hyper-V as the processor-specific virtualization platform that lets multiple isolated operating systems share a single hardware platform, with isolation enforced through partitions.
Hyper-V ships in two forms today:
- The Hyper-V role in Windows Server (Standard and Datacenter editions), enabled through Server Manager or PowerShell.
- Hyper-V on Windows client (Windows 10/11 Pro, Enterprise, and Education, 64-bit), enabled as an optional Windows feature.
One important change: the free, standalone *Microsoft Hyper-V Server* product has been discontinued. Hyper-V Server 2019 was the final release, and there is no Hyper-V Server 2022 or 2025. The hypervisor itself is very much alive - it underpins Azure, Windows, Xbox, and Microsoft's on-premises platform Azure Local (formerly Azure Stack HCI) - but it is now consumed as a role inside a licensed Windows installation rather than as a free standalone download.
Why it matters
Core concepts
Type 1 (bare-metal) hypervisor
Hyper-V is a Type 1 hypervisor: it runs directly on the physical hardware rather than as an application inside a host OS.
Despite being built into Windows, Hyper-V is not a Type 2 hypervisor. When you enable it, the hypervisor loads beneath Windows at boot and takes control of the hardware; the Windows OS you were running is then hoisted up to become the privileged parent partition running on top of the hypervisor. This is different from a Type 2 hypervisor like VirtualBox or VMware Workstation, which runs as an ordinary program on top of a full host OS.
The practical effect is near-native performance and strong isolation, because VMs aren't layered on top of a full general-purpose OS - they sit alongside the parent partition, all managed by the thin hypervisor underneath.
Example
After enabling Hyper-V on Windows Server, the boot process loads the hypervisor first; the original Windows install continues to run, but now as the parent partition above the hypervisor.
Why it matters — It explains Hyper-V's performance and isolation characteristics, and clears up the most common misconception about it.
Parent and child partitions
Hyper-V enforces isolation through partitions: one privileged parent (root) partition and one or more child partitions that host guest operating systems.
A partition is Hyper-V's unit of isolation. There is always at least one parent (root) partition running a supported version of Windows; it hosts the virtualization management stack and has direct access to hardware devices. The parent partition then creates child partitions - via the hypercall API - that host the guest operating systems.
Child partitions do not have direct access to the physical processor, memory, or devices. They get a virtual view of the hardware and reach real resources indirectly, keeping VMs isolated from each other and from the host.
Example
You run Windows Server as the parent partition and spin up three child partitions: two Windows VMs and one Linux VM, each isolated from the others.
Why it matters — The partition model is the foundation of Hyper-V's isolation and security guarantees.
VMBus, VSP, and VSC
The VMBus is a high-speed inter-partition communication channel; Virtualization Service Providers (VSPs) in the parent partition serve device requests from Virtualization Service Consumers (VSCs) in child partitions.
Because child partitions can't touch hardware directly, Hyper-V uses a synthetic device model. The VMBus is a logical channel connecting the parent and child partitions. In the parent partition, VSPs handle device access requests; in each child partition, matching VSCs redirect the guest's device requests over the VMBus to the VSPs, which reach the real hardware.
This "enlightened I/O" path - available to guests that are Hyper-V-aware, via Integration Services - bypasses slow device emulation and is what gives Hyper-V VMs efficient storage, networking, and other I/O.
Example
A Linux guest with integration components sends a disk request through its storage VSC, over the VMBus, to the storage VSP in the parent partition, which performs the actual I/O.
Why it matters — It's why Hyper-V VMs perform well; without enlightened I/O and Integration Services, guests fall back to slower emulated devices.
Hardware requirements: virtualization + SLAT
Hyper-V requires a 64-bit CPU with hardware-assisted virtualization (Intel VT-x / AMD-V) and Second Level Address Translation (SLAT).
Hyper-V relies on CPU virtualization extensions and on SLAT - Intel calls it EPT, AMD calls it RVI/NPT - to accelerate memory address translation between guest and physical memory. Microsoft states SLAT is required for Hyper-V on Windows Server 2016 and later. Virtualization must also be enabled in the system firmware (BIOS/UEFI), and the host needs enough RAM to serve the parent partition plus its VMs.
Example
A modern 64-bit server with VT-x/EPT enabled in UEFI and adequate RAM can host Hyper-V; an old CPU without SLAT cannot.
Why it matters — These prerequisites determine whether a given machine can run Hyper-V at all - a frequent gotcha when enabling the role.
Dynamic Memory, Live Migration, and Replica
Hyper-V includes enterprise features such as Dynamic Memory (demand-based RAM allocation), Live Migration (moving running VMs between hosts), and Hyper-V Replica (asynchronous VM replication).
Beyond basic virtualization, Hyper-V offers features that support production workloads: Dynamic Memory adjusts a VM's memory allocation based on demand; Live Migration moves a running VM from one host to another with no downtime (typically using shared storage or clustering); and Hyper-V Replica asynchronously replicates VMs to a secondary site for disaster recovery. Combined with Failover Clustering, these enable high availability.
Example
During host maintenance, an admin uses Live Migration to move running VMs to another clustered host so services stay up.
Why it matters — These are the capabilities that make Hyper-V viable for production, HA, and DR - not just lab virtualization.
How it works
The hypervisor loads beneath the OS
When Hyper-V is enabled, a thin hypervisor loads at boot and takes control of the physical hardware, arbitrating access to CPU and memory for all partitions.
Hypervisor
Example — On boot, the loader starts the hypervisor image before the full Windows environment comes up.
The Windows install becomes the parent partition
The existing Windows OS is hoisted onto the hypervisor as the privileged parent (root) partition, which runs the virtualization management stack and holds the device drivers with direct hardware access.
Parent partition
Example — Windows Server continues to run, but now as the management partition on top of the hypervisor.
Child partitions are created for VMs
The parent partition uses the hypercall API to create child partitions, each hosting a guest operating system in isolation, with only a virtual view of the hardware.
Child partitions
Example — Creating a new VM in Hyper-V Manager provisions a fresh child partition.
Resources are allocated and abstracted
The hypervisor schedules virtual CPUs and allocates memory; Hyper-V presents virtualized hardware (virtual CPUs, NICs, storage controllers) to each guest, which interacts with it as if it were physical.
Resource allocation
Example — A VM configured with 4 vCPUs and 8 GB RAM is scheduled onto physical cores and memory by the hypervisor.
Guests reach hardware over the VMBus
Device I/O from child partitions flows through synthetic drivers (VSCs) over the VMBus to the VSPs in the parent partition, which perform the real hardware access - the efficient 'enlightened I/O' path.
VMBus I/O
Example — A guest's network traffic travels via its network VSC over the VMBus to the network VSP in the parent partition.
Integration Services optimize the guest
Integration Services (drivers and services) installed in the guest enable enlightened I/O and features like time sync and Dynamic Memory, improving performance and host-guest coordination.
Integration Services
Example — A Linux guest with integration components uses synthetic devices instead of slower emulated ones.
Use cases
Server consolidation
IT admins, SMEs, MSPsCombine multiple underutilized physical servers into VMs on fewer hosts, cutting hardware, power, and datacenter footprint while keeping workloads isolated.
Consolidating separate mail, file, web, and database servers onto one or two well-specified Hyper-V hosts.
Benefit — Lower hardware and operating costs with maintained isolation.
Development and testing environments
Developers, QA, ITSpin up isolated VMs that mirror production, with different OSes or configurations, without dedicated hardware.
A developer creates a throwaway VM to test an app against a specific Windows Server build, then discards it.
Benefit — Fast, safe, reproducible test environments.
Disaster recovery and business continuity
IT operations, business continuity ownersReplicate VMs to a secondary site with Hyper-V Replica and use clustering for high availability, minimizing downtime and data loss.
Hyper-V Replica asynchronously copies critical VMs to a DR site that can be brought online if the primary fails.
Benefit — Resilience and quick recovery from site failures.
Legacy application support
IT admins, business ownersKeep applications that require older operating systems running in isolated VMs on modern hardware.
Running a line-of-business app that needs a legacy Windows version inside a Hyper-V VM instead of on aging physical hardware.
Benefit — Preserves critical functionality without risky migration.
Hybrid cloud with Azure Local
Architects, MSPs, enterprisesUse Hyper-V as the virtualization foundation for on-premises workloads that integrate with Azure, including Microsoft's Azure Local hyper-converged platform.
Running VMs on Azure Local on-prem while connecting to Azure services for management and hybrid scenarios.
Benefit — Consistent virtualization across on-prem and cloud.
Benefits
Included with Windows licensing
The Hyper-V role is included at no extra charge with a licensed Windows Server (Standard/Datacenter) or Windows client (Pro/Enterprise/Education) - there's no separate hypervisor purchase.
An organization already licensed for Windows Server can enable Hyper-V without buying additional virtualization software.
Deep Microsoft ecosystem integration
Hyper-V integrates natively with Active Directory, Windows Admin Center, System Center, Failover Clustering, and Azure/Azure Local.
Managing hosts and VMs through familiar Windows tooling and PowerShell.
Strong isolation and security features
The partition model provides strong VM isolation, and Hyper-V underpins security features such as Shielded VMs and virtualization-based security (VBS/HVCI).
Shielded VMs help protect VM data and state from a compromised host fabric.
Production-grade features
Dynamic Memory, Live Migration, Hyper-V Replica, and clustering support high availability and disaster recovery.
Live-migrating running VMs during maintenance with no downtime.
Broad guest support including Linux
Hyper-V supports Windows and many Linux distributions with integration services for optimized performance.
Running supported Linux guests with synthetic devices over the VMBus.
Limitations
Windows dependency and parent-partition overhead
MediumHyper-V requires a Windows host, and the parent partition is a full Windows OS that consumes resources and needs its own patching and maintenance.
Workaround — Use a Server Core installation to reduce the parent partition's footprint and patch surface.
No more free standalone edition
MediumThe free, standalone 'Microsoft Hyper-V Server' is discontinued; 2019 was the last version. There's no no-cost, no-Windows-license way to run Hyper-V going forward - you run it inside a licensed Windows install.
Workaround — Use the Hyper-V role in a licensed Windows Server/client, or evaluate Azure Local (or non-Microsoft hypervisors) if a free standalone host is essential.
Guest OS and Windows Server licensing still applies
MediumEven though the hypervisor is included, you still license the Windows Server host (per-core, Standard vs Datacenter) and any Windows guest OSes, which affects total cost at scale.
Workaround — Model licensing early: Datacenter grants unlimited Windows Server VMs and is often cheaper than Standard at high VM density.
Smaller third-party ecosystem than VMware
LowSome enterprise virtualization and backup tools have historically offered deeper or earlier support for VMware than for Hyper-V, though Hyper-V support is broad and mature.
Workaround — Verify that your backup, monitoring, and management tools fully support Hyper-V before standardizing on it.
Management learning curve
LowGetting the most from Hyper-V at scale involves Windows Server administration, PowerShell, clustering, and sometimes SCVMM.
Workaround — Standardize on Windows Admin Center and PowerShell, and invest in clustering/SCVMM skills for larger fleets.
Architecture
Hyper-V uses a microkernelized architecture: a small hypervisor sits directly on the hardware and handles CPU/memory partitioning, while device drivers and the management stack live in the parent (root) partition rather than in the hypervisor itself. Child partitions host guests that reach hardware indirectly through the VMBus and Virtualization Service Providers. Keeping drivers out of the hypervisor keeps it small and reduces its attack surface.
Windows hypervisor
The thin, processor-specific layer that runs directly on hardware, creates partitions, and arbitrates access to CPU and memory.
Loads at boot (e.g. hvix64 on Intel, hvax64 on AMD) beneath the OS.
Parent (root) partition
Privileged partition running a supported Windows OS; hosts the virtualization stack and device drivers with direct hardware access.
Windows Server with the Hyper-V role, running vmms.exe and VM worker processes.
Child partitions
Isolated partitions that host guest operating systems with only a virtual view of hardware.
A Windows VM and a Linux VM, each in its own child partition.
VMBus
Logical high-speed inter-partition communication channel connecting parent and child partitions.
Carries synthetic device I/O between VSCs and VSPs.
VSP / VSC
Virtualization Service Providers (parent) serve device requests from Virtualization Service Consumers (child) over the VMBus.
Storage, network, video, and HID providers in the parent partition.
Integration Services
Guest-side drivers and services enabling enlightened I/O and features like time sync and Dynamic Memory.
Integration components installed in Windows and Linux guests.
VMMS (vmms.exe)
The Virtual Machine Management Service that controls VM lifecycle and exposes WMI management APIs.
Handles start/stop, snapshots, and configuration of VMs.
Data flow
The hypervisor partitions CPU and memory and schedules virtual processors. A guest in a child partition issues a device request; its VSC forwards the request over the VMBus to the corresponding VSP in the parent partition, which performs the actual hardware I/O and returns the result over the VMBus. SLAT (EPT/RVI) accelerates guest-to-physical memory translation. Management flows through VMMS and its WMI APIs, driven by Hyper-V Manager, Windows Admin Center, PowerShell, or SCVMM.
Integrations: Failover Clustering for high availability and Live Migration, System Center Virtual Machine Manager (SCVMM) for fleet management, Windows Admin Center and PowerShell for management, Azure Local (Azure Stack HCI) and Azure for hybrid scenarios
Architecture limitations
Examples
Consolidating an SME's aging servers
A small business runs four aging physical servers, each barely utilized, and faces a hardware refresh.
Instead of replacing all four, it buys one well-specified server, enables the Hyper-V role on Windows Server, and migrates each workload into its own VM - keeping the services isolated while cutting hardware, power, and maintenance.
Disaster recovery with Hyper-V Replica
An organization needs a DR plan for its critical VMs without building a full second datacenter.
It configures Hyper-V Replica to asynchronously replicate the critical VMs to a secondary site. If the primary site fails, the replicated VMs can be failed over and brought online.
Evaluating Hyper-V during a VMware migration
Facing higher VMware subscription costs after Broadcom's changes, a team evaluates moving to Hyper-V.
Because they already license Windows Server, the Hyper-V role adds no separate hypervisor cost. They lab-test VM import, networking, backup-tool support, and clustering before committing, and consider Azure Local for hybrid needs.
Comparisons
Hyper-V vs VMware vSphere/ESXi vs VMware vSphere (ESXi)
Both are Type 1 hypervisors, but they differ in host model, management, ecosystem, and - significantly since Broadcom's acquisition - licensing. Hyper-V runs with a Windows parent partition and is included with Windows licensing; vSphere runs on the purpose-built ESXi host and is now sold only as subscription bundles.
| Criterion | Hyper-V vs VMware vSphere/ESXi | VMware vSphere (ESXi) |
|---|---|---|
| Host model | Hypervisor beneath Windows; Windows Server/client acts as the parent partition | ESXi is a dedicated, purpose-built bare-metal hypervisor OS |
| Licensing (2026) | Hyper-V role included with a licensed Windows Server (Standard/Datacenter) or Windows client; no free standalone SKU | Perpetual licensing eliminated by Broadcom; subscription-only, per-core bundles (vSphere Foundation / VMware Cloud Foundation) |
| Management | Hyper-V Manager, Windows Admin Center, PowerShell, SCVMM | vCenter Server and vSphere Client |
| Live migration | Live Migration (typically with shared storage/clustering) | vMotion |
| Ecosystem / cloud | Native Azure and Azure Local integration | Large third-party ecosystem; VMware Cloud on AWS and other cloud options |
When to choose — Hyper-V is the natural fit for Microsoft-centric organizations and those already licensed for Windows Server; vSphere remains a proven, feature-rich platform, though Broadcom's subscription-only model has prompted many smaller organizations to re-evaluate. The right choice depends on existing investment, budget, and feature needs.
Hyper-V vs Type 2 hypervisors vs Type 2 hypervisors (VirtualBox, VMware Workstation)
Hyper-V is a Type 1 hypervisor that runs beneath the OS, while Type 2 hypervisors run as applications on top of a full host OS. This affects performance, isolation, and use case.
| Criterion | Hyper-V vs Type 2 hypervisors | Type 2 hypervisors (VirtualBox, VMware Workstation) |
|---|---|---|
| Where it runs | Directly on hardware (Type 1); the OS becomes a partition | As an app on top of a full host OS (Type 2) |
| Typical use | Server and production virtualization, plus client dev/test | Desktop-centric, casual, and cross-platform VM use |
| Performance/isolation | Near-native performance, strong isolation | Extra overhead from the host OS layer; simpler to run ad hoc |
When to choose — Use Hyper-V for server workloads and integrated Windows dev/test; a Type 2 hypervisor is often simpler for quick, cross-platform desktop VMs. Note that enabling Hyper-V can conflict with some Type 2 hypervisors' own virtualization on the same machine.
Myths, corrected
Myth
Hyper-V is a Type 2 hypervisor because it runs on Windows.
Correction
Hyper-V is a Type 1 (bare-metal) hypervisor. When enabled, the hypervisor runs beneath Windows and the OS becomes the privileged parent partition on top of it - it is not an application running inside Windows.
Why it happens: Hyper-V is tightly integrated with Windows and enabled as a 'Windows feature', which makes it look like it runs on top of Windows rather than beneath it.
Myth
There's still a free standalone Hyper-V Server you can download and deploy.
Correction
The free standalone 'Microsoft Hyper-V Server' was discontinued; 2019 was the final version and there is no 2022 or 2025 release. You now run Hyper-V as a role inside a licensed Windows Server or Windows client.
Why it happens: Older guides and long institutional memory still reference the free standalone SKU, which was popular for years.
Myth
Hyper-V is being discontinued / is dead.
Correction
Only the free standalone product was discontinued. Hyper-V the technology is actively developed and underpins Azure, Windows, Xbox, and Microsoft's Azure Local platform.
Why it happens: News about the standalone SKU's end was widely misread as the end of Hyper-V itself.
Myth
Enabling Hyper-V is 'free virtualization' with no other costs.
Correction
The hypervisor role costs nothing extra, but you still license the Windows Server host (per-core, Standard vs Datacenter) and any Windows guest OSes, which drives total cost at scale.
Why it happens: The 'included with Windows' framing gets oversimplified into 'completely free'.
Practical implications
For admins
Enabling Hyper-V requires a 64-bit CPU with virtualization + SLAT and virtualization turned on in firmware. Plan resource allocation to avoid overcommit, keep Integration Services current in guests, and treat the host like any critical server: patch, back up, and monitor it. A Server Core host reduces overhead and patch surface.
For MSPs
For MSPs, Hyper-V is often the most cost-effective virtualization for Microsoft-centric SME clients because the role is included with Windows Server they already license. Be clear with clients that the free standalone edition is gone, that guest and host licensing still apply, and that Azure Local is the path for hybrid. Confirm backup/RMM tooling fully supports Hyper-V.
For business
The headline appeal is no separate hypervisor cost when you already run Windows Server, plus consolidation savings. But total cost must include Windows Server licensing (Datacenter can be cheaper at high VM density) and guest OS licensing - model these before deciding.
For security
Hyper-V provides strong VM isolation and underpins security features like Shielded VMs and VBS/HVCI. The trade-off is that host (parent-partition) hardening and patching are essential, since a compromised host fabric is a serious risk.
For end users
End users mostly encounter Hyper-V indirectly. On Windows client (Pro/Enterprise/Education) it powers dev/test VMs, and Hyper-V technology also underlies features like WSL2 and Windows Sandbox.
Cost impact
No separate hypervisor license: the Hyper-V role is included with a licensed Windows Server or Windows client. However, there is no free standalone edition anymore, and you still pay for the Windows Server license (per-core) and Windows guest licensing. Datacenter edition allows unlimited Windows Server VMs and is often more economical at high density.
Operational impact
Running Hyper-V means operating a Windows host and its VMs: patching the parent partition, maintaining Integration Services, backing up VMs, and - for HA/DR - managing clustering and replication. Management at scale typically adds Windows Admin Center or SCVMM.
Decision guide
Use when
- You run a Microsoft-centric environment and already license Windows Server
- You need server consolidation, dev/test, DR (Hyper-V Replica), or legacy app hosting on Windows
- You want an Azure-integrated hybrid path (Azure Local) or are migrating off VMware
Avoid when
- You need a bare-metal hypervisor with no Windows dependency (consider ESXi, Proxmox VE, or KVM)
- You specifically needed the discontinued free standalone Hyper-V Server model
- Your critical tooling has materially better support on another hypervisor
Requirements
- 64-bit CPU with hardware virtualization (Intel VT-x / AMD-V) and SLAT (EPT/RVI)
- Virtualization enabled in BIOS/UEFI firmware
- Sufficient RAM for the parent partition plus VMs (Microsoft lists ~4 GB minimum for the role)
- Windows Server (Standard/Datacenter) or Windows client Pro/Enterprise/Education, 64-bit
Alternatives
- VMware vSphere / ESXi
- Proxmox VE
- KVM / Nutanix AHV / XCP-ng
- Azure Local (Microsoft's hybrid HCI platform)
Related terms
Hypervisor
Software layer that creates and runs virtual machines by abstracting physical hardware.
Type 1 vs Type 2 hypervisor
Type 1 runs directly on hardware (like Hyper-V, ESXi); Type 2 runs as an app on a host OS (like VirtualBox, Workstation).
Parent (root) partition
The privileged partition running Windows that hosts Hyper-V's management stack and device drivers.
Child partition
An isolated partition hosting a guest OS with only a virtual view of hardware.
VMBus
Logical high-speed channel for communication between parent and child partitions.
VSP / VSC
Virtualization Service Provider (parent) and Consumer (child) that handle synthetic device I/O over the VMBus.
Integration Services
Guest-side drivers/services enabling enlightened I/O and features like time sync and Dynamic Memory.
SLAT
Second Level Address Translation (Intel EPT / AMD RVI), a CPU feature Hyper-V requires to accelerate memory translation.
Live Migration
Moving a running VM between Hyper-V hosts with no downtime.
Hyper-V Replica
Asynchronous replication of VMs to a secondary site for disaster recovery.
Azure Local
Microsoft's Hyper-V-based hyper-converged infrastructure platform for hybrid cloud, formerly Azure Stack HCI.
Frequently asked questions
What is Hyper-V in simple terms?
Hyper-V is Microsoft's virtualization technology that lets you run several virtual computers (virtual machines) on one physical computer. Each VM runs its own operating system and applications in isolation, unaware it's sharing the underlying hardware.
Is Hyper-V a Type 1 or Type 2 hypervisor?
Hyper-V is a Type 1 (bare-metal) hypervisor. Even though it's enabled from within Windows, the hypervisor runs directly on the hardware beneath the OS, and Windows becomes the privileged parent partition on top of it - not an app running inside Windows.
Is Hyper-V free?
The Hyper-V role is included at no extra cost with a licensed Windows Server (Standard/Datacenter) or Windows client (Pro/Enterprise/Education) - you don't buy the hypervisor separately. However, the free standalone 'Microsoft Hyper-V Server' product was discontinued after the 2019 version, so there's no longer a no-cost, no-Windows-license way to run it. You still license the Windows Server host and any Windows guest OSes.
Is Hyper-V being discontinued?
No. Only the free standalone 'Microsoft Hyper-V Server' product was discontinued (2019 was the last version). Hyper-V the technology is actively developed and underpins Azure, Windows, Xbox, and Microsoft's Azure Local platform. It remains available as a role in Windows Server and Windows client.
How does Hyper-V work?
When enabled, a thin hypervisor loads beneath the OS and takes control of the hardware; the Windows install becomes the parent partition, which hosts drivers and the management stack. New VMs run in isolated child partitions that reach hardware indirectly through the VMBus and Virtualization Service Providers, using synthetic (enlightened) I/O for performance.
Is Hyper-V the same as VMware?
No, they're competing platforms. Both are Type 1 hypervisors, but Hyper-V runs with a Windows parent partition and is included with Windows licensing, while VMware vSphere runs on the purpose-built ESXi host and - since Broadcom's acquisition - is sold only as per-core subscription bundles. They differ in management tooling, ecosystem, and cloud integration.
What are the system requirements for Hyper-V?
Hyper-V needs a 64-bit processor with hardware-assisted virtualization (Intel VT-x or AMD-V) and Second Level Address Translation (SLAT), virtualization enabled in BIOS/UEFI, and sufficient RAM (Microsoft lists around 4 GB minimum for the role). It requires Windows Server or Windows 10/11 Pro, Enterprise, or Education (64-bit).
How do I enable Hyper-V on Windows?
On Windows 10/11 Pro, Enterprise, or Education, open 'Turn Windows features on or off' and enable Hyper-V, then restart. On Windows Server, add the Hyper-V role via Server Manager, or run Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart in PowerShell. The machine must support hardware virtualization and SLAT, enabled in firmware.
Conclusion
Hyper-V is Microsoft's native Type 1 hypervisor. It runs beneath Windows - which becomes the parent partition - and hosts isolated VMs in child partitions that reach hardware over the VMBus. It ships as a role in Windows Server and on Windows client, with production features like Dynamic Memory, Live Migration, and Hyper-V Replica.
Main takeaway
Explore a hands-on tutorial for installing and configuring the Hyper-V role, or a comparison of hypervisors (Hyper-V vs VMware vs Proxmox) to inform a platform decision.
-640x640.webp&w=3840&q=75)