There's a deadline quietly approaching that many UK businesses haven't yet clocked: on 12 January 2027, Microsoft ends support for Windows Server 2016.
If you're running it, and a huge number of businesses still are, often without realising it's powering their file server, domain controller or a line-of-business application — your server won't stop working that day. But something arguably more dangerous happens: it stops receiving security updates. It carries on humming away, quietly becoming a bigger risk by the week.
This guide explains what end of support actually means, why it matters more than it may at first appear, and the realistic options for planning your move as we approach this fast-approaching deadline.
What does "end of support" actually mean?
Windows Server 2016 has been on borrowed time for a while. Mainstream support ended back in January 2022, so it's been on security updates only for years. The final milestone - the end of extended support - lands on 12 January 2027.
After that date, unless a server is covered by a paid support programme, Microsoft will no longer:
- Release security updates or patches
- Fix newly discovered vulnerabilities
- Provide technical support if something goes wrong
Crucially, the server keeps running. Nothing switches off. That's exactly what makes this deadline easy to ignore, and exactly why it's risky.
Why an unsupported server is a growing risk
The danger isn't that the server stops working. It's that the world keeps moving, and your server doesn't.
-
Every new vulnerability becomes permanent: Security flaws in Windows Server are discovered all the time. Before the deadline, Microsoft patches them. After it, any vulnerability found in Server 2016 simply stays open - a door that never gets closed. And because different Windows Server versions share large amounts of code, patches released for newer versions effectively act as a map, showing attackers which weaknesses likely exist in unpatched 2016 systems.
-
Attackers actively hunt for end-of-life systems: The lifecycle dates are public. Once a system is known to be out of support, it becomes a deliberate target — the list of ways in only grows, and nobody's fixing them.
-
Compliance and insurance stop cooperating: This is the one that catches businesses out. Many compliance frameworks require supported operating systems. Cyber insurers and larger customers increasingly mandate adherence to the lifecycle in their contracts. Running an unsupported server can quietly put you in breach of a policy or a client agreement — and you might not find out until you try to make a claim or renew a contract.
-
There's no safety net if something breaks: If a domain controller fails or a storage driver misbehaves after the deadline, there's no Microsoft support case to open. You're on your own.
Your options: the four realistic routes
The good news is you have time to plan and several genuine choices. The right one depends entirely on what the server actually does and how much change your environment can tolerate.
1. Upgrade in place: Move to a current version (Windows Server 2022 or 2025) on the same hardware, if it's capable. Cleanest where the hardware is up to it, and applications are compatible.
2. Migrate to new hardware or virtual machines: Move the workload onto modern kit or a fresh virtual environment. A good moment to consolidate and tidy up an ageing setup — though see the cost note below.
3. Move to the cloud: Shift the workload to a cloud platform such as Microsoft Azure. This can eliminate the hardware question entirely and, in some Azure scenarios, also include security update coverage. Often, the most future-proof route for businesses is ready to make the move.
4. Buy Extended Security Updates (ESU) as a bridge: Microsoft has confirmed a paid ESU programme for Server 2016, available for up to three years beyond the deadline. This buys time — but it's a bridge, not a solution. It's a paid stopgap for workloads that genuinely can't move in time, not a way to avoid the decision.
A cost wrinkle worth knowing about in 2026
There's an unusual complication for anyone weighing up a hardware refresh right now: server memory prices have risen sharply through 2026, driven by enormous demand from AI datacentres. That single factor has reshaped the maths behind the "buy new hardware" option, making it considerably more expensive than it would have been a year ago.
It doesn't change the deadline, but it does change the calculation - and for some businesses, it tips the balance toward cloud migration or a well-planned upgrade rather than a like-for-like hardware replacement. It's exactly the kind of thing worth modelling properly before committing budget.
Why now, not later
With fewer than six months to go from mid-2026, the planning window is closing, and every option except "do nothing" takes lead time.
Checking application compatibility, mapping dependencies, sourcing hardware or cloud capacity, migrating data, testing, and cutting over all take time to do properly. Rushed server migrations are exactly where things go wrong — and a server is rarely a standalone box. It often underpins your logins, your files, your email routing or a critical application, so getting it wrong has knock-on effects across the business.
There's often a stacked timeline too. If your environment also includes older Windows Server 2012 or 2012 R2 machines (whose final ESU window closed in October 2026), or SQL Server 2016 (which left support in July 2026), the sequencing of all this matters. It's rarely just one server in isolation.
How to prepare: a simple checklist
- Find out what you're running: Audit your environment for any Windows Server 2016 instances — they're often hiding in plain sight, powering something important.
- Map what each server does: Identify the applications, logins and services that depend on it, so nothing is missed in the move.
- Check application compatibility: Confirm your critical software is supported on the target version before committing to a route. This often decides the path for you.
- Weigh the options against real costs: Upgrade, new hardware, cloud, or ESU bridge - factor in the 2026 hardware price situation.
- Plan the migration properly: Sequence it, test it, and schedule the cutover to minimise disruption.
- Start now. The earlier you begin, the more options stay open — and the cheaper and calmer the whole thing is.
The bottom line
Windows Server 2016 reaching end of life isn't a reason to panic, but it is a firm reason to plan.
The server won't stop working on 12 January 2027 - but the risk simply starts building quietly from that day on, in security, in compliance, and in the growing cost of staying put.
The businesses that handle this well won't be the ones scrambling in late 2026; they'll be the ones who found their 2016 servers early, understood what each one did, and chose their route deliberately.
If you're not sure whether Server 2016 is still lurking somewhere in your setup, that's the first thing worth finding out - and the best time to find out is now.
Not sure what's running on your servers?
If the January 2027 deadline is on your radar - or you're not even sure whether Windows Server 2016 is still in your environment - we can help. At Netitude, we help businesses across Somerset, Bristol, and the Southwest audit their infrastructure and plan upgrades that fit the business, not just the deadline. Get in touch for an honest conversation about your options.
Frequently asked questions
-
When is Windows Server 2016 end of life? Windows Server 2016 reaches the end of extended support on 12 January 2027. After this date, Microsoft no longer provides security updates, patches or technical support for it unless the server is covered by the paid Extended Security Updates programme.
-
Will my server stop working after January 2027? No. The server will keep running exactly as before. What stops is the flow of security updates and support — meaning any new vulnerabilities discovered after the deadline won't be fixed, making the system progressively riskier over time.
-
What are Extended Security Updates (ESU)? ESU is a paid Microsoft programme that provides critical security updates beyond the end-of-support date. Windows Server 2016 is available for up to 3 years as a bridge for businesses that can't migrate in time. It's a stopgap, not a long-term solution.
-
What should I upgrade to? The main routes are upgrading to Windows Server 2022 or 2025, migrating to new hardware or virtual machines, or moving the workload to the cloud (such as Azure). The best choice depends on what the server does, your budget, and your appetite for change.
-
How long does a server migration take? It varies with complexity, but a well-planned migration typically takes several weeks from audit to cutover — most of which is planning and testing rather than disruption. Starting early is what keeps it smooth and keeps your options open.
Windows Server 2016 reaching end of life isn't a reason to panic, but it is a firm reason to plan.
The server won't stop working on 12 January 2027; the risk simply starts building quietly from that day on, in security, in compliance, and in the growing cost of staying put. The businesses that handle this well won't be the ones scrambling in late 2026; they'll be the ones who found their 2016 servers early, understood what each one did, and chose their route deliberately.
If you're not sure whether Server 2016 is still lurking somewhere in your setup, that's the first thing worth finding out - and the best time to find out is now.