Windows Server End of Life Dates
other
Developers have been relying on server-oriented releases of the Windows NT operating system since 1993, when Microsoft first introduced the brand name Windows Server. This operating system has been continuously developed and maintained by Microsoft, with the first release being Windows NT 3, to provide a robust and reliable platform for server operations. The primary purpose of Windows Server is to provide a secure and efficient way to manage and deploy server applications, making it an essential tool for developers who need to ensure the smooth operation of their server infrastructure.
The end-of-life landscape for Windows Server is complex, with a total of 20 versions released to date. Out of these, 16 versions have already reached their end-of-life, leaving 4 active versions that are still supported by Microsoft. The latest stable version of Windows Server is 10.0.14393, and developers should be aware that version 2016 is next in line to expire, with its end-of-life date set for January 12, 2027. The most recent version to reach its end-of-life was 23h2-ac, which expired on October 24, 2025. This highlights the importance of keeping track of the lifecycle of each version to ensure that developers can plan and prepare for upgrades and migrations.
Given that there are currently no known Common Vulnerabilities and Exposures (CVEs) tracked for Windows Server, the security picture appears to be favorable. With zero critical CVEs and no most affected version, developers can have confidence in the security of their Windows Server deployments. Since there are no known vulnerabilities, the Known Exploited Vulnerabilities (KEV) status is not applicable. Nevertheless, developers should still take proactive measures to ensure the security of their server infrastructure, such as regularly reviewing and updating their systems to the latest versions and applying security patches as soon as they become available.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2025 LTS | Nov 1, 2024 | Nov 13, 2029 | Nov 14, 2034 | in 3035d | 10.0.26100 | — | Active | |
| 23h2-ac | Oct 24, 2023 | Apr 24, 2025 | Oct 24, 2025 | 273d ago | 10.0.25398 | — | EOL | |
| 2022 LTS | Aug 18, 2021 | Oct 13, 2026 | Oct 14, 2031 | in 1908d | 10.0.20348 | — | Active | |
| 20h2-sac | Oct 20, 2020 | Aug 9, 2022 | Aug 9, 2022 | 1445d ago | 10.0.19042 | — | EOL | |
| 2004-sac | May 27, 2020 | Dec 14, 2021 | Dec 14, 2021 | 1683d ago | 10.0.19041 | — | EOL | |
| 1909-sac | Nov 12, 2019 | May 11, 2021 | May 11, 2021 | 1900d ago | 10.0.18363 | — | EOL | |
| 1903-sac | May 21, 2019 | Dec 8, 2020 | Dec 8, 2020 | 2054d ago | 10.0.18362 | — | EOL | |
| 2019 LTS | Nov 13, 2018 | Jan 9, 2024 | Jan 9, 2029 | in 900d | 10.0.17763 | — | Active | |
| 1809-sac | Nov 13, 2018 | Nov 10, 2020 | Nov 10, 2020 | 2082d ago | 10.0.17763 | — | EOL | |
| 1803-sac | Apr 30, 2018 | Nov 12, 2019 | Nov 12, 2019 | 2446d ago | 10.0.17134 | — | EOL | |
| 1709-sac | Oct 17, 2017 | Apr 9, 2019 | Apr 9, 2019 | 2663d ago | 10.0.16299 | — | EOL | |
| 2016 LTS | Oct 15, 2016 | Jan 11, 2022 | Jan 12, 2027 | in 172d | 10.0.14393 | — | Active | |
| 2012-r2 LTS | Nov 25, 2013 | Oct 9, 2018 | Oct 10, 2023 | 1018d ago | 6.3.9600 | — | EOL | |
| 2012 LTS | Oct 30, 2012 | Oct 9, 2018 | Oct 10, 2023 | 1018d ago | 6.2.9200 | — | EOL | |
| 2008-r2-sp1 LTS | Feb 22, 2011 | Jan 13, 2015 | Jan 14, 2020 | 2383d ago | 6.1.7601 | — | EOL | |
| 2008-sp2 LTS | Apr 29, 2009 | Jan 13, 2015 | Jan 14, 2020 | 2383d ago | 6.0.6003 | — | EOL | |
| 2003-sp2 LTS | Mar 13, 2007 | Jul 13, 2010 | Jul 14, 2015 | 4028d ago | 5.2.3790 | — | EOL | |
| 2003-sp1 | Mar 30, 2005 | Apr 14, 2009 | Apr 14, 2009 | 6310d ago | 5.2.3790 | — | EOL | |
| 2003 LTS | Apr 24, 2003 | Apr 10, 2007 | Apr 10, 2007 | 7045d ago | 5.2.3790 | — | EOL | |
| 2000 LTS | Feb 17, 2000 | Jun 30, 2005 | Jul 13, 2010 | 5855d ago | 5.0.2195 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
