Windows Server 2000 End of Life Date
Windows Server 2000 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
Windows Server 2000 was released on February 17, 2000 and support ended on July 13, 2010 — a supported lifespan of 10 years and 5 months, in line with the 10 years and 2 months median for Windows Server LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. It has been past its end-of-life date for 16 years and 4 months. 15 newer Windows Server releases have shipped since.
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| → 2000 LTS | 5.0.2195 | Jul 13, 2010 | EOL |
| Windows Server 2003 RTM LTS | 5.2.3790 | Apr 10, 2007 | EOL |
| Windows Server 2003 SP1 | 5.2.3790 | Apr 14, 2009 | EOL |
| Windows Server 2003 SP2 LTS | 5.2.3790 | Jul 14, 2015 | EOL |
| Windows Server 2008 SP2 LTS | 6.0.6003 | Jan 14, 2020 | EOL |
| Windows Server 2008 R2 SP1 LTS | 6.1.7601 | Jan 14, 2020 | EOL |
| 2012 LTS | 6.2.9200 | Oct 10, 2023 | EOL |
| Windows Server 2012 R2 LTS | 6.3.9600 | Oct 10, 2023 | EOL |
What does Windows Server 2000 end of life mean?
When Windows Server 2000 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Windows Server 2000 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Windows Server 2025 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.