Windows Server 2019 end of life and end of support
Extended support for Windows Server 2019 ends on 9 January 2029. Mainstream support ended on 9 January 2024, so the server already receives security fixes only.
Status on 3 October 2026
- Windows Server 2019
- Supported
- Security fixes
- Ends 9 January 2029
- Released
- 13 November 2018
- Mainstream support ended
- 9 January 2024998 days ago
- Security fixes end
- 9 January 2029829 days from today
Dates come from the Microsoft product lifecycle; check there before relying on them for a decision.
What ends, and what carries on
Two dates apply to Windows Server 2019. Mainstream support ended on 9 January 2024. Since then Microsoft has added nothing new and has fixed security problems only. Extended support ends on 9 January 2029, and on that day the security fixes stop as well.
Nothing switches off on either date. After the end date, each new vulnerability in the operating system is fixed for newer versions and left open on yours, and the vendors of databases, backup agents and security software stop testing against it.
So this is not urgent. It is a date to put in a plan and a budget.
What it means for the applications on the server
A lot of business applications arrived on Windows Server 2019 as part of a move off Windows Server 2012 or 2012 R2. That history matters, because the application was often copied across as it stood.
- The framework is not the pressure. Windows Server 2019 shipped with .NET Framework 4.7.2, which is supported for as long as the server is. A .NET Framework application here is on a supported runtime until the operating system’s own end date.
- What was carried over last time. Components copied by hand in the last move came along unchanged: COM libraries, a reporting runtime, an old database driver. They will have to be found and reinstalled again, and each move makes the original installers harder to locate.
- The database has its own dates. The SQL Server version on or beside this server may run out sooner than the server does. SQL Server 2016 is already out of support. See the SQL Server dates.
Your options
Stay, with the date in the plan. Windows Server 2019 receives security fixes until 9 January 2029. There is no reason to move for its own sake before then, provided updates are being installed.
Move to Windows Server 2022 or 2025. Windows Server 2022 receives security fixes until 14 October 2031 and Windows Server 2025 until 14 November 2034.
Combine the move with other work. If the application is due a database upgrade, a framework change or a move to the cloud, doing them together means testing once. Our cloud migration page describes how we rehearse a move.
Do not plan around a paid extension. Microsoft has sold Extended Security Updates for some earlier versions. None has been announced for Windows Server 2019.
What we would check first
We would start with the application, not the server. Which framework version does it target, which SQL Server version does it use, and which of its dependencies exist only on this machine? The answers decide whether the next move is a routine rebuild or a project.
Then we would write the inventory while there is no deadline: every site, service, scheduled task, certificate and installed component. If nobody is sure what the server does, a code audit produces that list and a plan at a fixed price.
Get a reminder
Windows Server 2019 stops receiving security fixes on 9 January 2029. Put the date where you will see it.
Add a reminder to your calendarNot sure where Windows Server 2019 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 2019 reach end of life?
Extended support ends on 9 January 2029. Mainstream support ended on 9 January 2024, so Windows Server 2019 has received security fixes only since then.
Will Windows Server 2019 stop working after January 2029?
No. The server and the applications on it carry on running. What stops is the monthly security fixes, so each vulnerability found after that date stays open on your server.
Is there extended support for Windows Server 2019?
Windows Server 2019 is in extended support, which means security fixes only, until 9 January 2029. Microsoft has not announced a paid Extended Security Updates programme for the period after that date, so do not plan around one.
Do we need to move off Windows Server 2019 yet?
No. It receives security fixes until 9 January 2029, so there is no need to move for its own sake. The sensible time is when the hardware, the database or the application is being changed anyway, and before the end date.
Which .NET Framework version comes with Windows Server 2019?
.NET Framework 4.7.2. It is supported for as long as the Windows version it is installed on, so on Windows Server 2019 it receives fixes until the server's own end date.
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.