← Back to blog

DVG Systems Windows Server

Windows Server 2016 Support Ends 12 January 2027

7 min read
On this page

If there is still a physical server humming in a closet in your building, there is a reasonable chance it runs Windows Server 2016. It has been reliable, and nothing about it feels urgent. It stops getting security updates on 12 January 2027.

This is not the same conversation as Windows 10 going out of support last year. A desktop out of support is a risk you can isolate. A file, print, application or domain server out of support is the thing every other device in the building trusts, which is exactly why attackers go looking for it.

What actually happens on 13 January 2027

Nothing visible. The server boots, shares stay mapped, printing works, and your application runs as it did the week before.

What changes is that Microsoft stops shipping security updates for the operating system, so every vulnerability found after that date stays open on your box permanently. Mainstream support ended in January 2022; extended support ends on 12 January 2027, and there is no further extension.

You also lose support. Microsoft will not take a ticket on an out-of-support operating system, and most software vendors quietly match Microsoft’s dates. That usually bites when something breaks and the vendor asks what OS it runs on.

The Office problem that has already happened

Here is the part that surprises people, because the date has passed.

Microsoft 365 Apps stopped being supported on Windows Server 2016 on 14 October 2025. If you run Word, Excel or Outlook on a Remote Desktop Services session hosted on a 2016 box — a common setup for shared Sage, accounting or dispatch workflows in the North — you are already outside the supported configuration.

Microsoft is still shipping security updates for Microsoft 365 desktop apps on Server 2016 up to 10 October 2028, with two conditions: they are available only for unmanaged devices that update directly from the Microsoft CDN, and feature updates stop at Version 2602. If your Office updates come from your own distribution point, that is not a theoretical gap.

SQL Server 2016 went in July

One more date to check while you are in the closet: SQL Server 2016 reached end of extended support on 14 July 2026. Plenty of line-of-business applications sit on SQL Server Express 2016 without anyone thinking of it as a database.

Extended Security Updates, and why you probably cannot buy them

Microsoft’s paid bridge is the Extended Security Updates programme. It exists for Server 2016 — three annual terms ending 11 January 2028, 9 January 2029 and 8 January 2030, each delivering only Critical and Important security updates. Four things about it tend to end the conversation for a small business:

  1. It costs 100% of the full licence price, every year — not a maintenance fee, but the price of buying the server licence again, annually, for up to three years.
  2. You need active Software Assurance or subscription licences to qualify. ESUs are sold to customers with active SA under an Enterprise Agreement, Server & Cloud Enrollment or similar, or with active subscription licences through a programme such as CSP. A server bought with an OEM licence and never covered by SA generally does not qualify — and that describes most small-business servers we see.
  3. Azure does not make it free. Windows Server 2012 and 2012 R2 get free ESUs on Azure virtual machines; Windows Server 2016 explicitly does not.
  4. It buys you patches, not help. ESU includes no technical support. Microsoft’s own description is “a last resort paid option” and “a temporary bridge to stay secure while one migrates”.

Two details catch people who try to enrol late. Sign up through Azure Arc after the end-of-support date and Microsoft back-bills a one-time charge for the months you missed, so waiting saves nothing. And you need active SA or equivalent subscription licences on your client access licences to reach an ESU-covered server at all.

The four realistic options

Upgrade the operating system, in place or on new hardware. For a file-and-print or domain controller role this is usually straightforward; the work is in the applications, not the OS.

Move the workload to Microsoft 365 or Azure. Most of what we still find on 2016 boxes is file shares, which belong in SharePoint or OneDrive, plus an application that may well have a hosted version now. Moving it to Azure also removes the “what happens when the building loses power” question.

Replace the application, if what keeps you on Server 2016 is software whose vendor stopped developing it. The date is forcing a decision you were going to face anyway.

Buy ESU and migrate behind it — legitimate if you qualify and have a real migration date, but not a plan on its own.

What to do before 12 January 2027

The time before 12 January 2027 is enough to find out what you are dealing with — not enough to discover in late December that your dispatch software will not run on anything newer.

  • Inventory the server honestly — every role, share, scheduled task, service account and device pointing at it, including the photocopier and the alarm panel.
  • Ask each software vendor, in writing, which Windows Server versions they support. This determines everything else, and it is the step with a lead time.
  • Check your licensing position before assuming ESU is available to you.
  • Confirm the backups actually restore. If you are about to migrate, this is the week to test a restore, not the week after.
  • Decide on a date and write it down, so January is a scheduled project rather than a surprise.

While you are checking dates: Windows Server 2019 runs to 9 January 2029, and mainstream support for Windows Server 2022 ended in October 2026. If you are buying hardware now, buy for the long date.

Send us the server details or book a free assessment and we will tell you what is on the box, what moves easily, what does not, and what it costs either way.

Frequently Asked Questions

What is the exact Windows Server 2016 end of support date?

12 January 2027. Microsoft’s lifecycle page lists extended support ending at 1/13/2027 06:59:59 Pacific Time, which its own ESU documentation states as 12 January 2027. Mainstream support ended in January 2022.

Will my server stop working on 13 January 2027?

No. Nothing switches off. The server keeps running exactly as it did; it simply stops receiving security updates, and Microsoft will no longer take a support ticket on it.

Can I buy Extended Security Updates and deal with it later?

Only if you qualify. ESU requires active Software Assurance or subscription licences, costs the full licence price each year, and provides no technical support. Enrol late through Azure Arc and Microsoft back-bills the months you missed.

Does this affect Office on my terminal server?

Yes, and it already has. Microsoft 365 Apps stopped being supported on Windows Server 2016 on 14 October 2025. Security updates continue to 10 October 2028, but only on unmanaged devices updating directly from the Microsoft CDN, and feature updates stop at Version 2602.

We are a First Nation, clinic or non-profit on a tight budget. What is the cheapest safe path?

Usually not ESU. Moving file shares into Microsoft 365 you already licence, and the remaining application onto a current or hosted server, is almost always cheaper over three years than paying the full licence price annually for patches.

What about SQL Server on the same box?

Check the version. SQL Server 2016 reached end of extended support on 14 July 2026, so if your application installed its own SQL 2016 or SQL 2016 Express instance, that is already out of support independently of the operating system.

Sources and last verified

Last verified 16 November 2026. Dates, pricing and eligibility rules change; check the linked pages before relying on a figure.

Ask AI

Accessibility