We have been waiting for news like this for quite some time now: PowerShell v7 will be included in Windows! In this blog post, I will highlight the roadmap and the inevitable deprecation of Windows PowerShell v5.

Why does this matter?
The Windows PowerShell v5 included today hasn’t received a new feature in over 10 years! PowerShell v7, unlike Windows PowerShell v5, is cross-platform, has received many upgrades, and is built on much newer, faster .NET Framework versions.
Why did it take so long?
PowerShell releases are tied to .NET Framework releases and their support lifecycle; to keep your servers supported and secure, you need a supported environment for both. (See PowerShell Support Lifecycle for more) The upcoming Windows Server 2028, now in public preview, will start with .NET 11 and PowerShell v7.7 (supported until November 2028), together with Windows 11 27H1, I guess?
The article from the PowerShell Team
Jason Helmick wrote an article on Microsoft’s DevBlogs site with details about the upcoming PowerShell v7 inclusion in Windows. (https://devblogs.microsoft.com/powershell/powershell-7-coming-to-windows/) Highlights are:
What happens to your scripts?
Nothing. PowerShell 7 is designed to be used side by side with Windows PowerShell 5.1. Your existing automation needs no changes. Windows PowerShell 5.1 continues to run your scripts, scheduled tasks, and services, and you move to PowerShell 7 when you’re ready.
What we’re still finishing
Windows PowerShell 5.1 earned its place as the trusted automation platform for Windows, and PowerShell 7 needs to earn its place too. PowerShell 7 is delivered as an MSIX package. MSIX still needs work to match some things that worked with the MSI installer. We’re working to close these gaps:
- Running as the SYSTEM account, which affects scheduled tasks, services, device-management scripts, and remoting
- Support for the DISM cmdlets, such as
Add-WindowsCapability. - Support for machine-wide settings, such as the all-users profile.
These changes are in progress now. We track the status of each in the MSIX tracking issue.
When you’re ready to move
Many scripts run in PowerShell 7 without changes. Some need changes before they work, and some may need to keep running in Windows PowerShell 5.1. That’s because Windows PowerShell 5.1 and PowerShell 7 differ in some places.
Test your scripts in PowerShell 7 before you move them. That’s how you find out which kind you have.
If a script of yours depends on one of those differences, we have documentation to help you decide what to do:
- Differences between Windows PowerShell 5.1 and PowerShell 7.x lists the differences
- Migrating from Windows PowerShell 5.1 to PowerShell 7 covers how the two run side by side, including modules, profiles, and remoting
Knowing which of your scripts, if any, need a change is the harder job, especially across many machines. To help you with that, we are investing in community-built tools, documentation, and improvements to PSScriptAnalyzer’s compatibility checks. Together they are meant to cover three things:
- Inventory: find what you have, including scheduled tasks and services.
- Analysis: flag what in your scripts needs attention before it runs in PowerShell 7.
- Guidance: for each finding, what to change and why.
We’ll share each piece, with documentation, as it’s ready.
Inbox Working Group
We’re starting an Inbox Working Group to triage issues that affect PowerShell 7 in Windows. The job of this group is to make sure that the issues you report reach the people who can act on them.
Run your scripts, tell us what you find
The best way to know how your scripts will do is to run them in PowerShell 7. We want your feedback. Follow our progress and describe your issues in our GitHub repository: PowerShell/PowerShell. We’re listening.
The PowerShell Team
Windows PowerShell v5.1 Deprecation
As mentioned above, it hasn’t received a new feature in 10 years. It will receive security updates, however, and scripts and tools that rely on it will continue to run. But it will be removed from future versions of Windows. Timeline for that is:
2026
Windows PowerShell v5.1 will be deprecated; Windows Server 2025 and Windows 11 26H2 are the last versions of Windows to include PowerShell 5.1 enabled by default.
Next versions of Windows
Windows PowerShell v5.1 will become available as a Feature On Demand, just like PowerShell v2.0 was for quite some time. Enabled by default on new Windows installs, but because it’s a Feature On Demand, you could deploy new servers without it. (That’s how I interpret that 🙂 )
Future Version of Windows
Not available anymore; you have completely moved over to PowerShell v7!
Actions
If you use Windows PowerShell 5.1 for administration or automation, we recommend that you start planning now.
- Find what uses Windows PowerShell 5.1. Look for scripts, scheduled tasks, installers, management agents, and tools that start
powershell.exeor load Windows PowerShell modules. - Plan your move to PowerShell 7. Use PowerShell 7 for new automation.
- Keep Windows PowerShell 5.1 where you still need it. Some modules and tools work only in Windows PowerShell 5.1.
More information
What about Windows PowerShell ISE?
The Windows PowerShell Integrated Scripting Environment (ISE) was created as an IDE for Windows PowerShell v2.0, redesigned for v3.0, and last updated for Windows PowerShell v5.1 in 2016. It does not support versions higher than Windows PowerShell v5.1, so it does not support v6 or later.
And yes, this means it’s time to say goodbye and start using more modern tools like Visual Studio Code. Took me some time to switch to that in the past, too, but VSCode is so much better!
Wrapping up
And that’s all about this week’s announcement; it was a long time coming… Have a lovely weekend!