Hyper-V Server 2016 End of Support: What Ends on January 12, 2027 and Where the Virtual Machines Go
Microsoft Hyper-V Server 2016 leaves extended support on the same day as Windows Server 2016. What that means for the free hypervisor, the hosts running it, and the virtual machines on them.
The free hypervisor loses support on the same day as Windows Server 2016
Microsoft's lifecycle page lists Hyper-V Server 2016 with a start date of October 15, 2016, mainstream support ending January 11, 2022, and extended support ending January 12, 2027 (shown as 1/13/2027 6:59:59 AM Pacific Time). After that date the hypervisor itself stops receiving security updates, whatever the guest operating systems are running. Microsoft's 2027 end-of-support roundup lists Hyper-V Server 2016, Windows Server 2016, Windows Storage Server 2016, and Windows Server Update Services for Windows Server 2016 together on January 12, 2027, so most environments face the host and guest deadlines at once.
Why a host deadline is more urgent than a guest deadline
- A hypervisor flaw exposes every virtual machine on the host, including guests that are fully patched.
- Hyper-V Server is a dedicated hypervisor installation, so an unsupported host cannot be patched around by hardening the guests.
- Backup and replication tools that integrate with the hypervisor may drop support for an unsupported host version on their own schedule.
- Hosts bought with Hyper-V Server 2016 are often near the end of their hardware warranty as well, so the host refresh and the hypervisor change tend to be one project.
What to inventory on each Hyper-V Server 2016 host
- Host model, processor generation, memory, local and shared storage, and warranty or support contract date.
- Every virtual machine: guest operating system and version, role, owner, and whether it is also a Windows Server 2016 guest facing the same deadline.
- Replication and backup: which tool protects the VMs, where replicas go, and when a restore was last tested.
- Clustering: whether hosts form a failover cluster, because cluster OS rolling upgrade moves one version at a time.
- Licensing position: Windows Server Standard or Datacenter licenses on the hosts, and Software Assurance, which affect both the upgrade and any Extended Security Updates.
Where the hypervisor and the virtual machines can go
| Path | When it fits | Depends on |
|---|---|---|
| Windows Server 2025 with the Hyper-V role on the same or new hosts | You want to stay on Microsoft virtualization with the longest runway (extended support to November 14, 2034) | Host hardware supported on 2025 by its manufacturer; Windows Server licensing for the hosts |
| Azure Local or Azure virtual machines | Some workloads suit Azure, or you want Microsoft-managed infrastructure with Arc management | Network connectivity, data location, and workload licensing |
| Another hypervisor platform | The platform decision is open and the backup tooling supports the target | Hardware compatibility, migration tooling, policy rebuild |
| Extended Security Updates on the guests | Only the Windows Server 2016 guests, not the hypervisor: ESUs cover Windows Server 2016 Standard and Datacenter, for up to three years after January 12, 2027 | Does not keep the Hyper-V Server 2016 host supported |
See the Windows Server 2016 Extended Security Updates guide and the VMware renewal or re-platform guide.
Sequencing the move
- Stand up the new host or cluster first, then move virtual machines in waves by owner and change window.
- Test a restore of a moved VM on the new platform before moving production.
- Upgrade or replace the Windows Server 2016 guests as part of the same waves, so the estate is not migrated twice.
- Retire the old hosts only after the last VM has run a full business cycle on the new platform.
See the Windows Server 2016 replacement service and the Infrastructure End-of-Support Assessment.
Plan the host and the guests as one project
Send us your Hyper-V hosts and the virtual machines on them. We will help you choose the target platform, size the new hosts, and sequence the moves before January 12, 2027. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.
Sources
Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.
- Microsoft Lifecycle: Hyper-V Server 2016 (opens in a new tab)
- Microsoft Lifecycle: Products ending support in 2027 (opens in a new tab)
- Microsoft Learn: Windows Server release information (opens in a new tab)
- Microsoft Learn: Prepare to deliver Extended Security Updates through Azure Arc (Windows Server 2016) (opens in a new tab)
- Microsoft Learn: Windows Server upgrade overview (opens in a new tab)
Related services
Related resources
Turn the checklist into a plan
The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.
