Microsoft to Deprecate PowerShell 5.1, Shift to PowerShell 7 in Next Windows Version

Microsoft said on November 17 that the next version of Windows will ship with PowerShell 7 as the default built-in shell, formally deprecating PowerShell 5.1 — the console that has run Windows automation.

Windows 11 version 26H2 and Windows Server 2025 will be the last releases where 5.1 is enabled by default.

PowerShell 5.1 shipped with the Windows 10 Anniversary Update and Windows Server 2016, WMF 5.1 in August 2016, and it has been effectively frozen ever since. PowerShell 7, by contrast, is developed in the open, runs cross-platform, and is where new features go.

“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,” Jason Helmick, a senior product manager at Microsoft, said in the announcement carried by Windows Central.

“PowerShell 7 is the modern PowerShell: the one we develop in the open, across platforms, and where new features go.”

Deprecated does not mean deleted — yet

The deprecation has more runway than the headline suggests. 5.1 will continue receiving security patches but no new features, and in the next Windows release it shifts to being offered as a Feature on Demand (FOD) — still enabled by default on new installs, per the companion support article KB5137172, which applies to Windows 11 Home and Pro, versions 24H2, 25H2 and 26H2.

Only in a later version does it disappear entirely, with Microsoft saying removal timing will depend on usage data and be announced in advance.

There is precedent for how slow this clock runs. Microsoft removed Windows PowerShell 2.0 from Canary builds of Windows 11, which it said has been deprecated for years, due to security concerns and the absence of modern capabilities. That took many years. The 5.1 timeline is vaguer — no date has been given — but it points the same direction.

Ollama running in PowerShell and Ubuntu on WSL
Photo: windowscentral.com

Windows Central adds a schedule note: the next version of Windows where PowerShell 7 will replace 5.1 as the default experience is scheduled for the end of 2027, so around about a year from now.

Two executables, one transition

Neither version breaks the other. They coexist side by side, and Microsoft says most existing scripts will run on PowerShell 7 without changes — some need changes before they work, and some may need to keep running in Windows PowerShell 5.1 because PowerShell 5.1 and PowerShell 7 differ in some places, which is why Microsoft is urging users to conduct testing before migrating their environments.

Helmick put it: “Including PowerShell 7 in Windows is a milestone we’ve been working toward since PowerShell went cross-platform. 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.”

Users can determine which version their environment is running by the executable name or a command. The verification methods Microsoft provided:

An IT professional reviews a PowerShell migration checklist beside screens showing classic and modern PowerShell
Photo: windowsforum.com
Verification Method PowerShell 5.1 PowerShell 7 and later
Executable name powershell.exe pwsh.exe
Result of the command “$PSVersionTable.PSEdition” Desktop Core

Run the command within PowerShell. That distinction matters: verifying script behavior and taking inventory of execution environments will be the practical focus.

MSIX and the Store change the update math

PowerShell 7 is delivered as an MSIX, and will be updatable via the Microsoft Store, streamlining the update process for users. The changeover is phased and depends on two things: a packaging format that still has gaps, and a deprecation clock that Microsoft has started but hasn’t finished setting.

Why corporate IT should start its inventory now

PowerShell is widely used in system administration and automation, and corporate IT departments are expected to review the impact on existing operational scripts and management tools. Because both versions will coexist during the transition period, verifying script behavior and taking inventory of execution environments will be the practical focus.

The open question is the endgame. Microsoft has not said when 5.1 leaves Windows entirely, only that the article will be updated as more information becomes available.

A few months ago, one open-source project’s support-policy discussion on GitHub noted flatly that there is no deprecation announcement. That assumption no longer holds. The removal will be announced in advance, Microsoft said in the KB document. The clock, for the first time, is official.

Photo of author

Technology Desk

Technology Desk at Archyde.

Trump Cites $5B in Approved Arms Sales and Nuclear Project in Manila Meeting