windows powershell end of life dates — full support timeline
5 of 6 tracked windows 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 |
|---|---|---|---|---|
| 5.1 | 2016-08-02 | not announced | — | supported |
| 5.0 | 2016-02-24 | 2016-08-02 | — | ended |
| 4.0 | 2013-10-01 | 2023-10-10 | — | ended |
| 3.0 | 2012-10-01 | 2023-10-10 | — | ended |
| 2.0 | 2009-07-01 | 2020-01-14 | — | ended |
| 1.0 | 2006-11-14 | 2020-01-14 | — | ended |
Who is affected
Anyone running an unsupported windows 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/windows-powershell, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next windows powershell deadline
You are reading this because a windows 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 windows powershell and related deadline as it is announced, with exact dates and primary sources.
Watch windows powershell deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.