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: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
2025 LTSNov 1, 2024Nov 13, 2029Nov 14, 2034in 2944d10.0.26100—Active
23h2-ac Oct 24, 2023May 12, 2026May 12, 2026164d ago10.0.25398—EOL
2022 LTSAug 18, 2021Oct 13, 2026Oct 14, 2031in 1817d10.0.20348—Active
20h2-sac Oct 20, 2020Aug 9, 2022Aug 9, 20221536d ago10.0.19042—EOL
2004-sac May 27, 2020Dec 14, 2021Dec 14, 20211774d ago10.0.19041—EOL
1909-sac Nov 12, 2019May 11, 2021May 11, 20211991d ago10.0.18363—EOL
1903-sac May 21, 2019Dec 8, 2020Dec 8, 20202145d ago10.0.18362—EOL
2019 LTSNov 13, 2018Jan 9, 2024Jan 9, 2029in 809d10.0.17763—Active
1809-sac Nov 13, 2018Nov 10, 2020Nov 10, 20202173d ago10.0.17763—EOL
1803-sac Apr 30, 2018Nov 12, 2019Nov 12, 20192537d ago10.0.17134—EOL
1709-sac Oct 17, 2017Apr 9, 2019Apr 9, 20192754d ago10.0.16299—EOL
2016 LTSOct 15, 2016Jan 11, 2022Jan 12, 2027in 81d10.0.14393—EOL soon
2012-r2 LTSNov 25, 2013Oct 9, 2018Oct 10, 20231109d ago6.3.9600—EOL
2012 LTSOct 30, 2012Oct 9, 2018Oct 10, 20231109d ago6.2.9200—EOL
2008-r2-sp1 LTSFeb 22, 2011Jan 13, 2015Jan 14, 20202474d ago6.1.7601—EOL
2008-sp2 LTSApr 29, 2009Jan 13, 2015Jan 14, 20202474d ago6.0.6003—EOL
2003-sp2 LTSMar 13, 2007Jul 13, 2010Jul 14, 20154119d ago5.2.3790—EOL
2003-sp1 Mar 30, 2005Apr 14, 2009Apr 14, 20096401d ago5.2.3790—EOL
2003 LTSApr 24, 2003Apr 10, 2007Apr 10, 20077136d ago5.2.3790—EOL
2000 LTSFeb 17, 2000Jun 30, 2005Jul 13, 20105946d ago5.0.2195—EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions