OSSeva Blog
OperationsWindows Server 2016 end of support: what happens to the apps on it
Windows Server 2016 extended support ends on 12 January 2027. After that date Microsoft ships security updates for the operating system only to customers who buy Extended Security Updates (ESUs), for up to three years. The applications on the server keep their own clocks: SQL Server 2016 reached end of support on 14 July 2026 and .NET 8 on 10 November 2026. Moving the operating system does not move those dates, and OSSeva does not patch Windows Server itself.
Running Apache Tomcat in production? OSSeva patches and supports it, end-of-life versions included.
Apache Tomcat extended support: what is coveredWindows Server 2016 end of support dates
Mainstream support for Windows Server 2016 ended in January 2022; extended support, which delivers security updates only, ends on 12 January 2027. Microsoft lists three ESU years after that.
| Milestone | Date |
|---|---|
| Release | 15 October 2016 |
| End of mainstream support | January 2022 |
| End of extended support | 12 January 2027 |
| ESU Year 1 | 13 January 2027 to 11 January 2028 |
| ESU Year 2 | 12 January 2028 to 9 January 2029 |
| ESU Year 3 | 10 January 2029 to 8 January 2030 |
Source: the Microsoft Lifecycle page for Windows Server 2016 (Fixed Lifecycle Policy, updated 11 November 2026) and the Windows IT Pro blog post on the end of support for the 2016 releases (updated 22 October 2026), both read on 15 November 2026. The lifecycle page shows exact cut-off times in Pacific Time, so check it for the hour. Containers released with Windows Server 2016 follow the same dates.
What Extended Security Updates cover
ESUs are security updates for the operating system. They are not support for the applications on it. Microsoft's blog post says ESUs can be bought for up to three years after the end of support, and recommends moving to a current Windows Server release instead. Microsoft's overview of the Windows Server 2012 ESU programme describes ESUs as security updates rated critical and important, with no new features; read the 2016 terms on Microsoft's pages before you rely on the same scope.
How to buy them for Windows Server 2016 was still being finalised in Microsoft's own post: it said details on pricing and availability would follow. Trade press reported on 10 August 2026 that ESUs for Windows Server 2016 through Azure Arc were generally available. Check Microsoft's ESU documentation for the route that applies to your servers before you plan around either. This page gives no ESU price because Microsoft's lifecycle page does not.
The workloads on the server have their own end dates
A Windows Server 2016 box usually runs software whose support ends on a different day from the operating system. Check each one.
| Workload | Support status on 15 November 2026 | Where the dates are |
|---|---|---|
| SQL Server 2016 | Extended support ended 14 July 2026; ESUs run to 17 July 2029 | SQL Server 2016 end of support |
| SQL Server 2017 | Extended support ends 12 October 2027; no ESU programme published | SQL Server end of life dates |
| SQL Server 2019 | Extended support ends 8 January 2030; no ESU programme published | SQL Server 2019 end of support |
| .NET 8 | Security patches ended 10 November 2026 | .NET 8 end of life |
| Apache Tomcat 9.0 | Apache expects end of support no earlier than 31 March 2027 | Tomcat 9 end of life checklist |
| Java 8 | No single date: the JDK vendors list December 2030 | Java 8 end of life by distribution |
Sources: Microsoft Lifecycle pages for the SQL Server versions, Apache's Tomcat version page, and each JDK vendor's roadmap, as set out on the linked pages.
Your options before 12 January 2027
There are four ways to handle a Windows Server 2016 estate, and they combine.
- Move the operating system. Upgrade in place or rebuild on a current Windows Server release. Microsoft recommends Windows Server 2025. This is the option that ends the Windows Server question.
- Buy ESUs for the operating system. A bridge for servers that cannot move yet, bought from Microsoft.
- Move a workload off Windows. A SQL Server database that is the reason for a Windows Server 2016 box can move to PostgreSQL, which removes the SQL Server clock and the licence with it. The SQL Server to PostgreSQL migration page covers how OSSeva does that migration.
- Keep the application runtimes patched. A runtime that has passed its own end date stays exposed whichever operating system it runs on. OSSeva provides .NET 8 extended support, including installers for Windows, and patched builds for Tomcat and the Java stack, on the published patch windows of 48 hours for Critical and 7 days for High.
What OSSeva does not do: patch Windows Server, supply Windows ESUs, or take over the operating system. The operating system stays with Microsoft or whoever you buy ESUs from. OSSeva's part is the open source and runtime layer that sits on it.
Frequently asked questions
Is Windows Server 2016 still supported?
Yes, until 12 January 2027, in extended support: security updates only, no new features. Mainstream support ended in January 2022.
Is there Extended Security Updates for Windows Server 2016?
Microsoft's lifecycle page lists three ESU years, from 13 January 2027 to 8 January 2030. Microsoft's October 2026 blog post said pricing and availability details for Windows Server 2016 would follow, and trade press reported Azure Arc availability on 10 August 2026. Confirm the purchase route with Microsoft.
Does SQL Server stop being supported when Windows Server 2016 does?
No. SQL Server has its own lifecycle. SQL Server 2016 has already passed its end date, SQL Server 2017 ends on 12 October 2027 and SQL Server 2019 on 8 January 2030, whatever the operating system's date.
Does OSSeva patch Windows Server?
No. OSSeva patches open source software and runtimes such as PostgreSQL, Tomcat, Spring and .NET, including the Windows installers for .NET 8. Operating system updates come from Microsoft.
Tags
Related articles
SQL Server 2016 on Windows Server 2016: Two Deadlines, One Plan
November 17, 2026OperationsSQL Server 2016 End of Life: ESU Terms, Dates and Your Options
October 7, 2026OperationsSQL Server 2017 End of Life: 12 October 2027 and What to Do Before Then
October 7, 2026SecurityDoes Microsoft Offer Extended Security Updates (ESU) for .NET?
November 17, 2026OperationsWhat SQL Server ESUs Cost and When They Stop Making Sense
November 17, 2026OperationsSQL Server 2019 end of support: the dates, and when moving to PostgreSQL pays
October 7, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?