Microsoft recently announced that PowerShell 7 is imminent.
In a blog post, the company details why there will be such a large leap in version numbering, going from 6.2 to 7.0 in the next revision. Additionally, it appears that PowerShell for Windows usage has stalled while it’s being utilized more for non-Microsoft platforms such as Mac and Linux.
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.
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.