Newshot

Microsoft Announces PowerShell 7 Will Ship With Windows by Default; Windows 11 26H2 Is the Last Version With 5.1 Pre-Enabled

AI summary

Microsoft announced today that future Windows versions will include PowerShell 7 by default, gradually pushing the modern command-line tool to replace Windows PowerShell 5.1. According to Microsoft's KB5137172 support document, Windows PowerShell 5.1 is now officially deprecated and no longer receives active feature development, though it remains part of Windows and continues to get security updates tied to the Windows lifecycle. Microsoft's schedule shows Windows Server 2025 and Windows 11 26H2 are the last versions to enable Windows PowerShell 5.1 by default; from the next Windows version, Windows PowerShell 5.1 will become a feature-on-demand (FOD) and will be fully removed in a future release, with timing to be determined based on usage data and announced in advance.

Translation(model translation, not the source's own text)

Microsoft announces PowerShell 7 will ship with Windows by default; Windows 11 26H2 will be the last version to pre-enable 5.1

IT Home, November 18: Microsoft announced today that future Windows versions will include PowerShell 7 by default, gradually pushing this modern command-line tool to replace Windows PowerShell 5.1.

Jason 赫尔米克 (Jason Helmick), senior product manager on Microsoft's PowerShell team, said that starting with the next Windows version, PowerShell 7 will be included in the system as an upgrade to Windows PowerShell 5.1. This is also one of the goals the PowerShell team has long hoped to achieve. Previously, Windows shipped with Windows PowerShell 5.1, while PowerShell 7 was the one that continued to be developed, supported cross-platform operation, and gained new features.

IT Home noted that according to Microsoft's KB5137172 support document, Windows PowerShell 5.1 has officially entered the deprecation phase and no longer receives active feature development, but it is still part of Windows and continues to receive security updates corresponding to the Windows lifecycle. Existing scripts and tools that depend on this version will not stop running immediately.

Microsoft's published timeline shows that the latest Windows Server 2025 and Windows 11 26H2 are the last versions to enable Windows PowerShell 5.1 by default. Starting with the next Windows version, Windows PowerShell 5.1 will become a feature on demand (FOD) and will be completely removed in a future version (the specific timing will be determined based on usage data and announced in advance).

Microsoft emphasized in particular that this adjustment will not require users to immediately modify existing scripts. PowerShell 7 and Windows PowerShell 5.1 can run side by side, and existing automation tasks, scheduled tasks, and system services can continue to use the old environment, so users can migrate gradually according to their actual situation.

However, the two are not fully compatible. Microsoft points out that some scripts can run directly in PowerShell 7, others need modification, and some scripts may need to continue using Windows PowerShell 5.1. Microsoft recommends that administrators check scripts, scheduled tasks, installers, and management agents in advance to confirm which tools depend on powershell.exe or legacy modules.

Microsoft also disclosed that PowerShell 7 is currently delivered through MSIX packages, and some features are still being improved, including running as the SYSTEM account, support for DISM commands, and computer-wide settings. These features involve scenarios such as scheduled tasks, system services, device management scripts, and remote management, and the related work is still underway.

Microsoft also plans to invest resources this time to improve script migration tools and compatibility checking capabilities, helping administrators identify dependencies in existing automation environments, discover potential compatibility issues, and receive corresponding modification suggestions. Microsoft has also established an Inbox Working Group to collect and triage issues affecting PowerShell 7's operation in Windows.

  • Microsoft releases PowerShell 7.7: Built on .NET 11, strengthens security protection

Related articles

  • Microsoft Windows 11 preview adds the ability to delete individual FIDO2 passkeys, no longer requiring a full security key reset
  • Microsoft rolls out Windows 11 Build 26320.10003 and 26340.10013 preview updates: taskbar adjustments and multiple new features
  • Microsoft Windows 11 reportedly affected by SignDrop zero-day vulnerability: regular users can escalate privileges to SYSTEM, with no dedicated fix patch yet
  • Developers launch WinPopBit project to let older processors such as AMD K8 and Intel Pentium 4 run Microsoft Windows 11
  • Microsoft releases Windows 11 Beta / Experimental / RP multi-channel preview builds: including 28020.3532 and other rollouts
  • Microsoft deliberately slows down Windows 11 startup app loading: aimed at preventing multiple apps from competing for system resources; modifying two registry entries can reduce it from 150 seconds to 30 seconds

The translation is machine-generated and individual terms may be off. Nothing is rewritten or cut; the original is authoritative.

Published by IT之家
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗