Windows Powershell 5.1 · Version Status
Windows Powershell 5.1 End of Life Date
Windows Powershell 5.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Windows Powershell 5.1 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
—
Standard release
Release Date
Aug 2, 2016
Windows Powershell 5.1 series
All Windows Powershell Versions
| Version | Latest | EOL Date | Status |
|---|
| 1.0 |
— |
Jan 14, 2020 |
EOL |
| 2.0 |
— |
Jan 14, 2020 |
EOL |
| 3.0 |
— |
Oct 10, 2023 |
EOL |
| 4.0 |
— |
Oct 10, 2023 |
EOL |
| 5.0 |
— |
Aug 2, 2016 |
EOL |
| → 5.1 |
— |
EOL |
Active |
What does Windows Powershell 5.1 end of life mean?
When Windows Powershell 5.1 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Windows Powershell 5.1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Windows Powershell 5.1 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Windows Powershell 5.1 reach end of life?
Windows Powershell 5.1 has already reached end of life.
Is Windows Powershell 5.1 still supported?
Yes, Windows Powershell 5.1 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Windows Powershell 5.1?
The recommended upgrade from Windows Powershell 5.1 is
Windows Powershell 5.1 — the latest actively supported version. Check the
Windows Powershell full timeline for all supported versions.
What are the security risks of running Windows Powershell 5.1 past EOL?
When Windows Powershell 5.1 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Windows Powershell should migrate immediately or implement compensating controls.