PowerShell 7 is coming to Windows. Beginning with the next release of Windows, PowerShell 7 will be included as the upgrade for Windows PowerShell 5.1. The Windows team has published the details in KB5137172. Here is what this means for you, your scripts, your automation, and where our work stands.
The top question we always get asked
For years, PowerShell has lived in two places. Windows PowerShell 5.1 is the one in the box, and it has carried a great deal of the world’s automation: the scheduled tasks, services, and admin scripts that have run quietly for years. PowerShell 7 is the modern PowerShell: the one we develop in the open, across platforms, and where new features go.
Bringing those together has been the request we heard most from you: the PowerShell that comes with Windows should be PowerShell 7. Including PowerShell 7 in Windows is a milestone we’ve been working toward since PowerShell went cross-platform. But we couldn’t have reached this milestone without your persistent requests.
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
0 comments
Be the first to start the discussion.