Microsoft has confirmed that PowerShell 7 will be included in the next release of Windows, replacing Windows PowerShell 5.1 as the system's default shell. The announcement was made by the PowerShell 7 team on Tuesday (11/17) on Microsoft's official blog, and the details of the 5.1 deprecation are in support article KB5137172.
Read also: Windows 11 KB5132057 brings new Search with direct actions and is the last preview of 2026 — the latest Windows 11 preview on Geekiki.
What changes
Windows PowerShell 5.1 is the shell that has shipped with Windows for years and underpins much of the system's automation: scheduled tasks, services and admin scripts. It has not received new features in over ten years. PowerShell 7 is the modern successor: cross-platform — it runs on Windows, Linux and macOS — developed in the open, and where new features go.
According to article KB5137172, Windows PowerShell 5.1 is now considered deprecated. Windows Server 2025 and Windows 11 version 26H2 are the last releases that include 5.1 enabled by default. In the next version of Windows, 5.1 will remain available as a Feature on Demand, enabled by default on new installs — and, in a later version, it will no longer be available. Microsoft has not set a date for that removal: the timing will be based on usage data and announced in advance.
Nothing changes immediately for existing 5.1 users. PowerShell 7 was designed to run side by side with Windows PowerShell 5.1: existing scripts, scheduled tasks and services keep working, and each user moves to PowerShell 7 when ready. Microsoft recommends testing scripts in PowerShell 7 before migrating, as there are differences in modules, profiles and remoting.
What is still missing for the transition
PowerShell 7 will be delivered as an MSIX package, and Microsoft admits the format still has gaps compared with the traditional MSI installer: running as the SYSTEM account, support for DISM cmdlets, and support for machine-wide settings such as the all-users profile. The team says it is working to close these gaps and tracks each one in a public GitHub issue.
To organize the migration, Microsoft created a dedicated working group to triage PowerShell 7 issues on Windows and is investing in community tools, documentation and improvements to PSScriptAnalyzer's compatibility checks, to help inventory scripts, flag what needs adjustment and guide the fix.
Already in Windows Insider
The change has already started appearing in test builds: Windows 11 Insider Preview Build 29712.1000, released on Friday (11/20) to the Experimental channel, lists PowerShell 7 in Windows as its only named change. Experimental channel builds can be unstable and reflect early-stage platform work, with no guaranteed match to a specific Windows release.
Why now
According to the PowerShell 7 team, shipping PowerShell 7 in Windows was the most-heard request since the project went cross-platform — a milestone pursued ever since. The change ends a decade in which Windows kept shipping PowerShell 5.1 as the default, even though PowerShell 7 had already been available as a manual install for years.
Image credit: screenshot of PowerShell 7.5, by Refresh100, Wikimedia Commons (MIT license).
Sources:
- Microsoft PowerShell Team — PowerShell 7 is coming to Windows
- Neowin — Microsoft is finally bringing PowerShell 7 to Windows by default
- WindowsForum — PowerShell 7 to Ship With Windows as Microsoft Deprecates PowerShell 5.1
- WindowsForum — Windows 11 Experimental Build 29712.1000 Adds PowerShell 7
Transparency: this article was produced with the assistance of artificial intelligence, cross-checking public posts on X and sources on the internet. Please consult the original sources for more details.
Por Muse