In short
Windows Server 2016 reaches end of life on January 12, 2027, when Microsoft stops shipping free security updates and technical support. Mainstream support already ended back in January 2022. You have three realistic options: pay for Extended Security Updates (roughly $5,614 per server over three years), upgrade the OS in place, or migrate the workload to Windows Server 2025. At Raff we recommend planning the move now: a typical small-business migration takes 2 to 6 weeks end to end, and every EOL wave produces a Q4 rush that makes the last months harder than they need to be.
Windows Server 2016 lifecycle: The exact dates
Windows Server 2016 follows Microsoft's Fixed Lifecycle Policy: five years of mainstream support, five years of extended support, then a paid Extended Security Updates (ESU) window for customers who cannot move in time.
| Milestone | Date | What stops |
|---|---|---|
| Release | October 15, 2016 | |
| Mainstream support ended | January 11, 2022 | New features, design changes, non-security fixes |
| Extended support ends (end of life) | January 12, 2027 | Free security updates, technical support |
| Extended Security Updates end | January 12, 2030 | The paid safety net; after this, nothing |
Both support dates come from the Microsoft Lifecycle page for Windows Server 2016. Microsoft confirmed the ESU program for Server 2016 in a February 25, 2026 announcement, giving stragglers a paid bridge of up to three years.
Put plainly: Windows Server 2016 leaves extended support on January 12, 2027, and even the paid ESU program runs out on January 12, 2030.
What actually happens after January 12, 2027
Your servers keep booting. Nothing turns off. The risk builds quietly instead:
- Every new vulnerability becomes permanent. Windows Server CVEs keep being discovered after a version leaves support; without patches, each one is an open door that never closes. Attackers specifically scan for end-of-life systems because the exploit list only grows.
- Compliance frameworks stop cooperating. PCI DSS, HIPAA, SOC 2, and ISO 27001 audits all expect production systems on a vendor-supported OS. An unsupported domain controller or file server is a finding, not a footnote.
- Cyber insurance gets harder. Renewal questionnaires increasingly ask for OS lifecycle status. Running an unsupported server can raise premiums or void claims after an incident.
- Software support erodes. Backup agents, EDR tools, and line-of-business vendors certify against supported platforms. Expect "upgrade your OS first" answers to support tickets.
One more deadline that surprises people: SQL Server 2016 already left extended support on July 14, 2026 (Microsoft Lifecycle). A 2016-era box running SQL Server 2016 is unsupported at the database layer today, before the OS deadline even lands.
Your three options compared
| Option | 3-year cost per server | Downtime | Makes sense when |
|---|---|---|---|
| Extended Security Updates | ~$5,614 (Standard) plus existing hardware costs | None | A hard blocker (legacy app) prevents any move |
| In-place upgrade | Licence cost, plus upgrade risk | Hours, with a risky rollback | Hardware is healthy and roles are simple |
| Migrate to Server 2025 on a VM | From ~$1,965 all-in (4 vCPU / 8 GB, licence included) | A planned cutover window | Aging hardware, most small-business setups |
Option 1: Pay for Extended Security Updates
ESU delivers security patches only: no bug fixes, no feature updates, no technical support. Microsoft prices ESU as a percentage of the licence cost that roughly doubles each year. For Windows Server 2016 Standard (about $1,069 list), that works out to roughly $802 in year one, $1,604 in year two, and $3,208 in year three: about $5,614 per server across the full window, on top of the hardware you already run.
Two purchasing details catch teams off guard. First, ESU is not automatic: you buy it through Microsoft's volume licensing channels or a Cloud Solution Provider, per server, per year. Second, in the previous ESU programs for Server 2008 and 2012 the coverage was cumulative, meaning a team that joined in year two also paid for the year they skipped. Budget for Server 2016 as if the same rule applies.
ESU buys time, not a future. It is the right call only when a critical dependency genuinely cannot move yet, and even then the money usually funds the migration you were postponing.
Option 2: Upgrade in place
Microsoft documents supported in-place upgrade paths from Server 2016 to newer versions in its Windows Server upgrade overview. An in-place upgrade keeps your hardware and installed roles, which is also its weakness: the 9-year-old disks, the accumulated configuration drift, and the applications nobody dares touch all come along for the ride. Rollback means restoring from backup. If the hardware is due for replacement anyway, upgrading in place solves the software deadline while keeping the hardware risk.
Option 3: Migrate to Windows Server 2025 (what we recommend)
A clean Windows Server 2025 build on current hardware sidesteps both problems: the OS is supported until November 2034, and the underlying compute is no longer your capital expense. On Raff, Windows Server 2025 VMs run on dedicated vCPU with NVMe storage:
| Plan | Compute | With Standard licence ($15/mo SPLA) |
|---|---|---|
| 2 vCPU / 4 GB / 80 GB NVMe | $21.99/mo | $36.99/mo |
| 4 vCPU / 8 GB / 120 GB NVMe | $39.59/mo | $54.59/mo |
| 8 vCPU / 16 GB / 180 GB NVMe | $70.49/mo | $85.49/mo |
Every Windows VM includes a 6-month Windows Server evaluation licence at no extra cost, so you can build and test the destination server before paying for a licence at all. After that it is $15.00/month per instance through Raff's SPLA program, or bring your own licence. Current prices are always on the Windows VM page.
The full technical walkthrough (AD DS promotion, FSMO transfer, Storage Migration Service, SQL Server move, cutover and rollback) is in our Windows Server 2016 to 2025 migration guide. For a lighter planning pass, start with the small-business migration checklist.
The cost math: ESU vs migrating
Three years of Server 2016 ESU costs about $5,614 per server; three years of a Raff 4 vCPU / 8 GB Windows Server 2025 VM costs about $1,965, licence included.
The ESU path also leaves you exactly where you started, but three years closer to the 2030 hard stop and still on the same hardware. The migration path ends with a current OS, supported until 2034, on infrastructure that someone else patches, powers, and replaces.
| ESU route (3 years) | Raff migration route (3 years) | |
|---|---|---|
| Software cost | ~$5,614 ESU | ~$1,965 total (36 x $54.59, compute + licence) |
| Hardware cost | Your existing server, power, and replacement risk | Included |
| End state in 2030 | Unsupported OS, no more ESU available | Windows Server 2025, supported until Nov 2034 |