Visual Studio End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Visual Studio 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 | Days | Status |
|---|---|---|---|---|---|
| 10.0 | Service Pack 1 | Jun 29, 2010 | Jul 14, 2020 | 2217 days past EOL | EOL |
| 11.0 | Update 4 | Oct 31, 2012 | Jan 10, 2023 | 1307 days past EOL | EOL |
| 12.0 | Update 5 | Jan 15, 2014 | Apr 9, 2024 | 852 days past EOL | EOL |
| 14.0 | Update 3 + KB3165756 | Jul 20, 2015 | Oct 14, 2025 | 299 days past EOL | EOL |
| 15.0 | 15.0.28 | Mar 7, 2017 | Jan 14, 2020 | 2399 days past EOL | EOL |
| 15.1 | 15.1.2 | Apr 5, 2017 | May 10, 2017 | 3378 days past EOL | EOL |
| 15.2 | 15.2.6 | May 10, 2017 | Aug 14, 2017 | 3282 days past EOL | EOL |
| 15.3 | 15.3.5 | Aug 14, 2017 | Oct 9, 2017 | 3226 days past EOL | EOL |
| 15.4 | 15.4.5 | Oct 9, 2017 | Dec 4, 2017 | 3170 days past EOL | EOL |
| 15.5 | 15.5.7 | Dec 4, 2017 | Mar 5, 2018 | 3079 days past EOL | EOL |
| 15.6 | 15.6.7 | Mar 5, 2018 | May 7, 2018 | 3016 days past EOL | EOL |
| 15.7 | 15.7.6 | May 7, 2018 | Aug 14, 2018 | 2917 days past EOL | EOL |
| 15.8 | 15.8.9 | Aug 14, 2018 | Nov 13, 2018 | 2826 days past EOL | EOL |
| 15.9 | 15.9.81 | Nov 13, 2018 | Apr 13, 2027 | 247 days remaining | Active |
| 16.0 | 16.0.22 | Apr 2, 2019 | Jan 12, 2021 | 2035 days past EOL | EOL |
| 16.1 | 16.1.6 | May 21, 2019 | Jul 24, 2019 | 2573 days past EOL | EOL |
| 16.2 | 16.2.5 | Jul 24, 2019 | Sep 23, 2019 | 2512 days past EOL | EOL |
| 16.3 | 16.3.10 | Sep 23, 2019 | Dec 3, 2019 | 2441 days past EOL | EOL |
| 16.4 | 16.4.27 | Dec 3, 2019 | Oct 12, 2021 | 1762 days past EOL | EOL |
| 16.5 | 16.5.5 | Mar 16, 2020 | May 19, 2020 | 2273 days past EOL | EOL |
| 16.6 | 16.6.5 | May 19, 2020 | Aug 5, 2020 | 2195 days past EOL | EOL |
| 16.7 | 16.7.28 | Aug 5, 2020 | Apr 12, 2022 | 1580 days past EOL | EOL |
| 16.8 | 16.8.7 | Nov 10, 2020 | Mar 9, 2021 | 1979 days past EOL | EOL |
| 16.9 | 16.9.26 | Mar 2, 2021 | Oct 11, 2022 | 1398 days past EOL | EOL |
| 16.10 | 16.10.4 | May 25, 2021 | Aug 10, 2021 | 1825 days past EOL | EOL |
| 16.11 | 16.11.58 | Aug 10, 2021 | Apr 10, 2029 | 975 days remaining | Active |
| 17.0 LTS | 17.0.23 | Nov 8, 2021 | Jul 11, 2023 | 1125 days past EOL | EOL |
| 17.1 | 17.1.7 | Feb 15, 2022 | May 10, 2022 | 1552 days past EOL | EOL |
| 17.2 LTS | 17.2.23 | May 10, 2022 | Jan 9, 2024 | 943 days past EOL | EOL |
| 17.3 | 17.3.7 | Aug 9, 2022 | Nov 8, 2022 | 1370 days past EOL | EOL |
| 17.4 LTS | 17.4.21 | Nov 8, 2022 | Jul 9, 2024 | 761 days past EOL | EOL |
| 17.5 | 17.5.5 | Feb 21, 2023 | May 16, 2023 | 1181 days past EOL | EOL |
| 17.6 LTS | 17.6.22 | May 16, 2023 | Jan 14, 2025 | 572 days past EOL | EOL |
| 17.7 | 17.7.7 | Aug 8, 2023 | Nov 14, 2023 | 999 days past EOL | EOL |
| 17.8 LTS | 17.8.23 | Nov 14, 2023 | Jul 8, 2025 | 397 days past EOL | EOL |
| 17.9 | 17.9.7 | Feb 13, 2024 | May 21, 2024 | 810 days past EOL | EOL |
| 17.10 LTS | 17.10.21 | May 21, 2024 | Jan 13, 2026 | 208 days past EOL | EOL |
| 17.11 | 17.11.6 | Aug 13, 2024 | Nov 12, 2024 | 635 days past EOL | EOL |
| 17.12 LTS | 17.12.22 | Nov 12, 2024 | Jul 14, 2026 | 26 days past EOL | EOL |
| 17.13 | 17.13.7 | Feb 11, 2025 | May 13, 2025 | 453 days past EOL | EOL |
| 17.14 LTS | 17.14.36 | May 13, 2025 | Jan 13, 2032 | 1983 days remaining | Active |
| 18.0 | 18.0.2 | Nov 11, 2025 | Dec 9, 2025 | 243 days past EOL | EOL |
| 18.1 | 18.1.1 | Dec 9, 2025 | Jan 13, 2026 | 208 days past EOL | EOL |
| 18.2 | 18.2.2 | Jan 13, 2026 | Feb 10, 2026 | 180 days past EOL | EOL |
| 18.3 | 18.3.3 | Feb 10, 2026 | Mar 10, 2026 | 152 days past EOL | EOL |
| 18.4 | 18.4.4 | Mar 10, 2026 | Apr 14, 2026 | 117 days past EOL | EOL |
| 18.5 | 18.5.3 | Apr 14, 2026 | May 12, 2026 | 89 days past EOL | EOL |
| 18.6 | 18.6.3 | May 12, 2026 | Jun 9, 2026 | 61 days past EOL | EOL |
| 18.7 | 18.7.4 | Jun 9, 2026 | Jul 14, 2026 | 26 days past EOL | EOL |
| 18.8 | 18.8.2 | Jul 14, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/visual-studio)
What does Visual Studio end of life mean for your organization?
When a version of Visual Studio 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 Visual Studio 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 Visual Studio 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Visual Studio versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Visual Studio has 46 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Visual Studio 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.