Microsoft has confirmed that Windows Server 2016 reaches the end of extended support on 12 January 2027, after which no edition will receive further security updates. UK organisations still running it in production need to start auditing and budgeting now, before the window to act safely closes.
View the data behind this chart
| Phase | Starts (week) | Duration (weeks) |
|---|---|---|
| Mainstream support | 0 | 156 |
| Extended support | 155 | 1 |
| EOL cliff | 155 | 1 |
A ten-year lifecycle hits its final patch
Windows Server 2016 went to general availability on 12 October 2016, following its unveiling at Microsoft's Ignite conference the previous month. It left mainstream support back in January 2022, and Microsoft has now fixed the end of extended support at 12 January 2027. The January 2027 security update will be the last one issued, Microsoft said, covering the Datacenter, Essentials, MultiPoint Premium and Standard editions alike.
On the same date, Essentials-specific functionality — including Remote Web Access — also stops being supported, which matters for smaller organisations that leaned on those features rather than running a full domain-joined estate.
Why this is a genuine support cliff, not a soft deadline
Once the January 2027 update ships, there is no extension, no paid programme mentioned by Microsoft for this release, and no safety net. Any newly disclosed vulnerability in the base OS after that point goes permanently unpatched on these systems. For regulated UK sectors — finance, healthcare, public sector supply chains — that turns an ageing but functioning server estate into an audit finding and a cyber insurance liability almost overnight.
This is also a hardware problem as much as a software one. Servers bought to run Windows Server 2016 at launch are now roughly a decade old, often out of manufacturer warranty, and more prone to the kind of failure that turns a planned migration into an emergency one. Running a proper server end of life review now, rather than after an incident, is the difference between a managed project and a crisis response.
Check exactly which editions and features you're carrying
Because all four editions lose support on the same date, a blanket assumption that only Datacenter or Standard is at risk can leave gaps. Essentials and MultiPoint Premium deployments — often found in smaller branch offices or education settings — need the same scrutiny, particularly where Remote Web Access is relied on for remote staff.
- •Datacenter and Standard editions: core workloads, virtualisation hosts, domain controllers
- •Essentials: small-business deployments using Remote Web Access and related tools
- •MultiPoint Premium: shared-access or education-style deployments
- •Any embedded or appliance-based systems still shipping with Server 2016 underneath
The supported migration path: Windows Server 2025
Microsoft's advice is unambiguous: move to Windows Server 2025, the current Long-Term Servicing Channel release, which reached Windows Insiders in January 2024 and general availability in November 2024. It carries mainstream support until November 2029 and extended support until 14 November 2034 — a runway of roughly eight years from today, which makes it the obvious landing point rather than an interim stopgap.
Organisations wanting to validate compatibility before committing budget can run a free 180-day trial through the Microsoft Evaluation Center, which is enough time to test core workloads, drivers and third-party software against the new release before signing off a full rollout. Our guide to planning a migrate EOL servers project for UK estates covers the practical sequencing in more detail.
Budgeting the move without blowing the capex cycle
A January 2027 deadline sounds distant until procurement lead times, testing cycles and change-freeze periods are factored in. Many UK buyers will find the realistic working window is closer to twelve months than fifteen. Running the numbers through a Windows Server EOL cost calculator early gives finance teams a defensible figure to plan against, rather than a late scramble for emergency spend.
Not every workload needs new hardware on day one. Where budget cycles don't align with the deadline, refurbished servers can extend compute capacity cost-effectively while migration work proceeds in phases, and a new vs refurbished server calculator helps quantify that trade-off properly. For estates that genuinely cannot migrate everything before January 2027, third-party maintenance can bridge the gap on hardware support, though it does nothing to replace the missing OS-level security patches — it buys time, not immunity.
Building the plan now
The sensible sequence is straightforward: inventory every instance of Windows Server 2016 across the estate, including Essentials and MultiPoint deployments that are easy to overlook; trial Windows Server 2025 against critical workloads; and sequence the migration so the riskiest, most exposed systems move first. Teams juggling broader procurement alongside this migration may also find it worth looping in IT procurement services early, since hardware refresh and licensing decisions often move faster with dedicated support than when handled alongside day-to-day operations.