Free tool · Microsoft end of support
Microsoft end-of-support lookup
Pick your Windows Server, SQL Server, .NET or Windows version and see when Microsoft stops sending security fixes for it, how long you have left, and whether paid Extended Security Updates can buy you time.
Your result
Choose a product and a version to see its dates.
- Mainstream support ends
- Security updates end (extended support)
- Support ends
- Paid Extended Security Updates until
monthmonths of security updates left.
Less than a month of security updates left.
No security updates for monthmonths.
Security updates stopped less than a month ago.
Microsoft still fixes bugs and security holes in this version. Keep installing its updates and you are covered.
Microsoft now sends security fixes only: no new features and no other bug fixes. It is safe while you keep patching, but start planning the move before the date above.
Microsoft still sends security fixes for this version, as long as you install them.
Under a year to go. Testing an application on a newer version and moving it usually takes months, not days. Start now.
Microsoft no longer fixes security holes found in it. It keeps running, which is why the risk is easy to miss. If the system holds customer data, expect your auditor, insurer or customers to ask about it.
Microsoft still sells Extended Security Updates for it until : security fixes only, paid for a year at a time. A way to buy time to move, not a place to stay.
The paid Extended Security Updates have ended too, so there is no way left to get Microsoft's security fixes for it.
Microsoft's lifecycle page lists no paid Extended Security Updates for this version.
.NET Framework 4.5.2 and later is part of Windows. It gets security fixes for as long as the Windows version it is installed on is supported. Look up that Windows version instead: on Windows Server 2016 that is until 12 January 2027, on Windows Server 2022 until 14 October 2031. Later 4.x versions install in place over earlier ones, and Microsoft expects applications built for an earlier 4.x to keep running on them.
That date applies on Windows 10 version 1809, Windows Server 2019 and later, where 3.5 SP1 is a product of its own. On older Windows it is part of the operating system and ends when that Windows version does.
Microsoft's .NET Framework page gives 4.6.2 its own end date. 4.8 and 4.8.1 install in place over it, and Microsoft expects applications built for 4.6.2 to keep running on them without being rebuilt.
.NET is only supported on its latest patch, so keep the runtime updated. Long Term Support (LTS) releases get three years, Standard Term Support (STS) releases two.
These are the dates for Home and Pro editions. Move to a newer Windows 11 version before the date to stay supported. Enterprise and Education editions have their own dates.
Organisations can buy Windows 10 Extended Security Updates a year at a time, for up to three years; Microsoft quoted US$61 per device for year one, doubling each year. Version 22H2 is required.
Dates are from Microsoft: its lifecycle pages for each product (linked under each table below) and the .NET and .NET Core support policy (last updated 13 October 2026). Microsoft gives them in US Pacific Time, so in Malaysia a last day ends on the following afternoon. Checked on 23 October 2026. Microsoft can change these dates, so confirm yours on its page before you plan around it. Not advice.
What the dates mean
Mainstream support
At least the first five years. Microsoft sends security updates and other fixes, and still accepts requests for non-security fixes.
Extended support
Security updates only, at no extra cost. When it ends, so do the security fixes. For Windows Server and SQL Server this is the date that matters.
Paid Extended Security Updates
For some versions Microsoft sells up to three more years of security fixes, paid for yearly. Some versions get them at no extra charge when they run in Microsoft Azure.
One date: .NET and Windows 11
These have a single end date per version. .NET LTS releases get three years and STS releases two; Windows 11 is supported version by version.
Every version and its dates
Click a version to see it in the lookup. Dates that have already passed, by your device's date, are shown in red.
Windows Server
| Version | Mainstream support ends | Extended support ends | Paid ESU until |
|---|---|---|---|
| Not offered | |||
| Not offered | |||
| Not offered | |||
| Not offered | |||
| ( on Azure only) | |||
| ( on Azure only) |
Source: Microsoft lifecycle pages for Windows Server 2025, 2022, 2019, 2016, 2012 R2, 2012, 2008 R2 and 2008.
SQL Server
| Version | Mainstream support ends | Extended support ends | Paid ESU until |
|---|---|---|---|
| Not offered | |||
| Not offered | |||
| Not offered | |||
| Not offered | |||
| ( on Azure only) | |||
| ( on Azure only) |
Source: Microsoft lifecycle pages for SQL Server 2025, 2022, 2019, 2017, 2016, 2014, 2012, 2008 R2 and 2008. Every edition of a version, Express included, has the same support dates; paid ESU is not offered for every edition.
.NET Framework
| Version | End of support |
|---|---|
| Follows the Windows version it runs on | |
| Follows the Windows version it runs on | |
| Follows the Windows version it runs on | |
| Follows the Windows version it runs on | |
| Follows the Windows version it runs on | |
| on Windows 10 version 1809, Windows Server 2019 and later. On older Windows, follows that Windows version. | |
Source: Microsoft's .NET Framework lifecycle page and .NET Framework lifecycle FAQ.
.NET and .NET Core
| Version | Release type | End of support |
|---|---|---|
| LTS | ||
| STS | ||
| LTS | ||
| – | ||
| – | ||
| – | ||
| – | ||
| – | ||
| – | ||
| – | ||
| – | ||
| – | ||
| – |
Source: Microsoft's .NET and .NET Core support policy, last updated 13 October 2026. .NET 11 is not out yet.
Windows 10 and 11, Home and Pro
| Version | End of support |
|---|---|
Source: Microsoft lifecycle pages for Windows 11 Home and Pro and Windows 10 Home and Pro, and the Windows 10 Extended Security Updates programme.