PowerShell Core Support Lifecycle
PowerShell Core is a distinct set of tools and components that is shipped, installed, and configured separately from Windows PowerShell. So, PowerShell Core is not included in the Windows 7/8.1/10 or Windows Server licensing agreements.
However, PowerShell Core is supported under traditional Microsoft support agreements, including Premier, Microsoft Enterprise Agreements, and Microsoft Software Assurance. You can also pay for assisted support for PowerShell Core by filing a support request for your problem.
We also offer community support on GitHub where you can file an issue, bug, or feature request. Also, you may find help from other members of the community on the general Microsoft Community or the Microsoft PowerShell Tech Community. We offer no guarantee there that the community will address or resolve your issue in a timely manner. If you have a problem that requires immediate attention, you should use the traditional, paid support options.
Lifecycle of PowerShell Core
PowerShell Core is adopting the Microsoft Modern Lifecycle Policy. This support lifecycle is intended to keep customers up-to-date with the latest versions.
The version 6.x branch of PowerShell Core will be updated approximately once every six months (examples: 6.0, 6.1, 6.2, etc.)
You must update within six months after each new minor version release to continue receiving support.
For example, if PowerShell Core 6.1 is released on July 1, 2018, you would be expected to update to PowerShell Core 6.1 by January 1, 2019 to maintain support.
The Modern Lifecycle Policy also requires that Microsoft give customers 12 months notice before discontinuing support for a product (that is, PowerShell Core).
Eventually, we expect PowerShell Core will adopt the "long-term servicing" approach. In this servicing approach, we would require only servicing and security updates to stay in support on a specific branch/version of 6.x.
The following table to see what platform the version of PowerShell Core you are using is officially supported.
Our community has also contributed packages for some platforms,
but they are not officially supported.
These packages are marked as
Community in the table.
Platforms listed as
Experimental are not officially supported, but are available
for experimentation and feedback.
|Windows 7, 8.1, and 10||Supported||Supported|
|Windows Server 2008 R2, 2012 R2, 2016||Supported||Supported|
|Windows Server Semi-Annual Channel||Supported||Supported|
|Ubuntu 14.04 and, 16.04||Supported||Supported|
|Ubuntu 18.10 (via Snap Package)||Community|
|Red Hat Enterprise Linux 7||Supported||Supported|
|AppImage (works on multiple Linux platforms)||Community||Community|
|Snap Package||See note||See note|
Snap packages will be experimental for a period. After, we are confident that Snap does not introduce new support issues, the support will follow the distribution you are running the package on.
PowerShell release end of life
Based on Lifecycle of PowerShell Core, the following table lists the dates when various release will no longer be supported.
|Version||End Of Life|
|6.0||February 13, 2019|
|6.1||6 Months after 6.2 releases|
Platforms, which are out of support
When a platform version reaches end-of-life as defined by the platform owner, PowerShell Core will also cease to support that platform version. Previously released packages will remain available for customers needing access but formal support and updates of any kind will no longer be provided.
So, the distribution owners ended support for the following versions and are not supported.
|OS||Version||End of Life|
Notes on licensing
PowerShell Core is released under the MIT license. Under this license, and without a paid support agreement, users are limited to community support. With community support, Microsoft makes no guarantees of responsiveness or fixes.
Windows PowerShell Module
Support for PowerShell Core does not include product modules, unless those modules explicitly
support PowerShell Core.
ActiveDirectory module that ships as part of Windows Server is an unsupported scenario.
However, modules that do not explicitly support PowerShell Core may be compatible in some cases.
By installing the
you can add the Windows PowerShell
PSModulePath to your PowerShell Core
First, install the
WindowsPSModulePath module from the PowerShell Gallery:
# Add `-Scope CurrentUser` if you're installing as non-admin Install-Module WindowsPSModulePath -Force
After installing this module, run the
Add-WindowsPSModulePath cmdlet to add the Windows PowerShell
PSModulePath to PowerShell Core:
# Add this line to your profile if you always want Windows PowerShell PSModulePath Add-WindowsPSModulePath
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.