Windows Server 2016 · end of life

Support ends on 12 January 2027. Here is exactly what that means, and your three options.

After that date Microsoft stops issuing security updates for Windows Server 2016. No pitch below, just the plain answer and the real costs, so you can decide what to do.

Talk it through, no charge
A 3-minute read. Or call 0151 452 3060.
I'm Eric at HiltDigital. I built the 2-minute checker, but if you would rather just have the answer than fill anything in, this page is it.

What "end of life" actually means for you

It is not that the server stops working on 13 January. It keeps running. The problem is that it stops getting security patches, and three things follow from that.

1

Cyber Essentials becomes an automatic fail

An unsupported operating system cannot meet the "keep your software up to date" control. If you hold Cyber Essentials, or a client, insurer or tender ever asks for it, the certificate you rely on to win or keep work lapses.

2

Your cyber insurance gets shaky

Insurers have tightened the "supported software" wording in cyber policies. Running an end-of-life server past the deadline can sit on the wrong side of that clause, so a ransomware claim in 2027 could come back declined rather than paid. The server does not even have to be the way in for the claim to be questioned.

3

It becomes the soft target

Once patching stops, every newly discovered flaw stays open for good. Attackers scan specifically for end-of-life systems because they know the door will never be fixed.

Are you even affected?

Most owners genuinely do not know what their server is or what it does, and that is completely normal. You are affected if any of this runs on Windows Server 2016:

  • A file server or shared drive in a cupboard or comms room
  • Your domain controller (the thing everyone logs in against)
  • A line-of-business app: accounts, practice management, an ERP or database
  • Remote desktop / a server people log into to work
  • An on-premise Exchange or SQL server

Not sure which version you are on? That is the most common question we get, and it takes us a couple of minutes to tell you. Ask me and I will check for you.

Your three options, with real costs

There is no single right answer. It depends on what the server does and where you want to be in three years. Here is the honest version of each.

1. Stay put and buy Extended Security Updates (ESU)

Escalating yearly

Microsoft sells security patches for the old server for up to three more years. The price climbs each year, roughly three quarters of the licence cost in year one, the full cost by year three, and it is capped at three years. It covers critical and important security patches only: no bug fixes, no new features, and your other software vendors quietly stop testing against the old OS.

Right when: you have one specific blocker and a firm date to clear it.
The catch: it is an escalating bill for a problem you still have to solve, and the door closes after three years anyway.

2. Upgrade to a current on-premise server

One-off project

A new Windows Server (2022 or 2025) is supported well into the 2030s. It is a capital cost plus the migration work, but if you genuinely need a server in the building, it buys you the better part of a decade and keeps you compliant.

Right when: you need on-premise hardware (large local files, specific apps, poor connectivity).
The catch: you are buying hardware you will have to do this dance with again eventually.

3. Move the workload to the cloud

Monthly, no big capital cost

Often the file server becomes SharePoint or OneDrive, and any server that has to stay a server moves to Azure, where the same Extended Security Updates are included at no extra cost while you modernise. It turns a big one-off bill into a predictable monthly one and takes the end-of-life treadmill off your plate.

Right when: most of what the server does is files and apps that have modern cloud equivalents.
The catch: it needs planning and decent connectivity, so it is a project, not a switch you flip.

What to actually do next

  1. Find out what you have got. Confirm whether anything really runs on Server 2016 and what it does. This is the step most people skip and then panic about later.
  2. Pick the path. Match the server's job to one of the three options above. For most small businesses it is cloud or a straight upgrade; ESU is a bridge, not a destination.
  3. Plan the cutover before the deadline. A migration is not a weekend job, and rushing a server move over Christmas is how things break. Start now and you do it calmly; leave it and you either rush or pay for ESU to buy time.

Not sure which one is yours?

Tell me what you have got and I will tell you which of the three options fits, roughly what it costs and the order to do it in. No charge, and a straight answer either way, even if the answer is "you have got ages, relax".

Talk it through with me Or call 0151 452 3060