Windows Server 2016 support ends in January 2027: what to do now

The date is published, fixed and not in dispute: 12 January 2027. After it, extended support for Windows Server 2016 ends, and that is the last day a security fix is issued for the system. Mainstream support had already ended five years earlier, in January 2022.

And nothing will happen to the server on 13 January. It will boot and run and carry the accounting system exactly as it did the day before. Which is precisely how these dates pass a company by: without an event.

What actually stops

One thing, and it is the one that matters: security patches. Every vulnerability found in Windows Server after that date stays open on your machine, and it will be known, published and have a ready-made tool written for it — because vulnerabilities are published when they are patched, and the patching is what stops.

That inverts the situation: a server without updates is not merely less protected than a patched one, it is an easier target, because the list of ways into it grows every month and never shrinks.

Who would bother with an internal server anyway?

A fair question: the server is inside the company and behind a firewall, so how would anyone reach it? The answer is that most of what hits a company does not arrive at the server from outside. It arrives on a staff machine — a message, or remote access left open — and then moves around inside looking for whatever is unpatched. The old server is the first thing it finds.

The three options, honestly

One: upgrade the system on the same machine. Possible if the hardware will carry a newer release. But a server bought to run 2016 is usually eight years old or more by now, and you would be putting a newer system onto hardware that has itself left its manufacturer's support. You pay for a new licence to defer the question by a year.

Two: a new server with a new licence. The cleanest, and what we recommend for anyone whose machine has reached that age. You collect two wins at once: a supported system and hardware under warranty. And choosing the specification starts from the workload, not from the model.

Three: move the service instead of upgrading it. If the server only carries mail, or only files, the question is not which system but whether you need a server for it at all. Some workloads move to a subscription and the matter ends. Others — an accounting system on a local database — do not, and saying otherwise is selling rather than advising.

Start from an inventory, not from a decision

Before deciding anything, know what you have. What we see most often is a server nobody is quite sure about, so the decision is deferred for fear of breaking something unknown. An inventory removes that fear:

• Which release exactly, which machine, and how old
• What it actually runs: a database, files, the domain, mail, print
• Who depends on it, and which application will not work without it
• Whether the software on it supports a newer system — a question for your software vendor, not for us and not for Microsoft
• And when a backup was last actually restored from

Why now rather than December

Because what is left between today and the date is enough to do this in order: take the inventory, ask your software vendor, get the budget approved, order, migrate over a weekend, and leave the old machine running for a week as a fallback. Anyone starting in December does all of that compressed, migrates on a working day, and switches the old one off immediately because its rack space is needed.

The difference between the two is not cost. It is the number of surprises.

In short

• 12 January 2027 is the last security patch for Windows Server 2016.
• The machine will not stop — it simply becomes a target whose entry routes widen month by month.
• The danger usually comes from inside the network, not straight off the internet.
• Start with the inventory, and ask your software vendor first.
• The remaining time is enough to do it in order. December will not be.

ZEMAVO Technology supplies servers and Windows Server licensing against proper tax invoices, moves your data off the old machine, and tests the restore before handover.