← ← Back to all products
Microsoft Windows PowerShell
Active
Runtimes & JDKs Latest Version: 5.1 Latest Release: N/A
Windows PowerShell is a Windows-only automation framework, the predecessor to cross-platform PowerShell.
Versions
6
Latest Version
5.1
Active Support
1
EOL
5
Lifecycle Timeline
Today ↓
5.1
5.1
5.0
5.0
4.0
4.0
3.0
3.0
2.0
2.0
1.0
1.0
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 5.1 | Aug 2, 2016 | Yes | No | 5.1 | No | Active |
| 5.0 | Feb 24, 2016 | No | Aug 2, 2016 | 5.0 | No | EOL |
| 4.0 | Oct 1, 2013 | No | Oct 10, 2023 | 4.0 | No | EOL |
| 3.0 | Oct 1, 2012 | No | Oct 10, 2023 | 3.0 | No | EOL |
| 2.0 | Jul 1, 2009 | No | Jan 14, 2020 | 2.0 | No | EOL |
| 1.0 | Nov 14, 2006 | No | Jan 14, 2020 | 1.0 | No | EOL |
Frequently Asked Questions
Which versions of Microsoft Windows PowerShell have reached end of life?
The following Microsoft Windows PowerShell versions have reached end of life and no longer receive security updates: 5.0, 4.0, 3.0, 2.0, 1.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Microsoft Windows PowerShell 5.0?
Microsoft Windows PowerShell 5.0 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Microsoft Windows PowerShell?
The latest version of Microsoft Windows PowerShell is 5.1, released in the 5.1 release cycle.
How many versions of Microsoft Windows PowerShell are currently supported?
Microsoft Windows PowerShell currently has 1 actively supported version(s): 5.1.
When does Microsoft Windows PowerShell 5.1 reach end of life?
Microsoft Windows PowerShell 5.1 does not have a specific end-of-life date announced yet.
What should I do when Microsoft Windows PowerShell reaches end of life?
When a Microsoft Windows PowerShell version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.