PowerShell Core Support Lifecycle

PowerShell Core is a distinct set of tools and components that is shipped, installed, and configured separately from Windows PowerShell. Therefore, 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. Alternatively, 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 your issue will be addressed or resolved 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 (e.g. 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 1st, 2018, you would be expected to update to PowerShell Core 6.1 by January 1st, 2019 to maintain support.

PowerShell Core branch lifecycle

The Modern Lifecycle Policy also requires that Microsoft give customers 12 months notice before discontinuing support for a product (i.e. PowerShell Core).

Eventually, we expect PowerShell Core will adopt the "long-term servicing" approach where we would require only servicing and security updates to stay in support on a specific branch/version of 6.x.

Supported platforms

PowerShell Core is officially supported on the following platforms:

  • Windows 7, 8.1, and 10
  • Windows Server 2008 R2, 2012 R2, 2016
  • Windows Server Semi-Annual Channel
  • Ubuntu 14.04, 16.04, and 17.04
  • Debian 8.7+, and 9
  • CentOS 7
  • Red Hat Enterprise Linux 7
  • OpenSUSE 42.2
  • Fedora 27, 28
  • macOS 10.12+

Our community has also contributed packages for the following platforms, but they are not officially suppported:

  • Arch Linux
  • Kali Linux
  • AppImage (works on multiple Linux platforms)

Notes on licensing

PowerShell Core is released under the MIT license. Under this license, and in the absence of 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 extend to other product modules unless those modules explicitly support PowerShell Core. For example, using the 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 WindowsPSModulePath module, you can append the Windows PowerShell PSModulePath to your PowerShell Core PSModulePath.

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