Skip to content
TrustList
News

PowerShell 7 will ship in the box with the next Windows release

Editorial

By TrustList Editorial

Microsoft says the next Windows release will include PowerShell 7 as the upgrade for Windows PowerShell 5.1, which keeps running existing scripts; MSIX gaps for SYSTEM, DISM and machine-wide settings are still being closed.

About PowerShell 7 will ship in the box with the next Windows release

PowerShell 7 will ship in the box with the next Windows release

17 November 2026: Microsoft's PowerShell team has said that, 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 details in a support article numbered KB5137172, and the PowerShell team's blog post sets out what it means for scripts and automation.

Not yet independently verified. The Microsoft post names KB5137172 for details but gives no Windows version or ship date. Claims that 26H2 is the last Windows version to ship 5.1 by default, and that a later version removes it as an optional feature, are Windows Central's report only and do not appear in the Microsoft text we read. We did not read KB5137172 and did not test PowerShell 7 on any script. We will update this when it can be confirmed, and remove this note.

Existing scripts keep working

The post's main message is reassurance. PowerShell 7 is designed to run side by side with Windows PowerShell 5.1, and the team says existing automation needs no changes. Windows PowerShell 5.1 continues to run scripts, scheduled tasks and services, and administrators move to PowerShell 7 when they are ready. The team describes the 5.1 version as the one that has carried much of the world's Windows automation, and PowerShell 7 as the modern, cross-platform version developed in the open.

Gaps Microsoft says it is still closing

PowerShell 7 is delivered as an MSIX package, and the post admits that MSIX does not yet match everything the older MSI installer did. Three gaps are named. The first is running as the SYSTEM account, which affects scheduled tasks, services, device-management scripts and remoting. The second is support for the DISM cmdlets, such as Add-WindowsCapability. The third is support for machine-wide settings, such as the all-users profile. The team says work is in progress and tracks each item in a public issue.

For a business, these three gaps are exactly the places where management scripts run, so they decide how fast you can move.

Tools and a working group

Microsoft says it is investing in community-built tools, documentation and better compatibility checks in PSScriptAnalyzer to cover three jobs: finding what you have, including scheduled tasks and services; flagging what in a script needs attention before it runs in PowerShell 7; and explaining what to change and why. It will share each piece as it is ready. The team is also starting an Inbox Working Group to triage issues that affect PowerShell 7 in Windows, and asks users to report problems in the PowerShell repository on GitHub.

What press reports add

Windows Central reports that Windows 11 26H2 is the last Windows version to ship Windows PowerShell 5.1 by default, and that a later, unnamed version would remove it as an optional, on-demand feature. That text did not appear in the Microsoft post we read, so treat it as the press outlet's report until Microsoft's article says the same.

What an IT team should do

Begin an inventory now. List scheduled tasks, services, login scripts, device-management scripts and any tooling that calls powershell.exe by name, because those will be the first to meet a machine where PowerShell 7 is present. Microsoft's documentation on the differences between 5.1 and 7.x and on migrating between them is the place to start for modules, profiles and remoting.

Next, test scripts in PowerShell 7 before moving them. Many will run unchanged, some will need edits, and some may have to stay on 5.1 for now. Record which group each script belongs to. Pay particular attention to anything that must run as SYSTEM, uses DISM cmdlets or relies on an all-users profile, since those depend on the open gaps.

Finally, ask your vendors whether their management modules support PowerShell 7, and put the answers in your plan, because a module that needs 5.1 will set your own timetable.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in