Windows Server end of support comes on a different date for each version. Windows Server 2016 is next in line, with 12 January 2027 as its last date on Microsoft’s list. After that day the server keeps running, but Microsoft stops shipping security updates for it. If needed, Extended Security Updates can then cover a set number of years after the date.
Last reviewed 2026-11-14 by Manish Sharma.
Mainstream support is the first phase of Microsoft’s lifecycle, when a product gets security updates as well as other fixes. Extended support follows, with security updates but no non-security fixes, design changes or new features, per Microsoft’s Fixed Lifecycle Policy. Then Extended Security Updates (ESU), a separate program, adds security updates for a limited time after extended support stops. This article is for IT heads and infrastructure managers in India and the GCC. Its readers run Windows Server and SQL Server on premises. It covers the dates and their effect on a running estate, but gives no prices and no migration steps. For the server move itself, see the checks to run before, during and after moving a Windows Server host.
Windows Server End of Support Dates by Version
Each version has two dates that matter: the close of mainstream support and the close of extended support. The table shows them as Microsoft’s Windows Server release information prints them, as of November 2026. For three of the four versions, that page shows “End of updates” in the mainstream column. That is, the first phase has already passed.
| Version | Build | Mainstream support | Extended support |
|---|---|---|---|
| Windows Server 2016 (version 1607) | 14393 | End of updates | 12 January 2027 |
| Windows Server 2019 (version 1809) | 17763 | End of updates | 9 January 2029 |
| Windows Server 2022 | 20348 | End of updates | 14 October 2031 |
| Windows Server 2025 | 26100 | 13 November 2029 | 14 November 2034 |
For Windows Server 2022, the release page also shows “End of updates”. Its own lifecycle page puts the close of mainstream support in October 2026. The stamp there is 10/14/2026 6:59:59 AM Pacific Time.
The nearest date on the list is the windows server 2016 end of support on 12 January 2027. That is about two months from the time of writing. Older versions are already past every date. For Windows Server 2012 and 2012 R2, the last ESU year closed on 13 October 2026, per Microsoft’s ESU overview. In practice, a 2012 server in production today has no security updates left from that program. A 2016 server, by contrast, still has about two months of extended support left.
Key Takeaway Plan Windows Server end of support server by server, each against its own date.
Mainstream, Extended and the Last Covered Day
Use the day the release information page prints. Microsoft’s own pages decide the date whenever another source gives a different one.
If you open the Windows Server 2016 lifecycle page, you will see a different-looking value. That page stamps the close of extended support as 1/13/2027 6:59:59 AM, in Pacific Time. The release information page, however, lists 2027-01-12. This article uses the release-page day for every Windows Server version. For that reason, the table says 12 January 2027.
Some dates have no row on the release page, such as the 2022 mainstream date and the SQL Server dates below. For those, the article gives the month and the lifecycle stamp as shown. The exact day stays open until a Microsoft page states the day convention.
For a plan, an audit file or a board paper, copy the date from the Microsoft page. Then record the page and the day you read it.
What Stops at Windows Server End of Support
On the date, Microsoft stops releasing security updates and bulletins for that version. Microsoft ships no fix for a flaw found later, unless you have ESU or a supported version.
Microsoft’s ESU overview is written for Windows Server 2012 and 2012 R2. Still, it puts the effect plainly for the program in general: running an unsupported version “can cause security or compliance issues”. That applies to the operating system and every role on it, such as file shares, domain services and web servers.
Before you decide on any server past its Windows Server end of support date, we recommend a vulnerability assessment. It shows which known flaws are already present. The decision can then rest on the actual exposure of each server as well as its age.
Application Support Can End Before the OS
Application support can stop earlier than the operating system it runs on. For example, Microsoft has a page about Microsoft 365 Apps on Windows Server.
That page says support for Microsoft 365 Apps on Windows Server 2016 ended on 14 October 2025. The same date also applies to Windows Server 2019. On Windows Server 2022, the apps had support while the operating system was in mainstream support. That phase closed in October 2026. In each case, the operating system itself still had extended support left.
Microsoft does continue security updates for the apps on all three versions until 10 October 2028. However, the updates reach only unmanaged devices that update directly from Microsoft’s content delivery network (CDN).
If a server takes its updates through an internal update service, it may fall outside that scope.
The same pattern can apply to line-of-business software. An accounting package, a document system or a reporting tool can drop support for a server version before Microsoft does. We recommend asking each application vendor for its own support date in writing, per version. Then record it beside the operating system date.
Extended Security Updates as a Time-Boxed Bridge
ESU adds security updates for a limited time only. For Windows Server 2016, the Windows Server 2016 lifecycle page lists three yearly ESU terms. Year 1 starts on 13 January 2027, and Year 3 then closes on 8 January 2030.
Microsoft’s ESU overview describes what the program includes in general. However, that page is written for Windows Server 2012 and 2012 R2. It says ESU comes at no extra charge for servers hosted in Azure. For the choice of cloud, see how the two clouds compare for Windows Server hosting. Otherwise, it is available to purchase. It describes ESU as security updates rated critical and important. It also states that ESU does not include new features, customer-requested non-security hotfixes or design change requests. The same page calls ESU “a last resort option” for customers who need to run legacy products past their support date.
For a 2016 estate, read that as a planning limit. The 2016 lifecycle page lists three yearly terms, and the 2012 program’s rules suggest critical and important security fixes only. Meanwhile, any non-security bug stays unfixed, and support from application vendors may already have gone.
Buying a Windows Server 2016 ESU, eligibility and cost are questions for Microsoft or your licensing partner. This article does not cover them. Ask for the terms in writing, with the server count and the years you need. Do this before you treat ESU as part of the plan.
Key Takeaway In Signisys’s working view, ESU works best with a dated exit: a named route and target quarter for each server.
What Still Runs After the Support Date
Everything keeps running. The operating system starts and applications open. SQL Server also keeps serving queries the day after the support date, as it did the day before.
What changes is the exposure. In Signisys’s working view, the risk grows with each new flaw published for a version Microsoft no longer patches. A server can look stable for months while its exposure rises. The longer it stays in production, the more known issues it carries.
Outside parties may also ask which versions you run. In Signisys’s working view, a cyber insurer at a policy renewal may want to know. Likewise, an application vendor handling a support case may want to know. Some vendors may also ask you to reproduce a fault on a supported version first. Ask your insurer and each vendor what they require; this article names no insurer or vendor rule.
The servers themselves can also add a second deadline, when firmware and hardware support runs out on its own schedule. That is a separate question, covered in our article on what aging server hardware adds.
Database Versions on the Same Hosts
SQL Server has its own lifecycle, separate from the Windows Server host it runs on. A database can lose support before its host or after it. In either case, the earlier of the two dates sets your real deadline for that server. List both dates side by side for every host that carries a database.
SQL Server End of Support on Windows Server Hosts
The figures here come from Microsoft’s lifecycle page for each version, as of November 2026. They also draw on its SQL Server end of support options page. The lifecycle pages show dates in Pacific Time.
SQL Server end of support for the 2016 version arrived in July 2026, with the lifecycle stamp 7/15/2026 6:59:59 AM. Its lifecycle page also lists ESU years, and Year 3 closes on 17 July 2029. SQL Server 2017 follows in October 2027, with the stamp 10/13/2027 6:59:59 AM. Unlike 2016, its lifecycle page lists no ESU years.
For later versions, the lifecycle pages stamp extended support for SQL Server 2019 at 1/9/2030. Then come SQL Server 2022 at 1/12/2033 and SQL Server 2025 at 1/7/2036. The options page gives only the years 2030, 2033 and 2036. It also says the lifecycle page supersedes its table.
On terms, the options page says extended support includes only security updates. If a version offers ESU, it delivers critical security updates for up to three years past the support date. However, only customers with Software Assurance or subscription licenses can use it. A non-security bug gets no fix.
For example, take SQL Server 2016 on a Windows Server 2016 host. The database is already past its date, and the host follows in January 2027.
What Auditors Ask After Windows Server End of Support
A server past its Windows Server end of support date can become an audit question. That happens when nobody can show the date, the owner and the next step. Auditors and regulators can ask for two things: a dated list of software without support, and a plan for each item. For firms in India regulated by the RBI, a named direction sets this out.
The RBI Direction for Regulated Entities
RBI’s Master Direction on IT governance (RBI/2023-24/107, 7 November 2023) covers unsupported software in two clauses. Both sit under clause 9, IT Services Management. Clause 9(d) says regulated entities (REs) shall avoid using outdated and unsupported hardware or software. It also says they shall monitor software’s end-of-support (EOS) date. The same clause asks REs to track annual maintenance contract dates of IT hardware as well. That is a separate point from support dates for software.
Clause 9(e) then asks for a plan: REs shall develop a technology refresh plan for the replacement of hardware and software in a timely manner before they reach EOS.
The direction came into effect on 1 April 2024. It applies only to entities the RBI regulates under it. These are commercial banks, NBFCs in the Top, Upper and Middle Layers, credit information companies and the named all-India financial institutions.
For a regulated entity, the practical reading has two parts. The first is a register of every Windows Server and SQL Server version with its support date. The second is a refresh plan that names a date for each server before it reaches that point. A 2016 server with no plan before 12 January 2027 would miss what 9(e) asks for. How an inspection team treats that case is a question for your compliance team to take to the RBI.
Key Takeaway Under the RBI direction, a regulated entity’s 2016 servers need a refresh plan before 12 January 2027.
Other Sector Regulators in India and the GCC
Firms outside RBI’s scope still answer to someone. In India, that may be SEBI for market entities, or CERT-In for incident reporting. Likewise, in the GCC, central banks and national cyber agencies publish their own controls.
This article quotes no clause from those bodies. Instead, check your sector regulator’s current direction. Then ask your compliance team which clause covers unsupported software for your firm.
How to List the Versions You Run
You need one list. It holds each server with its Windows Server version and build, its SQL Server instances and each support date. Four steps produce it with tools already on the servers.
Run systeminfo on each server. Microsoft’s page on the command says it displays detailed configuration information about a computer and its operating system. Then read the OS name, version and build from its output. Add /s with a server name to query a remote server. You can also add /fo CSV to get output you can paste into a sheet.
Connect to each instance and run SELECT @@VERSION. Microsoft’s page on it says the output gives the SQL Server build as well as system information. That information includes the host operating system version. The same page notes that this operating system value may not reflect the retail version of the underlying operating system. Confirm it with the result from step 1.
Take each Windows Server build from the release information page and each SQL Server version from its lifecycle page. Then record the date, the page and the day you read it.
For every application on the server, add the vendor’s support date for that server version, in writing. Finally, mark the earliest of the three dates in each row.
For example, a firm in Pune or Dubai with forty servers across two sites still needs only one sheet. One named person keeps it. When you sort it by the earliest date, the next server due sits at the top.
Routes After Windows Server End of Support
There are four kinds of route for a server past its date. You can upgrade in place or rebuild on a newer version. You can also move the workload to the cloud. For a SQL Server database, see the order for moving a SQL Server database to the cloud. Another route is ESU for a set time, and the last is to retire the server and its application. Each route depends on the application, its vendor’s support and the time left on the list you built. Our use case page covers license and upgrade questions for these workloads. A move also brings its own risks older applications carry into a move, separate from the support date. Whichever route you take after Windows Server end of support, give each server a named owner and a target quarter.
A disclosure: Signisys offers cloud migration as well as cloud services and platform engineering. In a consultation, we review your Windows Server and SQL Server versions, their support dates and the audit questions you face. We promise no result. No charge, with a fixed scope.
Windows Server End of Support FAQ
Does a server stop working after Windows Server end of support?
Is Extended Security Updates a long-term answer?
Does Windows Server end of support matter outside banking?
Who should own the list of support dates?
Security Insights, Delivered.
Practical, vendor-neutral analysis of threats, tools, and architecture decisions.