powershell end of life dates — full support timeline
7 of 10 tracked powershell releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 7.6 LTS | 2026-03-18 | 2028-11-14 | 7.6.4 | supported |
| 7.5 | 2025-01-23 | 2026-11-10 | 7.5.9 | ends soon |
| 7.4 LTS | 2023-11-16 | 2026-11-10 | 7.4.18 | ends soon |
| 7.3 | 2022-11-09 | 2024-05-08 | 7.3.12 | ended |
| 7.2 LTS | 2021-11-08 | 2024-11-08 | 7.2.24 | ended |
| 7.1 | 2020-11-11 | 2022-05-08 | 7.1.7 | ended |
| 7.0 LTS | 2020-03-04 | 2022-12-03 | 7.0.13 | ended |
| 6.2 | 2019-03-29 | 2020-09-04 | 6.2.7 | ended |
| 6.1 | 2018-09-13 | 2019-09-28 | 6.1.6 | ended |
| 6.0 | 2018-01-20 | 2019-02-13 | 6.0.5 | ended |
Who is affected
Anyone running an unsupported powershell release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/powershell, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next powershell deadline
You are reading this because a powershell release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every powershell and related deadline as it is announced, with exact dates and primary sources.
Watch powershell deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.