November 17th, 2026
celebratelikeheartcompelling13 reactions

PowerShell 7 is coming to Windows

SR. PRODUCT MANAGER

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:

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

Author

Jason Helmick
SR. PRODUCT MANAGER

Nice to meet you! I’m a Product Manager on the PowerShell team at Microsoft. My focus is on all things PowerShell including Predictive IntelliSense, Crescendo, DSC and PlatyPS. One favorite pastime is working with the rapidly growing PowerShell community.

10 comments

Sort by :
  • Michael Taylor 5 hours ago

    Curious how this is going to work since MSIX only supports per-user installations. Does that mean everybody who logs into Windows will now get their own copy of PS? How is that going to allow SysAdmins to ensure that the latest PS is installed on Windows machines including servers?

  • Chris Black 12 hours ago

    Hopefully, gradually we will get feature parity… like WDAC commands etc 😉 But it is definitely a step in the right direction 🙂

    Happy Azure Localling 🙂

  • Ken Hamilton

    I would love it if SCOM supported PowerShell 7+. I’m forced to do everything (workflows and console/module) with Windows Powershell.

    • Jason HelmickMicrosoft employee Author 8 hours ago

      Thanks for the feedback Ken. SCOM is built and maintained by its own product team, who set their plans based on feedback from their customers, so the most effective thing you can do is tell that team directly through the SCOM feedback channels. The PowerShell team is also talking with product teams across Microsoft as PowerShell 7 comes to Windows, and we’ll keep doing that.

  • Solodow, Damien

    Fantastic news! Will be interested to see how the team squares the lifecycle differences.
    Does this mean that the Microsoft.Online.SharePoint.PowerShell module will stop requiring Windows PowerShell?

    Will PS7 native versions of the inbox modules (e.g. the various RSAT ones) be coming as well, and if so will they be available for down-level (e.g. 26H2) clients?

    • Jason HelmickMicrosoft employee Author 8 hours ago

      Thank you for the kind words and the questions. PowerShell 7 is included beginning with the next release of Windows, so this is forward only. Earlier versions, including 26H2, keep Windows PowerShell 5.1, which remains supported and receives security updates per each Windows version's lifecycle KBArticle

      The SharePoint Online and RSAT modules are owned by their own product teams, who set plans based on their customers' feedback, so please tell those teams directly, including which Windows versions you need. The PowerShell team is also talking with product teams across Microsoft as PowerShell 7 comes to Windows.

      Read more
  • ozbobWA

    Will the ISE default to the new PowerShell7?

    • Jason HelmickMicrosoft employee Author 8 hours ago

      Thanks for asking ozbobWA. The Windows PowerShell ISE is built for Windows PowerShell 5.1, and it doesn’t switch to PowerShell 7. Using the ISE with PowerShell 7 isn’t something we support. For PowerShell 7 you can use the editor you prefer. If you’d like a free option, Visual Studio Code with the PowerShell extension is a good choice, and its ISE Mode gives you a familiar ISE-style layout. Here’s how to turn it on: [How to replicate the ISE experience in Visual Studio Code](https://learn.microsoft.com/powershell/scripting/dev-cross-plat/vscode/how-to-replicate-the-ise-experience-in-vscode).

    • Mark Montgomery

      I have the same question. While general script development can be done (and is done today) in VScode. It is incredibly handy to diagnose both issues and scripts quickly and effectively on the troubled machine in ISE even when they are PS core scripts. Frequently you only need a section of the script.

      • Jason HelmickMicrosoft employee Author 8 hours ago

        Thanks for asking Mark. The Windows PowerShell ISE is built for Windows PowerShell 5.1, and it doesn’t switch to PowerShell 7. Using the ISE with PowerShell 7 isn’t something we support. For PowerShell 7 you can use the editor you prefer. If you’d like a free option, Visual Studio Code with the PowerShell extension is a good choice, and its ISE Mode gives you a familiar ISE-style layout. Here’s how to turn it on: [How to replicate the ISE experience in Visual Studio Code](https://learn.microsoft.com/powershell/scripting/dev-cross-plat/vscode/how-to-replicate-the-ise-experience-in-vscode).