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: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 2025 LTS | Nov 1, 2024 | Oct 9, 2029 | Oct 10, 2034 | in 3000d | 10.0.26100 | — | Active | |
| 2022 LTS | Aug 18, 2021 | Oct 13, 2026 | Oct 14, 2031 | in 1908d | 10.0.20348 | — | Active | |
| 20h2 | Oct 20, 2020 | Aug 9, 2022 | Aug 9, 2022 | 1445d ago | 10.0.19042 | — | EOL | |
| 2004 | May 27, 2020 | Dec 14, 2021 | Dec 14, 2021 | 1683d ago | 10.0.19041 | — | EOL | |
| 1909 | Nov 12, 2019 | May 11, 2021 | May 11, 2021 | 1900d ago | 10.0.18363 | — | EOL | |
| 1903 | May 21, 2019 | Dec 8, 2020 | Dec 8, 2020 | 2054d ago | 10.0.18362 | — | EOL | |
| 1809 | Nov 13, 2018 | Nov 10, 2020 | Nov 10, 2020 | 2082d ago | 10.0.17763 | — | EOL | |
| 2019 LTS | Nov 13, 2018 | Jan 9, 2024 | Jan 9, 2029 | in 900d | 10.0.17763 | — | Active | |
| 1803 | Apr 30, 2018 | Nov 12, 2019 | Nov 12, 2019 | 2446d ago | 10.0.17134 | — | EOL | |
| 1709 | Oct 17, 2017 | Apr 9, 2019 | Apr 9, 2019 | 2663d ago | 10.0.16299 | — | EOL | |
| 1607 | Oct 15, 2016 | Jan 11, 2022 | Jan 11, 2022 | 1655d ago | 10.0.14393 | — | 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 |
Data sourced from endoflife.date · CVE data from NVD
