11---
2- description : Details the policies governing support for PowerShell
3- ms.date : 05/08 /2024
2+ description : Details the policies governing support for PowerShell.
3+ ms.date : 05/09 /2024
44ms.topic : lifecycle
55title : PowerShell Support Lifecycle
66---
@@ -16,7 +16,7 @@ linked to [.NET and .NET Core Support Policy][06]. In this servicing approach, c
1616Long Term Support (LTS) releases or current releases.
1717
1818An ** LTS** release of PowerShell is built on an LTS release of .NET. Updates to an LTS release only
19- contain critical security updates and servicing fixes that are designed to minimize impact to
19+ contain critical security updates and servicing fixes that are designed to minimize impact on
2020existing workloads. LTS releases of PowerShell are supported until the end-of-support for .NET.
2121
2222A ** current** release is a release that occurs between LTS releases. Current releases can contain
@@ -30,18 +30,23 @@ the next release (current or LTS).
3030
3131## Supported platforms
3232
33- PowerShell runs on multiple operating systems (OS) and processor architectures. To be supported by
34- Microsoft, the OS must meet the following criteria:
33+ PowerShell runs on multiple operating systems (OS) and processor architectures. For support, the
34+ platform must meet the following criteria:
3535
36- - The version and processor architecture of the OS is supported by .NET Core .
37- - The version of the OS is supported for at least one year.
38- - The version of the OS isn't an interim release or equivalent.
39- - The version of the OS is currently supported by the OS publisher .
40- - The PowerShell team has tested the version of the distribution .
36+ - The target platform (OS version and processor architecture) is supported by .NET.
37+ - The OS version is supported by the distributor for at least one year.
38+ - The OS version isn't an interim release or equivalent.
39+ - The OS version is currently supported by the distributor .
40+ - Microsoft has tested and approved PowerShell on the target platform .
4141
42- When a platform version reaches end-of-life as defined by the platform owner, PowerShell also ends
43- support on that platform version. Previously released packages remain available for customers
44- needing access but formal support and updates of any kind are no longer be provided.
42+ Support for PowerShell ends when either of the following conditions are met:
43+
44+ - The target platform reaches end-of-life as defined by the platform owner
45+ - The specific version of PowerShell reaches end-of-life
46+
47+ After a version of PowerShell reaches end-of-life, no further updates, including security updates,
48+ are provided. Microsoft encourages customers to upgrade to a supported version of PowerShell to
49+ continue receiving updates and support.
4550
4651### Windows
4752
@@ -80,46 +85,39 @@ feedback on experimental features and we provide best-effort support for them.
8085
8186## Notes on licensing
8287
83- PowerShell is released under the [ MIT license] [ 10 ] . Under this license, and without a paid support
88+ PowerShell is released under the [ MIT license] [ 15 ] . Under this license, and without a paid support
8489agreement, users are limited to [ community support] [ 04 ] . With community support, Microsoft makes no
8590guarantees of responsiveness or fixes.
8691
8792## Getting support
8893
89- Support for PowerShell is delivered via traditional Microsoft support agreements, including
90- [ paid support] [ 12 ] , [ Microsoft Enterprise Agreements] [ 14 ] , and [ Microsoft Software Assurance] [ 15 ] .
91- You can also pay for [ assisted support] [ 11 ] for PowerShell by filing a support request for your
92- problem.
94+ Support for PowerShell is provided on a best-effort basis. Support for Windows PowerShell 5.1 is
95+ provided through Windows support channels. You can use the standard paid support channels to get
96+ support for PowerShell.
9397
94- There are multiple [ community support] [ 04 ] options. You can file an issue, bug, or feature request on
95- GitHub. Also, you can get help from other members of the community in the Microsoft
96- [ PowerShell Tech Community] [ 13 ] or any of the community forums listed on the [ PowerShell] [ 04 ] hub
97- page. If you have a problem that requires immediate attention, you should use the traditional, paid
98- support options.
98+ - [ Support for business] [ 18 ]
99+ - [ Contact support] [ 17 ]
99100
100- > [ !IMPORTANT]
101- > You must have the latest patch update installed to qualify for support. For example, if you're
102- > running PowerShell 7.3 and 7.3.1 has been released, you must update to 7.3.1 to qualify for
103- > support.
101+ There are many free support options available from the PowerShell community. The most active
102+ community support channels are available through ** Discord** or ** Slack** . The discussion channels
103+ are mirrored on both platforms, so you can choose the platform that you prefer. These channels can
104+ help you troubleshoot issues, answer questions, and provide guidance on how to use PowerShell.
105+
106+ If you think that you found a bug, you can file an issue on [ GitHub] [ 16 ] . The PowerShell team can't
107+ provide support through GitHub, but they welcome bug reports. The [ community support] [ 04 ] page
108+ provides links to the most popular community support channels.
104109
105- ## PowerShell End -of-support dates
110+ ## PowerShell end -of-support dates
106111
107- Based on these lifecycle policies, the following table lists the dates when support for the current
108- versions of PowerShell end :
112+ The PowerShell support lifecycle is tied to the [ support lifecycle of .NET ] [ 06 ] . The following table
113+ lists the end-of-support dates for the current versions of PowerShell:
109114
110115| Version | Release Date | End-of-support |
111116| ------------------ | ----------------- | ----------------- |
112117| 7.4 (LTS-current) | November 16, 2023 | November 10, 2026 |
113118| 7.2 (LTS-previous) | November 8, 2021 | November 8, 2024 |
114119
115- Support for PowerShell on a specific platform is based on the support policy of the version of .NET
116- used.
117-
118- - PowerShell 7.4 (LTS-current) is based on the [ .NET 8.0 Supported OS Lifecycle Policy] [ 09 ]
119- - PowerShell 7.3 (Stable) is based on the [ .NET 7.0 Supported OS Lifecycle Policy] [ 08 ]
120- - PowerShell 7.2 (LTS-previous) is based on the [ .NET 6.0 Supported OS Lifecycle Policy] [ 07 ]
121-
122- End of support dates for already retired versions were:
120+ The following table lists the end-of-support dates for retired versions of PowerShell:
123121
124122| Version | Release Date | End-of-support |
125123| --------- | ------------------ | ------------------ |
@@ -132,26 +130,25 @@ End of support dates for already retired versions were:
132130
133131## Release history
134132
135- The following table contains a timeline of the major releases of PowerShell. This table is provided
136- for historical reference. It isn't intended for use to determine the support lifecycle.
137-
138- | Version | Release Date | Note |
139- | ----------------------------- | :----------: | ------------------------------------------------------------------------------- |
140- | PowerShell 7.5 (preview) | TBA | Built on .NET 9.0.0-preview.1 |
141- | PowerShell 7.4 (LTS-current) | Nov-2023 | Built on .NET 8.0.0 |
142- | PowerShell 7.3 | Nov-2022 | Built on .NET 7.0 |
143- | PowerShell 7.2 (LTS-previous) | Nov-2021 | Built on .NET 6.0 (LTS-previous) |
144- | PowerShell 7.1 | Nov-2020 | Built on .NET 5.0 |
145- | PowerShell 7.0 (LTS) | Mar-2020 | Built on .NET Core 3.1 (LTS) |
146- | PowerShell 6.2 | Mar-2019 | Built on .NET Core 2.1 |
147- | PowerShell 6.1 | Sep-2018 | Built on .NET Core 2.1 |
148- | PowerShell 6.0 | Jan-2018 | First release, built on .NET Core 2.0. Installable on Windows, Linux, and macOS |
149- | Windows PowerShell 5.1 | Aug-2016 | Released in Windows 10 Anniversary Update and Windows Server 2016, WMF 5.1 |
150- | Windows PowerShell 5.0 | Feb-2016 | Released in Windows Management Framework (WMF) 5.0 |
151- | Windows PowerShell 4.0 | Oct-2013 | Integrated in Windows 8.1 and with Windows Server 2012 R2, WMF 4.0 |
152- | Windows PowerShell 3.0 | Oct-2012 | Integrated in Windows 8 and with Windows Server 2012 WMF 3.0 |
153- | Windows PowerShell 2.0 | Jul-2009 | Integrated in Windows 7 and Windows Server 2008 R2, WMF 2.0 |
154- | Windows PowerShell 1.0 | Nov-2006 | Optional component of Windows Server 2008 |
133+ The following table contains a historical timeline of the major releases of PowerShell.
134+
135+ | Version | Release Date | Note |
136+ | ----------------------------- | :----------: | -------------------------------------------------------------------------- |
137+ | PowerShell 7.5 (preview) | Future | Built on [ .NET 9.0.0] [ 14 ] |
138+ | PowerShell 7.4 (LTS-current) | Nov-2023 | Built on [ .NET 8.0.0] [ 13 ] |
139+ | PowerShell 7.3 | Nov-2022 | Built on [ .NET 7.0] [ 12 ] |
140+ | PowerShell 7.2 (LTS-previous) | Nov-2021 | Built on [ .NET 6.0] [ 11 ] |
141+ | PowerShell 7.1 | Nov-2020 | Built on [ .NET 5.0] [ 10 ] |
142+ | PowerShell 7.0 (LTS) | Mar-2020 | Built on [ .NET Core 3.1] [ 09 ] |
143+ | PowerShell 6.2 | Mar-2019 | Built on [ .NET Core 2.1] [ 08 ] |
144+ | PowerShell 6.1 | Sep-2018 | Built on [ .NET Core 2.1] [ 08 ] |
145+ | PowerShell 6.0 | Jan-2018 | Built on [ .NET Core 2.0] [ 07 ] . Installable on Windows, Linux, and macOS |
146+ | Windows PowerShell 5.1 | Aug-2016 | Released in Windows 10 Anniversary Update and Windows Server 2016, WMF 5.1 |
147+ | Windows PowerShell 5.0 | Feb-2016 | Released in Windows Management Framework (WMF) 5.0 |
148+ | Windows PowerShell 4.0 | Oct-2013 | Released in Windows 8.1 and with Windows Server 2012 R2, WMF 4.0 |
149+ | Windows PowerShell 3.0 | Oct-2012 | Released in Windows 8 and with Windows Server 2012 WMF 3.0 |
150+ | Windows PowerShell 2.0 | Jul-2009 | Released in Windows 7 and Windows Server 2008 R2, WMF 2.0 |
151+ | Windows PowerShell 1.0 | Nov-2006 | Released as optional component of Windows Server 2008 |
155152
156153Run the following command to see the full version number of .NET used by the version of PowerShell
157154you're running:
@@ -167,12 +164,15 @@ you're running:
167164[ 04 ] : /powershell/scripting/community/community-support
168165[ 05 ] : /powershell/scripting/learn/experimental-features
169166[ 06 ] : https://dotnet.microsoft.com/platform/support/policy/dotnet-core
170- [ 07 ] : https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md
171- [ 08 ] : https://github.com/dotnet/core/blob/main/release-notes/7.0/supported-os.md
172- [ 09 ] : https://github.com/dotnet/core/blob/main/release-notes/8.0/supported-os.md
173- [ 10 ] : https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt
174- [ 11 ] : https://support.microsoft.com/supportforbusiness/productselection
175- [ 12 ] : https://support.serviceshub.microsoft.com/supportforbusiness
176- [ 13 ] : https://techcommunity.microsoft.com/t5/PowerShell/ct-p/WindowsPowerShell
177- [ 14 ] : https://www.microsoft.com/licensing/licensing-programs/enterprise
178- [ 15 ] : https://www.microsoft.com/licensing/licensing-programs/software-assurance-default
167+ [ 07 ] : https://github.com/dotnet/core/blob/main/release-notes/2.0/2.0-supported-os.md
168+ [ 08 ] : https://github.com/dotnet/core/blob/main/release-notes/2.1/2.1-supported-os.md
169+ [ 09 ] : https://github.com/dotnet/core/blob/main/release-notes/3.1/3.1-supported-os.md
170+ [ 10 ] : https://github.com/dotnet/core/blob/main/release-notes/5.0/5.0-supported-os.md
171+ [ 11 ] : https://github.com/dotnet/core/blob/main/release-notes/6.0/supported-os.md
172+ [ 12 ] : https://github.com/dotnet/core/blob/main/release-notes/7.0/supported-os.md
173+ [ 13 ] : https://github.com/dotnet/core/blob/main/release-notes/8.0/supported-os.md
174+ [ 14 ] : https://github.com/dotnet/core/blob/main/release-notes/9.0/supported-os.md
175+ [ 15 ] : https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt
176+ [ 16 ] : https://github.com/PowerShell/PowerShell/issues/new/choose
177+ [ 17 ] : https://support.microsoft.com/contactus
178+ [ 18 ] : https://support.serviceshub.microsoft.com/
0 commit comments