Windows Server Core End of Life Dates

other

Developers rely on Windows Server Core to provide a streamlined and secure foundation for their infrastructure, and for good reason. Created to address the need for a more efficient and less vulnerable server operating system, Windows Server Core has been a staple in the development community since its introduction. Maintained by Microsoft, this product has undergone significant updates and improvements over the years, with the latest stable version being 10.0.26100. By tracking the end-of-life dates and supported versions of Windows Server Core, developers can plan their upgrades and ensure seamless continuity of their operations.

The end-of-life landscape for Windows Server Core is complex, with a total of 16 versions, 12 of which have already reached the end of their support lifecycle. Currently, there are 4 active versions, and the next version to expire is 2016, which will reach its end-of-life on 2027-01-12. This gives developers a clear timeline to plan their migration to a more recent version. The most recent end-of-life date was 2023-10-10, when version 2012 ceased to receive support. By staying informed about these timelines, developers can avoid potential security risks and compatibility issues associated with outdated software.

From a security standpoint, Windows Server Core has a remarkably clean track record, with 0 CVEs tracked and 0 critical vulnerabilities reported. As a result, there is no most affected version, and no Known Exploited Vulnerability status has been assigned. While this is certainly good news, it does not mean that developers can become complacent. To ensure the continued security and integrity of their systems, developers should still prioritize regular updates and migrations to the latest supported versions of Windows Server Core, taking advantage of the latest security patches and features to protect their infrastructure from potential threats.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
2025 LTSNov 1, 2024Oct 9, 2029Oct 10, 2034in 2909d10.0.26100—Active
2022 LTSAug 18, 2021Oct 13, 2026Oct 14, 2031in 1817d10.0.20348—Active
20h2 Oct 20, 2020Aug 9, 2022Aug 9, 20221536d ago10.0.19042—EOL
2004 May 27, 2020Dec 14, 2021Dec 14, 20211774d ago10.0.19041—EOL
1909 Nov 12, 2019May 11, 2021May 11, 20211991d ago10.0.18363—EOL
1903 May 21, 2019Dec 8, 2020Dec 8, 20202145d ago10.0.18362—EOL
1809 Nov 13, 2018Nov 10, 2020Nov 10, 20202173d ago10.0.17763—EOL
2019 LTSNov 13, 2018Jan 9, 2024Jan 9, 2029in 809d10.0.17763—Active
1803 Apr 30, 2018Nov 12, 2019Nov 12, 20192537d ago10.0.17134—EOL
1709 Oct 17, 2017Apr 9, 2019Apr 9, 20192754d ago10.0.16299—EOL
1607 Oct 15, 2016Jan 11, 2022Jan 11, 20221746d ago10.0.14393—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

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions