EOL.Wiki EOL.Wiki
← ← Back to all products

PowerShell

Active
Runtimes & JDKs Latest Version: 7.6.0 Latest Release: Mar 18, 2026

PowerShell is a cross-platform task automation framework by Microsoft with a command-line shell and scripting language.

Versions

10

Latest Version

7.6.0

Active Support

3

EOL

7

Lifecycle Timeline

Today
7.6
7.6
7.5
7.5
7.4
7.4
7.3
7.3
7.2
7.2
7.1
7.1
7.0
7.0
6.2
6.2
6.1
6.1
6.0
6.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
7.6Mar 18, 2026-Nov 14, 20287.6.0
Yes
Active
7.5Jan 23, 2025-Nov 10, 20267.5.5No
Active
7.4Nov 16, 2023-Nov 10, 20267.4.14
Yes
Active
7.3Nov 9, 2022-May 8, 20247.3.12No
EOL
7.2Nov 8, 2021-Nov 8, 20247.2.24
Yes
EOL
7.1Nov 11, 2020-May 8, 20227.1.7No
EOL
7.0Mar 4, 2020-Dec 3, 20227.0.13
Yes
EOL
6.2Mar 29, 2019-Sep 4, 20206.2.7No
EOL
6.1Sep 13, 2018-Sep 28, 20196.1.6No
EOL
6.0Jan 20, 2018-Feb 13, 20196.0.5No
EOL

Frequently Asked Questions

Which versions of PowerShell have reached end of life?
The following PowerShell versions have reached end of life and no longer receive security updates: 7.3, 7.2, 7.1, 7.0, 6.2, 6.1, 6.0. It is recommended to upgrade to a supported version.
Is it safe to continue using PowerShell 7.3?
PowerShell 7.3 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 PowerShell?
The latest version of PowerShell is 7.6.0, released in the 7.6 release cycle.
How many versions of PowerShell are currently supported?
PowerShell currently has 3 actively supported version(s): 7.6, 7.5, 7.4.
When does PowerShell 7.6 reach end of life?
PowerShell 7.6 is scheduled to reach end of life on Nov 14, 2028.
What should I do when PowerShell reaches end of life?
When a 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.