The Next Release of PowerShell – PowerShell 7

Steve Lee

Recently, the PowerShell Team shipped the Generally Available (GA) release of PowerShell Core 6.2. Since that release, we’ve already begun work on the next iteration!

We’re calling the next release PowerShell 7, the reasons for which will be explained in this blog post.

Why 7 and not 6.3?

PowerShell Core usage has grown significantly in the last two years. In particular, the bulk of our growth has come from Linux usage, an encouraging statistic given our investment in making PowerShell viable cross-platform.  This chart represents the number of times pwsh.exe (or just pwsh on Linux/macOS) was started (unless telemetry was disabled).


However, we also can clearly see that our Windows usage has not been growing as significantly, surprising given that PowerShell was popularized on the Windows platform. We believe that this could be occurring because existing Windows PowerShell users have existing automation that is incompatible with PowerShell Core because of unsupported modules, assemblies, and APIs. These folks are unable to take advantage of PowerShell Core’s new features, increased performance, and bug fixes. To address this, we are renewing our efforts towards a full replacement of Windows PowerShell 5.1 with our next release.

This means that Windows PowerShell and PowerShell Core users will be able to use the same version of PowerShell to automate across Windows, Linux, and macOS and on Windows, and PowerShell 7 users will have a very high level of compatibility with Windows PowerShell modules they rely on today.

We’re also going to take the opportunity to simplify our references to PowerShell in documentation and product pages, dropping the “Core” in “PowerShell 7”. The PSEdition will still reflect Core, but this will only be a technical distinction in APIs and documentation where appropriate.

Note that the major version does not imply that we will be making significant breaking changes. While we took the opportunity to make some breaking changes in 6.0, many of those were compromises to ensure our compatibility on non-Windows platforms. Prior to that, Windows PowerShell historically updated its major version based on new versions of Windows rather than Semantic Versioning

.NET Core 3.0

PowerShell Core 6.1 brought compatibility with many built-in Windows PowerShell modules, and our estimation is that PowerShell 7 can attain compatibility with 90+% of the inbox Windows PowerShell modules by leveraging changes in .NET Core 3.0 that bring back many APIs required by modules built on .NET Framework so that they work with .NET Core runtime. For example, we expect Out-GridView to come back (for Windows only, though)!

A significant effort for PowerShell 7 is porting the PowerShell Core 6 code base to .NET Core 3.0 and also working with Windows partner teams to validate their modules against PowerShell 7.

Support Lifecycle Changes

Currently, PowerShell Core is under the Microsoft Modern Lifecycle Policy. This means that PowerShell Core 6 is fix-forward: we produce servicing releases for security fixes and critical bug fixes, and you must install the latest stable version within 6 months of a new minor version release.

In PowerShell 7, we will align more closely with the .NET Core support lifecycle, enabling PowerShell 7 to have both LTS (Long Term Servicing) and non-LTS releases.

We will still have monthly Preview releases to get feedback early.

When do I get PowerShell 7?

The first Preview release of PowerShell 7 will likely be in May. Be aware, however, that this depends on completing integration and validation of PowerShell with .NET Core 3.0.

Since PowerShell 7 is aligned with the .NET Core timeline, we expect the generally available (GA) release to be some time after the GA of .NET Core 3.0.

What about shipping in Windows?

We are planning on eventually shipping PowerShell 7 in Windows as a side-by-side feature with Windows PowerShell 5.1, but we still need to work out some of the details on how you will manage this inbox version of PowerShell 7.

And since the .NET Core timeline doesn’t align with the Windows timeline, we can’t say right now when it will show up in a future version of Windows 10 or Windows Server.

What other features will be in PowerShell 7?

We haven’t closed on our feature planning yet, but expect another blog post relatively soon with a roadmap of our current feature level plans for PowerShell 7.

Steve Lee Principal Engineering Manager PowerShell Team


Discussion is closed. Login to edit/delete existing comments.

  • Nico Grüner 0

    @Steve Lee,

    you have written:
    “This means that Windows PowerShell and PowerShell Core users will be able to use the same version of PowerShell to automate across Windows, Linux, and macOS and on Windows, and PowerShell 7 users will have a very high level of compatibility with Windows PowerShell modules they rely on today.”

    But that is not true! Powershell Core is not compatible with Powershell 5.1 or earlier even in basic functionality, and you and the dev team know this.
    You are not willing to be fully compatible and and for Microsoft, Linux users now count more than their own Windows users, who have been using Powershell for a long time.

    A very good example is a basic functionallity for file Encoding. Since PowerShell 3.0 (!!!!!) the Parameter -Encoding has a value called “Default”. Since PowerShell 3.0, this value “Default” will encode the file based on the os Settings ansi Code page.
    With PowerShell core this was changed, now the value “Default” encodes all the time in UTF8.

    I have open a issue for this Problem in the git repo of PowerShell Core, you can finde the link below.

    There you can see that the Linux useres are more importend for Microsoft and his PowerShell Core than the own useres, what comes from Windows.
    Microsoft is not willing to change this mistake back to the functionality like it was in PowerShell 5.1.
    Tha means that for this example non of the scripts what Yous the parameter “-Encoding” with the value “default” want work well in PowerShell core.
    The generated Output file will be all the time in the wrong Encoding. If a file like this hannded over to a 3 Party app, all the datas in the 3. Party app will be wrong as well because of a wrong Encoding of PowerShell Core and Microfot how is not willing to fix this issue.

    Now I’m curious if my comment is deleted because he is too critical. In any case, I have already taken screenshots 😉

    • Micah R 0

      Your issue is that ANSI is not default anymore and that’s a good thing. UTF-8 can encode all Unicode characters and is thus multi-lingual. ANSI cannot. This is not about Linux vs Windows, it’s about making PowerShell work for everyone around the world.

Feedback usabilla icon