Windows Server 2016 End of Support: Jan 2027 Upgrade Guide

On January 12, 2027, Microsoft ends extended support for Windows Server 2016. No more security updates, no more patches, no more support cases — for an operating system that still runs a very large installed base of Active Directory domains, file servers, and Hyper-V hosts. If your estate includes Server 2016, the months left before the deadline — fewer than six — are your planning window, because every option except “do nothing” takes lead time — and “do nothing” is the one option that gets more expensive every month after the deadline.

This guide covers what actually happens after end of support, what Extended Security Updates (ESU) really cost, the supported upgrade paths to Windows Server 2019, 2022, and 2025 — and the question most upgrade guides skip: what to do about the hardware. Most Server 2016 deployments live on 2014–2017 machines that are aging out right alongside the OS, and in 2026's market — with new-server lead times stretching past 30 weeks and list prices climbing — the refresh math has changed.

Quick answer: if your hardware is from the Server 2016 era, don't in-place upgrade on a ten-year-old box and don't rent time with ESU. Move to Windows Server 2022 or 2025 on a refurbished 14th/15th-gen Dell or HPE Gen10/Gen11 platform — you get a supported OS into the 2030s at 50–70% below the cost of new hardware, shipped in days instead of months. We show the exact platform-to-OS mapping below.

What Actually Happens on January 12, 2027

Windows Server 2016 left mainstream support back in January 2022; since then it has received security fixes only. After January 12, 2027, even those stop. Your servers will keep booting — nothing switches off — but three clocks start ticking:

Security exposure compounds. Newly disclosed vulnerabilities affecting Server 2016 will, outside the ESU program, never receive a Microsoft fix. Attackers actively reverse-engineer patches released for newer Windows Server versions to find the same holes in unsupported ones — end-of-life server operating systems are among the most reliably exploited targets on any network.
Compliance pressure mounts. Frameworks like HIPAA, PCI-DSS, and CMMC do not name minimum OS versions, but they all require managing known vulnerabilities — an unsupported OS in scope means documented compensating controls at minimum, and increasingly hard questions from auditors, assessors, and cyber-insurers.
The software ecosystem moves on. Backup agents, EDR/antivirus, monitoring tools, and line-of-business applications drop Server 2016 from their support matrices — usually faster than Microsoft did.

None of this is hypothetical — it is the same sequence that played out for Server 2008 and Server 2012. The organizations that came out fine were the ones that treated the deadline as a project with a date, not a suggestion.

Your Four Options, Honestly Compared

Every Server 2016 machine in your estate ends up on one of four paths. Here is the honest comparison:

Path	What you get	The catch
Buy Extended Security Updates	Up to 3 more years of security-only patches (to January 2030), enrolled through volume licensing or Azure Arc	Recurring cost — in Microsoft's current published program each ESU year costs the full Windows Server license price over again; no new features, no bug fixes; you still face this same migration in 2030 — on hardware three years older
In-place upgrade on existing hardware	Supported OS with no hardware spend; Server 2025 accepts direct in-place upgrades from Server 2016	Most Server 2016 hosts are 2014–2017 platforms already past their OEM validation window for the newest OS — you modernize the software while keeping ten-year-old fans, PSUs, and drives
New OS on refreshed (refurbished) hardware	Clean install of Server 2022/2025 on a validated 14th/15th-gen platform with warranty; supported runway to 2031–2034; consolidation savings	Requires a migration project (which every path except ESU requires anyway) and new licenses (ditto)
Migrate workloads to Azure	Managed infrastructure and migration tooling; in earlier ESU cycles, Azure-hosted VMs also received ESU at no extra charge	Microsoft's March 2026 pricing-consistency update sets one list price for new ESU offerings in Azure, on-premises, and other clouds — verify before counting on free ESU; and for steady-state workloads, recurring compute charges commonly overtake owned-hardware costs — run the TCO for your workload

For most on-premises estates the practical answer is the third row — and the reason is as much about the hardware market as the OS. We will get to that. First, the two topics that generate the most confusion: ESU pricing and upgrade paths.

The ESU Reality Check: Renting Time Is Expensive

Microsoft announced the Server 2016 ESU program in February 2026. Enrollment runs through classic volume licensing or Azure Arc (with monthly Azure billing), the updates themselves flow through Windows Update/WSUS as usual, and on-premises eligibility requires active Software Assurance or subscription licenses. The structural facts:

Three years maximum — security-only updates through January 2030, then the road genuinely ends.
Pricing follows Microsoft's published ESU model. In the current program (Windows Server 2012/R2), every ESU year costs 100% of the full Windows Server license price — again each year — aligned to how the underlying server is licensed: physical cores (16-core server minimum) or virtual cores per VM (8-core minimum). Enrollment is cumulative: join in year two and you buy year one as well.
Do not assume the old free-in-Azure carve-out. Earlier ESU cycles were free for Azure-hosted VMs, but Microsoft's March 2026 pricing-consistency update sets one list price for new ESU offerings (released April 1, 2026 or later) across Azure, on-premises, and other clouds. Server 2016's program starts in 2027 — confirm current terms with Microsoft or your licensing partner before building a plan around Azure ESU economics.

Run the arithmetic before choosing this path. Three years of ESU add up to roughly three full Windows Server license prices — on a Standard host that alone approaches the cost of a complete refurbished 15th-generation server, and on Datacenter or high-core hosts it exceeds one several times over — and at the end of the ESU term you still have to do the migration, minus the budget you spent renting time. ESU is a bridge for the handful of systems that genuinely cannot move — a legacy app pinned to an old runtime, a regulated system mid-revalidation — not a fleet strategy.

Upgrade Paths: 2019 vs 2022 vs 2025

The mechanics are more flexible than they used to be. Windows Server 2025 broke with the old two-versions-back rule: Microsoft supports direct in-place upgrades to Server 2025 from Server 2012 R2, 2016, 2019, and 2022 using installation media. From Server 2016 you can also take the classic hops to 2019 or 2022. The real question is which target buys you the most supported runway:

Version	Mainstream support ends	Security updates end	Runway from mid-2026
Server 2016	Ended Jan 2022	Jan 12, 2027	Under 6 months
Server 2019	Ended Jan 2024	Jan 9, 2029	~2.5 years — too short to migrate to
Server 2022	Oct 13, 2026	Oct 14, 2031	~5 years — the value target
Server 2025	Nov 13, 2029	Nov 14, 2034	~8 years — the long-runway target

Practical read: skip Server 2019 as a destination — migrating to an OS with about 2.5 years of life left just schedules the next migration. (One deliberate exception: Server 2019 is the newest Windows Server that supports SQL Server 2016, so it can serve as a short compatibility bridge — see the warning below.) The real choice is Server 2022 (mature, validated across OEM matrices, supported by essentially every third-party vendor — verify your critical agents regardless — five years of patches left) versus Server 2025 (eight years of runway, hotpatching — now free for Azure Arc-connected Standard/Datacenter servers, though quarterly baseline reboots remain — and the current platform). Licensing is per-core on both — 8-core minimum per processor, 16 per server, plus CALs that must match the new server version. Budget licenses into the project either way, because every path except ESU requires them.

SQL Server warning: SQL Server 2016 is not supported on Windows Server 2022 or 2025 — Microsoft's support matrix caps it (with SP3) at Windows Server 2019. And SQL 2016 itself left extended support on July 14, 2026. If a Server 2016 box also runs SQL Server 2016, an in-place OS upgrade alone would leave an unsupported production stack — plan the database upgrade or a side-by-side move to a supported SQL version as part of the same project.

Active Directory & cluster note: even though in-place upgrading a domain controller is technically supported, the cleaner pattern — and the one we see cause the fewest 2 a.m. incidents — is to stand up fresh DCs on the new OS, replicate, transfer FSMO roles, and demote the old ones. A hardware refresh makes this the natural workflow rather than an extra step. The same conservatism applies to failover clusters and Storage Spaces Direct: rolling cluster upgrades move one OS version at a time, so a 2016 cluster is usually better replaced side-by-side with a new cluster than upgraded node-by-node in place.

The Part Upgrade Guides Skip: Your Hardware Is Also End-of-Life

Windows Server 2016 shipped in October 2016 — but the OS version does not tell you how old the metal underneath is, so scope this correctly first. If your 2016 instances are guest VMs on newer, supported hosts, this section is about the hosts, not the guests: upgrade the VMs and move on. The estates that need attention are the physical installs and hypervisor hosts of the same vintage as the OS — Dell PowerEdge 13th-gen (R630/R730), HPE ProLiant Gen9, 2014-era platforms. By January 2027 those boxes will be a decade old: out of OEM support, past the design life of their fans, PSUs, and drives, with DDR4-2133/2400 memory and PCIe Gen3. In-place upgrading the OS on that hardware modernizes the software and keeps every hardware risk exactly where it was.

Technically, Windows Server 2025's CPU requirements (64-bit, POPCNT and SSE4.2 instructions, TPM 2.0 for security features like BitLocker) are met by virtually every Xeon of the last decade — the installer will run on your old fleet. But OEM validation is a different matter, and it maps cleanly onto the refurbished market:

Target OS	Refurbished platforms with OEM validation	Best for
Windows Server 2022 (supported to Oct 2031)	Dell 14th-gen — PowerEdge R640, R740; HPE DL360 Gen10, DL380 Gen10	The value play — lowest cost per node, five years of OS runway, DDR4 memory at refurbished prices
Windows Server 2025 (supported to Nov 2034)	Dell 15th-gen — PowerEdge R650, R750; HPE ProLiant Gen10 and newer per HPE's certification matrix	The long-runway play — OS and hardware lifecycles aligned into the 2030s, PCIe Gen4, 8 memory channels per CPU

Note the asymmetry: Dell's official Windows Server 2025 validation starts at 15th-gen (the R750's supported-OS list runs Server 2016 through 2025), while its excellent 14th-gen platforms are validated through Server 2022 — which is precisely why an R640/R740 running Server 2022 is the best price-per-supported-year deal on the market right now. (A 2025 BIOS release note for the R740/R640 does mention Server 2025, but the models' official supported-OS lists still top out at Server 2022 — treat that as the supported ceiling.) HPE's matrices list Windows Server 2025 support down into the Gen10 family — but support there is configuration-specific, so check the exact model, CPU generation, and System ROM level in HPE's matrix before committing.

And this is where 2026 market conditions do the selling. Reported lead times on newly configured systems from the major OEMs now stretch to 30–40 weeks for some configurations — long enough to overshoot the January 2027 deadline — and vendors have pushed through double-digit price increases driven by the AI memory shortage. A refurbished 14th/15th-gen server costs 50–70% less than its new equivalent, ships from stock in days, and — crucially in this RAM market — comes with its DDR4 memory installed, at a fraction of today's module prices. Every configuration on our refurbished servers pages is burn-in tested and covered by a free 1-year warranty, extendable to 5 years — carrying you deep into the Server 2022 support window.

Consolidation bonus: a single R750 (up to 80 Ice Lake cores, 32 DIMM slots) can often replace two or three Server 2016-era hosts — size it against real utilization numbers, and keep an N+1 node where the workloads need HA. Licensing cuts both ways: fewer chassis can mean fewer licensed cores, but Windows Server Standard covers only two VMs per fully licensed host, so consolidating a VM fleet onto one dense node usually calls for stacked Standard licenses or Datacenter. Our R750 review runs the consolidation math in detail.

The Six-Month Migration Checklist

Working backward from January 12, 2027, here is a realistic sequence for a small-to-mid estate:

1. Inventory (now). Every Server 2016 instance: physical or VM, roles (AD, file, print, Hyper-V, SQL, app), what depends on it, and what hardware it runs on. The forgotten box in a branch office is the one that gets you.
2. Sort by fate. Retire what nobody uses (there is always something), mark the few genuine ESU candidates, target everything else at Server 2022 or 2025 using the runway table above.
3. Verify application support. Check each critical app's support matrix against the target OS before buying anything. This step decides 2022-vs-2025 more often than any Microsoft feature list. While you are in there, flag SQL Server 2016 instances: SQL 2016 left extended support on July 14, 2026, and is not supported on Windows Server 2022/2025 (see the warning above) — those databases move as part of this project, not after it.
4. Order hardware early in the window. If you refresh with refurbished, days-not-months lead times mean this is no longer the critical path — send us the workload list and we will spec and quote configurations the same day. If you insist on new, order essentially immediately: OEM lead times already overlap the deadline.
5. Migrate side-by-side. Fresh OS installs on the new hosts, then move workloads: new DCs replicate and take over FSMO roles; file services move with Storage Migration Service; VMs re-platform onto the new hypervisor hosts. Side-by-side beats in-place because rollback is always available — the old box is still there.
6. Decommission for value. Retired 13th-gen fleets are not e-waste — working Dell and HPE hardware has real resale value. Our IT asset buy-back program quotes fair prices, provides free shipping boxes, performs NIST 800-88 data sanitization, and pays fast — recovered budget that offsets a meaningful slice of the refresh.

Refreshing a Fleet — and Retiring One

PCSP has refurbished enterprise hardware for 17+ years from our Michigan facility. Every server we ship — R640, R740, R650, R750, or ProLiant — is configured to your exact spec, load-tested as a complete system, and dispatched the same business day on orders placed before 1:00 PM EST, with free shipping in the contiguous US. Replacing a whole Server 2016 estate? Ask about multi-unit pricing, and remember the buy-back program works in the same transaction: we quote your outgoing 13G/Gen9 fleet while building its replacement, so one project handles both ends of the refresh.

Frequently Asked Questions

When does Windows Server 2016 support end?

Extended support for Windows Server 2016 ends on January 12, 2027. Mainstream support already ended in January 2022, so the OS has been on security-only updates for years — after January 2027, even those stop unless you purchase Extended Security Updates.

What happens if I keep running Windows Server 2016 after January 2027?

The servers keep working, but vulnerabilities affecting Server 2016 will generally no longer receive Microsoft fixes (outside the ESU program), auditors and cyber-insurers treat the OS as unsupported, and third-party software vendors progressively drop it from their support matrices. The practical risk compounds monthly.

Can I upgrade directly from Windows Server 2016 to Windows Server 2025?

Yes. Windows Server 2025 supports direct in-place upgrades from Server 2012 R2, 2016, 2019, and 2022 using installation media. Verify application compatibility first, and for domain controllers prefer standing up fresh DCs on the new OS and migrating roles rather than upgrading in place.

Can I run SQL Server 2016 on Windows Server 2022 or 2025?

No. Microsoft's support matrix caps SQL Server 2016 (SP3) at Windows Server 2019; on Windows Server 2022 the oldest supported version is SQL Server 2017, and on Windows Server 2025 it is SQL Server 2019. SQL Server 2016 itself left extended support on July 14, 2026 — plan the database upgrade together with the OS migration, not after it.

How much do Windows Server 2016 Extended Security Updates cost?

In Microsoft's current published program (Windows Server 2012/R2), each ESU year costs 100% of the full Windows Server license price — per year, aligned to the server's core licensing — with cumulative enrollment: joining late means buying the earlier years too. ESU runs a maximum of three years (to January 2030), enrolled through volume licensing or Azure Arc. Note that Microsoft's March 2026 pricing-consistency update sets one list price for new ESU offerings across Azure, on-premises, and other clouds — do not assume the free-in-Azure treatment of earlier ESU cycles applies to Server 2016.

Will Windows Server 2025 run on my existing hardware?

Probably — the hard requirements (64-bit CPU with POPCNT and SSE4.2, TPM 2.0 for security features like BitLocker) are met by virtually every Xeon of the past decade. But OEM validation matters for production: Dell validates Server 2025 on 15th-gen and newer PowerEdge, with 14th-gen validated through Server 2022; HPE's certification matrix extends Server 2025 support into the ProLiant Gen10 family. Running a new OS on a decade-old, out-of-support chassis modernizes the software while keeping all the hardware risk.

Which refurbished server should I buy to replace Windows Server 2016 hosts?

For Windows Server 2022 (supported to October 2031), the value picks are the Dell PowerEdge R640/R740 and HPE DL360/DL380 Gen10 — validated platforms at the lowest cost per node. For Windows Server 2025 (supported to November 2034), step up to the Dell R650/R750 for PCIe Gen4, eight memory channels per CPU, and hardware-OS lifecycles that stay aligned into the 2030s.

Do I need new licenses and CALs when I upgrade from Server 2016?

Yes, unless you have Software Assurance. Windows Server 2019/2022/2025 licenses are per-core (minimum 8 cores per processor, 16 per server), and client access licenses must match or exceed the new server version. Consolidating several old hosts onto one higher-core modern server often reduces the total licensing footprint for the same capacity.

Is Windows Server 2022 still a smart upgrade target in 2026, or should I go straight to 2025?

Server 2022 remains a strong target: security updates run to October 2031, third-party support is essentially universal, and it is validated on cheaper 14th-gen refurbished hardware. Choose Server 2025 when you want the longest runway (November 2034), hotpatching, or are buying 15th-gen hardware anyway. Server 2019 is usually the wrong destination — only about 2.5 years of support left — unless you need it as a compatibility bridge, e.g. for SQL Server 2016.

Under Six Months Left — Still Enough, If You Start Now

Windows Server 2016 end of support is the rare IT deadline with a clean answer: move to Server 2022 or 2025 on hardware that will outlive the OS transition, and do it while refurbished 14th/15th-gen platforms are plentiful and new-hardware prices are still climbing. Pick the platform, configure CPUs, memory, and drives in our configurator, and we will build, test, and ship it — usually the same business day. The hardware half of your January 2027 problem can be solved this quarter.

Tell us what your Server 2016 estate runs today, and we will spec replacement configurations — with trade-in values for the outgoing fleet — within one business day.

Shop Refurbished Servers Shop Dell R750 Request a Custom Quote

Free shipping to the contiguous US • Same-day fulfillment on orders before 1:00 PM EST • 1–5 year warranties available