Windows End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Windows versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| XP SP3 | 5.1.2600 | Apr 21, 2008 | Apr 8, 2014 | — | 4506 days past EOL | EOL |
| Vista SP2 | 6.0.6200 | Apr 29, 2009 | Apr 11, 2017 | — | 3407 days past EOL | EOL |
| 7 SP1 | 6.1.7601 | Feb 22, 2011 | Jan 14, 2020 | — | 2399 days past EOL | EOL |
| 8 | 6.2.9200 | Oct 30, 2012 | Jan 12, 2016 | — | 3862 days past EOL | EOL |
| 8.1 | 6.3.9600 | Nov 13, 2013 | Jan 10, 2023 | — | 1307 days past EOL | EOL |
| 10 1507 IOT | 10.0.10240 | Apr 29, 2015 | Nov 10, 2020 | — | 2098 days past EOL | EOL |
| 10 1507 | 10.0.10240 | Jul 29, 2015 | May 9, 2017 | — | 3379 days past EOL | EOL |
| 10 1507 (E) LTS | 10.0.10240 | Jul 29, 2015 | Oct 14, 2025 | — | 299 days past EOL | EOL |
| 10 1511 | 10.0.10586 | Nov 10, 2015 | Oct 10, 2017 | — | 3225 days past EOL | EOL |
| 10 1607 (W) | 10.0.14393 | Aug 2, 2016 | Apr 10, 2018 | — | 3043 days past EOL | EOL |
| 10 1607 (E) | 10.0.14393 | Aug 2, 2016 | Apr 9, 2019 | — | 2679 days past EOL | EOL |
| 10 1607 (E) LTS | 10.0.14393 | Aug 2, 2016 | Oct 13, 2026 | — | 65 days remaining | Warning |
| 10 1703 (W) | 10.0.15063 | Apr 11, 2017 | Oct 9, 2018 | — | 2861 days past EOL | EOL |
| 10 1703 (E) | 10.0.15063 | Apr 11, 2017 | Oct 8, 2019 | — | 2497 days past EOL | EOL |
| 10 1709 (W) | 10.0.16299 | Oct 17, 2017 | Apr 9, 2019 | — | 2679 days past EOL | EOL |
| 10 1709 (E) | 10.0.16299 | Oct 17, 2017 | Oct 13, 2020 | — | 2126 days past EOL | EOL |
| 10 1803 (W) | 10.0.17134 | Apr 30, 2018 | Nov 12, 2019 | — | 2462 days past EOL | EOL |
| 10 1803 (E) | 10.0.17134 | Apr 30, 2018 | May 11, 2021 | — | 1916 days past EOL | EOL |
| 10 1809 (W) | 10.0.17763 | Nov 13, 2018 | Nov 10, 2020 | — | 2098 days past EOL | EOL |
| 10 1809 (E) | 10.0.17763 | Nov 13, 2018 | May 11, 2021 | — | 1916 days past EOL | EOL |
| 10 1809 (E) LTS | 10.0.17763 | Nov 13, 2018 | Jan 9, 2029 | — | 884 days remaining | Active |
| 10 1903 | 10.0.18362 | May 21, 2019 | Dec 8, 2020 | — | 2070 days past EOL | EOL |
| 10 1909 (W) | 10.0.18363 | Nov 12, 2019 | May 11, 2021 | — | 1916 days past EOL | EOL |
| 10 1909 (E) | 10.0.18363 | Nov 12, 2019 | May 10, 2022 | — | 1552 days past EOL | EOL |
| 10 2004 | 10.0.19041 | May 27, 2020 | Dec 14, 2021 | — | 1699 days past EOL | EOL |
| 10 20H2 (W) | 10.0.19042 | Oct 20, 2020 | May 10, 2022 | — | 1552 days past EOL | EOL |
| 10 20H2 (E) | 10.0.19042 | Oct 20, 2020 | May 9, 2023 | — | 1188 days past EOL | EOL |
| 10 21H1 | 10.0.19043 | May 18, 2021 | Dec 13, 2022 | — | 1335 days past EOL | EOL |
| 11 21H2 (W) | 10.0.22000 | Oct 4, 2021 | Oct 10, 2023 | — | 1034 days past EOL | EOL |
| 11 21H2 (E) | 10.0.22000 | Oct 4, 2021 | Oct 8, 2024 | — | 670 days past EOL | EOL |
| 10 21H2 (W) | 10.0.19044 | Nov 16, 2021 | Jun 13, 2023 | — | 1153 days past EOL | EOL |
| 10 21H2 (E) | 10.0.19044 | Nov 16, 2021 | Jun 11, 2024 | — | 789 days past EOL | EOL |
| 10 21H2 (E) LTS | 10.0.19044 | Nov 16, 2021 | Jan 12, 2027 | — | 156 days remaining | Warning |
| 10 21H2 IoT LTS | 10.0.19044 | Nov 16, 2021 | Jan 13, 2032 | — | 1983 days remaining | Active |
| 11 22H2 (W) | 10.0.22621 | Sep 20, 2022 | Oct 8, 2024 | — | 670 days past EOL | EOL |
| 11 22H2 (E) | 10.0.22621 | Sep 20, 2022 | Oct 14, 2025 | — | 299 days past EOL | EOL |
| 10 22H2 | 10.0.19045 | Oct 18, 2022 | Oct 14, 2025 | Oct 10, 2028 Extended Security Updates (ESU) |
299 days past EOL | EOL |
| 11 23H2 (W) | 10.0.22631 | Oct 31, 2023 | Nov 11, 2025 | — | 271 days past EOL | EOL |
| 11 23H2 (E) | 10.0.22631 | Oct 31, 2023 | Nov 10, 2026 | — | 93 days remaining | Warning |
| 11 24H2 (W) | 10.0.26100 | Oct 1, 2024 | Oct 13, 2026 | — | 65 days remaining | Warning |
| 11 24H2 (E) | 10.0.26100 | Oct 1, 2024 | Oct 12, 2027 | — | 429 days remaining | Active |
| 11 24H2 (E) LTS | 10.0.26100 | Oct 1, 2024 | Oct 9, 2029 | — | 1157 days remaining | Active |
| 11 24H2 IoT LTS | 10.0.26100 | Oct 1, 2024 | Oct 10, 2034 | — | 2984 days remaining | Active |
| 11 25H2 (W) | 10.0.26200 | Sep 30, 2025 | Oct 12, 2027 | — | 429 days remaining | Active |
| 11 25H2 (E) | 10.0.26200 | Sep 30, 2025 | Oct 10, 2028 | — | 793 days remaining | Active |
| 11 26H1 (W) | 10.0.28000 | Feb 10, 2026 | Mar 14, 2028 | — | 583 days remaining | Active |
| 11 26H1 (E) | 10.0.28000 | Feb 10, 2026 | Mar 13, 2029 | — | 947 days remaining | Active |
[](https://endoflife.ai/windows)
Microsoft Extended Security Updates (ESU) Timeline
Microsoft's official lifecycle data lists the following Extended Security Update windows. ESU is a paid program that delivers critical security patches only, after a version's mainstream and extended support have already ended — it does not include new features, non-security fixes, or technical support.
| Product | ESU Phase | ESU End Date |
|---|---|---|
| Windows 7 | Extended Security Update Year 3* | Jan 11, 2023 |
| Windows 7 | Extended Security Update Year 2* | Jan 12, 2022 |
| Windows 7 | Extended Security Update Year 1* | Jan 13, 2021 |
Source: Microsoft Lifecycle — official Microsoft data, supplementary to endoflife.date.
What does Windows end of life mean for your organization?
When a version of Windows reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Windows should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Windows reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
For the full decision flow on this product, see our detailed guide: Windows 10: upgrade, buy ESU, or replace?
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Windows versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Windows has 34 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Windows exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.