Thursday 19 November 2026 Edition compiled at 07.46 NL EN FR
← Tech · Programming languages
Tech · Programming languagesDeveloper tools

Microsoft sidelines Windows PowerShell 5.1 as the next Windows bundles pwsh by default

The old shell becomes an optional component and will later disappear entirely, and administrators are advised to start inventorying their scripts now.

· latest source update di · 3 sources · Microsoft PowerShell Team, Techzine, IT-Connect · Compiled with AI
Illustration for this article

Microsoft's PowerShell team announced on its developer blog on Tuesday that the next version of Windows will be the first to ship with PowerShell 7. That is the open-source edition that also runs on macOS and Linux and is built on .NET. At the same time, the old Windows PowerShell 5.1, based on the .NET Framework, is now officially listed as deprecated in a support document, Techzine reports.

Little changes for now. IT-Connect writes that Windows 11 26H2 and Windows Server 2025 are the last versions in which 5.1 is enabled by default. In the next Windows it becomes a feature on demand, although it is still switched on for new installations. In a later version 5.1 will be removed entirely, with the timing depending on how much the old version is still used in practice, according to Microsoft. Until then powershell.exe and pwsh.exe run side by side.

PowerShell 7 is not entirely ready yet. From version 7.7 it ships as an MSIX package instead of MSI, and according to both sites that still causes problems with scripts running under the SYSTEM account, with DISM cmdlets such as Add-WindowsCapability and with machine-wide settings such as the shared profile.

Microsoft advises administrators to check now which scripts, scheduled tasks, installers and agents still call powershell.exe. The company is working on tools to map that out, including stricter compatibility checks in PSScriptAnalyzer, and is setting up a working group to follow up on issues with the built-in PowerShell 7, according to Techzine.

Spotted a mistake in this article? Let us know.