Windows Server 2016 end of life and end of support
Windows Server 2016 end of life is 12 January 2027: after that date Microsoft releases no more security fixes for it unless you pay for Extended Security Updates. This page is for IT managers, and the managers who hold the budget, who are responsible for business applications still running on 2016 servers.
Status on 12 November 2026
- Windows Server 2016
- Ending within a year
- Security fixes
- Ends 12 January 2027, in 61 days
- Released
- 15 October 2016
- Mainstream support ended
- 11 January 20221,766 days ago
- Security fixes end
- 12 January 202761 days from today
- Paid extension ends
- 12 January 20301,157 days from today
Dates come from the Microsoft product lifecycle; check there before relying on them for a decision.
Windows Server 2016 end of life: what ends, and what carries on
On 12 January 2027 Microsoft stops releasing security updates, bug fixes and technical support for Windows Server 2016. The January 2027 updates, released that day, are the last free ones. Nothing switches off. Websites keep serving, databases keep answering and scheduled jobs keep running, which is why the date tends to pass without anyone noticing.
The change is in what happens next. Each new vulnerability found in the operating system is published, fixed for newer versions and left open on yours. Over time other things stop arriving too: newer versions of SQL Server, backup agents, monitoring tools and security software drop support for an operating system their vendors no longer test against.
Two other things end on the same day or have already ended:
- .NET Framework 4.6.2, the version that shipped with Windows Server 2016, also goes out of support on 12 January 2027. An application still targeting it should move to .NET Framework 4.8, which is usually a small change.
- SQL Server 2016 went out of support on 14 July 2026. If the application’s database runs on the same server, see our SQL Server 2016 end of support page.
Windows Server dates at a glance
| Version | Mainstream support | Security fixes end | Paid updates |
|---|---|---|---|
| Windows Server 2012 and 2012 R2 | Ended 9 October 2018 | Ended 10 October 2023 | Ended 13 October 2026 |
| Windows Server 2016 | Ended 11 January 2022 | 12 January 2027 | To January 2030 |
| Windows Server 2019 | Ended 9 January 2024 | 9 January 2029 | |
| Windows Server 2022 | Ended 13 October 2026 | 14 October 2031 | |
| Windows Server 2025 | Until 13 November 2029 | 14 November 2034 |
If you are not sure which version a server is running, our guide to finding out which version you are running shows where to look.
What it means for the applications on the server
For a business system, the server is rarely the hard part. The work is in whatever runs on it.
- The application’s framework. An application still on .NET Framework 4.6.2 needs moving to 4.8 before or during the server move.
- Things installed by hand. Older applications often depend on components registered on the server years ago: COM libraries, reporting runtimes, a specific database driver, fonts, certificates. These are not in the source code and have to be found and reinstalled.
- IIS settings. Application pool identities, bindings, authentication modes and rewrite rules live in the server’s configuration, and an application can fail on a new server simply because one was missed.
- Scheduled tasks and services. Overnight imports, report emails and clean-up jobs frequently run as Windows scheduled tasks under a named account that nobody has logged into for years.
- What connects to it. Other systems, file shares and firewall rules refer to the old server by name or address.
None of this is difficult once it is written down. It is the discovery that takes the time.
Questions to ask the application’s supplier
The server belongs to you, but the application on it often belongs to someone else. Before choosing a route, ask the supplier, in writing:
- Is the application supported on Windows Server 2022 or 2025? Which versions, exactly?
- Which SQL Server version and which .NET Framework or .NET version does it need?
- Who installs and patches the application on a new server: you, or them? What do they charge for it?
- Is there a newer version of the application we would need to move to first?
- Are they still trading and still supporting this product?
If the supplier has gone, or does not answer, the application has become yours to look after. Our page on unsupported software covers that situation.
Your options
Move to a supported version. The lasting fix. Windows Server 2022 and 2025 are both supported into the 2030s. A move is also the natural moment to bring the database and the application’s framework up to date, since everything is being tested anyway. Our Windows Server 2016 upgrade options guide compares an in-place upgrade with building a new server.
Move to the cloud at the same time. If the server is physical hardware of the same age, replacing it like for like means buying new hardware. Our cloud migration page describes how we rehearse a move so that the cut-over is routine.
Buy Extended Security Updates. A paid stopgap that keeps critical and important security fixes coming for up to three years. It makes sense for an application that genuinely cannot move by 12 January 2027, for example because its supplier has not yet confirmed support for a newer version, as long as the time bought is used to move it. Points to know before you rely on it:
- For Windows Server 2016, ESUs are paid even for servers running in Azure. The free ESUs that Windows Server 2012 had in Azure do not apply.
- Outside Azure they are bought either through Microsoft volume licensing, which needs active Software Assurance or subscription licences, or monthly through Azure Arc. Check which applies to your licences now, not in January.
- They are sold a year at a time, and you cannot buy year two without year one. Signing up late through Azure Arc is back-billed to the end-of-support date.
- They include no technical support beyond the updates themselves.
Microsoft’s ESU FAQ has the current terms; your licensing partner can quote the price.
Isolate and accept the risk. For a system with a short remaining life, restricting who and what can reach the server reduces the exposure. It does not remove it, and an auditor or insurer may not accept it.
A plan for the weeks to 12 January 2027
Working back from the date, a realistic order is:
- By the end of November: inventory. List every 2016 server and, for each one, the applications, sites, services, scheduled tasks, installed components, databases and inbound connections. Name an owner for each application.
- Early December: supplier answers and licensing. Send the questions above to each supplier. Ask your licensing partner whether you can buy ESUs and through which route.
- December: decide per server. Move, buy ESUs, or isolate. A server whose application is confirmed on a newer version and is simple to rebuild can move. One that is not confirmed is an ESU candidate.
- Before any Christmas change freeze: rehearse. Build a test server on the target version, install the application and run it against a copy of the data. Whatever breaks is the real list of work.
- Early January: cut over or cover. Move the servers that are ready. Have ESUs in place for the rest before 12 January 2027, and a dated plan to move them.
A server that misses the date is not a disaster, but it needs a written decision and an owner.
What to tell your board, auditor or insurer
They need facts, not reassurance. For each 2016 server: what it runs, the end-of-support date, the option chosen, who owns it and when the work will finish. Our guide to making the business case before end of support sets out how to put that to the people who approve the budget.
If your organisation holds Cyber Essentials, the scheme’s requirements document (v3.3, April 2026) says all software on in-scope devices must be licensed and supported, and removed when it becomes unsupported, or placed in a sub-set that prevents all traffic to and from the internet. High and critical security updates must be applied within 14 days of release. Whether paid ESUs count as supported for your assessment is a question for your certification body. Cyber insurance forms and customer security questionnaires often ask the same question in their own words.
What we would check first
We would start with the inventory above, then build a test server on a supported version and rehearse the move. If nobody is sure what depends on the server, a code audit produces that inventory and a plan at a fixed price. If the database needs moving too, our SQL Server and Windows Server compatibility table shows which versions run together. If the application itself is on an old framework, our .NET Framework page covers the options, and our software maintenance service can look after it once it has moved.
Get a reminder
Windows Server 2016 stops receiving security fixes on 12 January 2027. Put the date where you will see it.
Add a reminder to your calendarNot sure where Windows Server 2016 is still running?
Most organisations find more copies than they expected. Two ways to find out, depending on how much you want to know.
Check which version you have
Standard, Datacenter and Essentials editions share the same dates. So do servers installed with and without the desktop.
How to check every productOn the server, run winver, or this PowerShell command. The build number identifies the release.
(Get-CimInstance Win32_OperatingSystem) | Select-Object Caption, BuildNumber | Build number | Product |
|---|---|
| 9200 | Windows Server 2012 |
| 9600 | Windows Server 2012 R2 |
| 14393 | Windows Server 2016 |
| 17763 | Windows Server 2019 |
| 20348 | Windows Server 2022 |
| 26100 | Windows Server 2025 |
When it is not yours to upgrade
A server is often kept on an old version of Windows because of one thing running on it: a packaged application its vendor only certifies on that version, a hardware controller with an old driver, or a licence dongle.
List what each server runs before planning its upgrade, and ask each vendor in writing which Windows Server versions their product supports. Where the answer is none of the current ones, the choice is between replacing that product and isolating the old server from the rest of the network.
Making the case for the work
An upgrade nobody outside IT can see is easy to defer. These are the reasons that tend to move it up the list.
- Cyber Essentials
- The scheme requires software in scope to be supported by its vendor. Anything past its end-of-support date has to be removed, or cut off from the internet, before you can certify or renew.
- Cyber insurance
- Proposal forms commonly ask whether you run unsupported software. Check what yours asked, and what you answered.
- Customer questionnaires
- Larger customers ask the same question of their suppliers. An honest "yes, and here is the plan" is a better answer than a late discovery.
- Personal data
- UK data protection law expects appropriate technical measures to protect personal data. Software that can no longer be patched is hard to square with that.
- The cost of waiting
- An upgrade done to a deadline, after something has failed, costs more than the same upgrade planned. Where Microsoft sells a paid security extension, its price has risen each year it runs.
- Official guidance
- The National Cyber Security Centre is blunt: "The only fully effective way to mitigate this risk is to stop using the obsolete product." See its guidance on obsolete products.
What we do and do not sell: we do not sell Microsoft licences or Extended Security Updates, so we have no stake in which version you choose. Our part is the application: finding what depends on the old version, testing it against the new one and fixing what breaks.
Supported versions to move to
How long each would keep you in support. All Windows Server versions
| Version | Released | Mainstream support ended | Security fixes end | Status today |
|---|---|---|---|---|
| Windows Server 2022 | 18 August 2021 | 13 October 2026 | 14 October 2031 | Supported |
| Windows Server 2025 | 1 November 2024 | 13 November 2029 | 14 November 2034 | Supported |
Questions we are asked
When does Windows Server 2016 reach end of life?
Extended support ends on 12 January 2027. Mainstream support ended on 11 January 2022, so the server has received security fixes only since then.
What happens to Windows Server 2016 on 12 January 2027?
Nothing switches off. The server and everything on it carry on running. What stops is the monthly security fixes, so each vulnerability found after that date stays open on your server unless you have paid for Extended Security Updates.
Is there extended support for Windows Server 2016 after 2027?
Microsoft sells Extended Security Updates for up to three years, to January 2030. They cover critical and important security fixes only, not technical support or other bug fixes. Unlike Windows Server 2012, they are a paid offering even for servers running in Azure. They are bought a year at a time, and the second and third years can only be bought if you bought the years before.
Can Windows Server 2016 be upgraded in place?
Yes. Microsoft supports in-place upgrades from Windows Server 2016, and from Windows Server 2025 a non-clustered server can upgrade directly across up to four versions. Many teams still prefer to build a new server and move the application across, because the old server stays untouched as a fallback until the new one has proved itself. Our guide to Windows Server 2016 upgrade options covers both routes.
Which Windows Server version should we move to?
Windows Server 2022 or 2025. Both receive security fixes into the 2030s. The deciding factor is usually the application rather than the server: use the newest version the application's supplier supports, and the SQL Server version it needs.
Does SQL Server 2016 on the same server matter too?
Yes. SQL Server 2016 went out of support on 14 July 2026, so a 2016 server that also hosts its database is already running one unsupported product. It makes sense to move both at once, since the application has to be tested either way.
Send us your version list
Paste the output of the free check, or list the Windows, SQL Server, .NET and Office versions your application runs on and how it is hosted. We reply within a working day with what is exposed, what to fix first and what each step is likely to involve. No charge and no commitment; it is the same first look we do before any takeover.
Running a version that is out of support?
Tell us which version, what depends on it and how it is hosted. We will set out the upgrade route and what it is likely to involve.