Hyper-V carries no separate hypervisor license because it ships inside Windows Server, where the Datacenter edition, licensed per core with a 16-core-per-processor minimum, permits unlimited Windows virtual machines, while VMware by Broadcom now charges a per-core subscription on top of the operating system that commonly runs 3x to 10x the prior VMware cost. For organizations already licensing Windows Server, that difference can make Hyper-V effectively free at the hypervisor layer against a seven-figure VMware subscription. This comparison sets out how each is licensed, what the real cost gap is, where Hyper-V falls short of VMware on capability, and which platform fits which estate in 2026.
Inside This Guide
Two approaches to the hypervisor
VMware and Hyper-V represent two commercial philosophies for virtualization. VMware sells the hypervisor and its surrounding stack as a dedicated product, now a per-core subscription under Broadcom, priced as a thing in its own right. Hyper-V is a feature of Windows Server, included with the operating-system license rather than sold separately, so its cost is folded into a license many organizations already buy. The technical capabilities overlap heavily for mainstream workloads, but the pricing models could hardly be more different: one is a standalone subscription, the other is a bundled feature. The whole cost comparison flows from that distinction.
This difference has become decisive since the Broadcom acquisition, because the standalone VMware subscription is exactly the cost that rose sharply while the bundled Hyper-V cost did not. For organizations facing a 3x to 10x VMware renewal, Hyper-V is one of the main alternatives considered, alongside Proxmox and Nutanix. The full VMware picture is in our VMware by Broadcom licensing guide, and the broader alternatives in our VMware exit strategy guide.
VMware by Broadcom licensing
Under Broadcom, VMware is sold only as a per-core subscription, with perpetual licenses withdrawn. You license every physical core in scope, subject to a 16-core-per-processor minimum, against an edition, principally VMware Cloud Foundation for the full private-cloud stack or vSphere Foundation for compute and management without the full networking and storage layers. The subscription bundles support and recurs annually, with no owned asset at the end of the term. The per-core mechanics are in our VMware per-core licensing guide.
The strength of the VMware model is the maturity and breadth of the platform: vSphere, vSAN, NSX, and the Aria management suite are deeply integrated and feature-rich. The cost of that strength is the per-core subscription, which on a virtualized estate of any size runs into six or seven figures a year and recurs indefinitely. Reducing it means right-sizing the edition and the core count and negotiating hard, which is the work of our VMware by Broadcom negotiation practice.
A practical subtlety is that the free Microsoft Hyper-V Server product, a standalone hypervisor with no graphical Windows environment, was discontinued after the 2019 version, so the modern route to Hyper-V is the role inside Windows Server rather than a separate free download. This matters for the cost comparison because it ties Hyper-V firmly to Windows Server licensing: there is no longer a genuinely free standalone Hyper-V to consider, and the economics rest entirely on whether the Windows Server Datacenter license is already justified by the Windows guests on the host.
Hyper-V licensing
Hyper-V itself has no license fee. It is a role within Windows Server, so the cost question is really a Windows Server licensing question. Windows Server is licensed per physical core, with a 16-core-per-processor minimum and a requirement to license all cores in the server, in two main editions. Standard edition permits two Windows virtual machines per fully licensed host, while Datacenter edition permits unlimited Windows virtual machines on the licensed host, which is the edition that makes Hyper-V economical for dense virtualization. An organization that already runs Windows Server Datacenter for its Windows workloads can run Hyper-V on the same hosts at no additional hypervisor cost.
The nuance is that Windows Server licensing is required for the Windows guests in any case, on VMware or on Hyper-V. The Datacenter edition that unlocks unlimited Windows VMs is therefore a cost many estates already carry, which is what makes Hyper-V effectively free at the hypervisor layer in a Windows-heavy environment. Where the guests are mostly Linux, the calculus changes, because the Windows Server Datacenter cost is then incurred mainly to obtain the hypervisor rather than to license guests you already need. The Microsoft licensing detail sits with our Microsoft practice.
It is also worth noting that the licensing metrics themselves are nearly identical between the two, which removes one variable from the comparison. Both license physical cores, both apply a 16-core-per-processor minimum, and both require all cores in a server to be licensed. The difference is not how the cores are counted but what the count is attached to: a recurring VMware subscription priced as a product, or a Windows Server license that many estates buy regardless. Because the counting is the same, an accurate core inventory serves both costings, which is why building that inventory is the first step whichever direction an organization leans.
Side-by-side matrix
| Factor | VMware by Broadcom | Hyper-V (Windows Server) |
|---|---|---|
| License model | Standalone per-core subscription | Included with Windows Server license |
| Metric | Physical cores, 16-core minimum | Physical cores, 16-core minimum |
| Perpetual option | No | Yes, Windows Server is perpetual |
| Hypervisor cost | Full subscription per core | None beyond Windows Server |
| Best guest mix | Any | Windows-heavy estates |
| Platform breadth | Very high (vSAN, NSX, Aria) | Moderate, with System Center |
| Ecosystem | Largest in virtualization | Strong on Windows and Azure |
Cost comparison
The cost gap is the headline finding, and it is large for Windows-heavy estates. Where an organization already licenses Windows Server Datacenter for its Windows guests, moving those workloads to Hyper-V removes the entire VMware per-core subscription with no new licensing cost, because the hypervisor is already paid for inside Windows Server. The table models the comparison for a representative cluster, showing the VMware subscription against the incremental Hyper-V cost on hosts already running Windows Server Datacenter.
| Scenario | VMware annual cost | Hyper-V incremental cost |
|---|---|---|
| Windows-heavy, Datacenter already licensed | Full per-core subscription | $0 additional hypervisor cost |
| Mixed estate, partial Windows licensing | Full per-core subscription | Cost of Datacenter on remaining hosts |
| Linux-heavy estate | Full per-core subscription | Datacenter cost incurred for hypervisor |
| Cost driver | Edition and core count | Windows Server edition already held |
The Windows estate decides it: Hyper-V is effectively free at the hypervisor layer when you already license Windows Server Datacenter for your Windows guests, because the hypervisor is bundled into a cost you carry anyway. On a Linux-heavy estate the saving shrinks, because the Datacenter license is then bought mainly to obtain the hypervisor. The guest operating-system mix is the single biggest factor in the comparison.
Feature and capability gaps
VMware leads on platform breadth and ecosystem maturity. vSphere with vSAN and NSX delivers integrated software-defined storage and networking, a deep third-party ecosystem, and operational tooling refined over two decades. Hyper-V covers the core virtualization functions, live migration, high availability, and replication, and with System Center and Windows Admin Center it manages large estates, but it does not match the full VMware stack feature for feature, particularly in software-defined networking and the breadth of third-party integrations. For many mainstream server workloads the gap does not matter; for advanced software-defined data center requirements it can.
The honest assessment is that Hyper-V is a capable, production-grade hypervisor that meets the needs of a large share of enterprise workloads, and that VMware remains the more complete platform for the most demanding software-defined environments. The decision therefore turns on whether an estate genuinely uses the advanced VMware capabilities or simply runs virtual machines on them, because the latter group pays a large premium for breadth it does not consume.
Migration considerations
Moving from VMware to Hyper-V is a project, not a switch. Virtual machines must be converted, networking and storage re-implemented on the Hyper-V and Windows Server model, operational tooling and runbooks rebuilt, and staff retrained on a different management stack. Microsoft and third parties provide conversion tooling, and for Windows guests the move is generally straightforward, but the operational re-tooling and skills change are the real work and the real timeline, which typically runs months for a sizable estate. The broader migration framework is in our VMware exit strategy guide.
As with any VMware alternative, the migration analysis has value even if the migration is not executed, because a costed and timelined Hyper-V plan is a credible alternative at the Broadcom renewal. A buyer that can show it is genuinely able to move Windows workloads to Hyper-V negotiates the VMware subscription from a stronger position than one that cannot, which is covered in our Broadcom VMware licensing changes guide.
One operational factor deserves weight alongside the licensing math: the skills and tooling an organization already runs. A team deeply invested in vCenter, vSphere automation, and a VMware-centric operational model carries a real, if soft, switching cost that does not appear on a license quote. Conversely, an organization already managing a large Windows and Azure estate with System Center and Windows Admin Center may find Hyper-V a smaller operational change than its VMware footprint would suggest. The licensing saving is the headline, but the operational fit determines how cleanly that saving is actually realized.
The verdict: which when
Choose Hyper-V when the estate is Windows-heavy and already licenses Windows Server Datacenter, the workloads run virtual machines without depending on the advanced VMware software-defined stack, and cost reduction is a priority. In that case Hyper-V removes the VMware subscription at little or no additional licensing cost, and the capability gap is immaterial for the workloads involved. This describes a large share of mainstream enterprise virtualization.
Stay on or choose VMware when the estate genuinely uses the integrated vSAN and NSX capabilities, depends on the breadth of the VMware ecosystem, or runs a Linux-heavy mix where the Windows Server Datacenter cost would be incurred mainly to obtain the hypervisor. Even then, the right response to the Broadcom increase is to right-size the edition and negotiate hard, using a costed Hyper-V or other exit plan as the alternative rather than accepting the opening quote.
The practical rule: If your guests are mostly Windows and you already pay for Datacenter, Hyper-V is close to free and the VMware premium is hard to justify for plain virtualization. If you genuinely use the full VMware stack or run mostly Linux, VMware may still fit, but hold a costed Hyper-V plan as your negotiating alternative either way.
Action steps
Start with the guest operating-system mix and the current Windows Server licensing, because those decide whether Hyper-V is nearly free or carries real incremental cost. Map which workloads actually use the advanced VMware capabilities versus simply running on them, since that defines how much of the VMware premium is justified. Then cost a Hyper-V migration for the eligible workloads, both as a possible move and as a negotiating alternative for the VMware renewal.
For the full VMware context, start with the VMware by Broadcom licensing guide, the per-core licensing guide, and the exit strategy guide. For engagement help, our VMware by Broadcom practice and negotiation service size and negotiate the position, backed by our software licensing advisory team.