Microsoft has removed Windows PowerShell 2.0 from the latest Windows 11 Insider Preview builds, marking a major step forward in enhancing the operating system's security. This change was announced with the release of Windows 11 Insider Preview Build 27891 to the Canary Channel on July 3, 2025. It addresses long-standing security and architectural weaknesses that have affected the outdated version of PowerShell.
The removal of PowerShell 2.0 is a key security improvement for Windows 11. Initially released with Windows 7, PowerShell 2.0 has long been a vulnerable point due to its lack of modern protections such as script block logging, constrained language mode, and integration with the Anti-Malware Scan Interface (AMSI). These missing features made it an attractive tool for attackers who use it to avoid detection by Windows Defender and run harmful scripts.
Another major issue with PowerShell 2.0 is its dependence on .NET Framework 2.0, which lacks the security improvements found in newer frameworks. Unlike PowerShell 5.1 and the 7.x versions, it does not support key features like execution policy enforcement, transcription logging, or module loading restrictions. Security experts have observed many cases where attackers intentionally downgrade to PowerShell 2.0 by using the "powershell.exe -version 2" command to bypass current protections.
In addition to removing PowerShell 2.0, Build 27891 brings a range of fixes and improvements. These include a fix for the “Reset this PC” feature found under Settings > System > Recovery, which had not been working in earlier Canary builds.
The update also corrects visual issues with the taskbar’s acrylic material and resolves a problem where Windows Update downloads would freeze at 2 percent.
Other enhancements include fixes to the File Explorer’s address bar dropdown truncation and increased stability of the Settings app, particularly when accessing microphone properties in the Sound section.
The Task Manager received improvements as well, such as accurate CPU usage calculations and a fix for the System Idle Process that was incorrectly displaying zero percent usage. Looking ahead, Microsoft plans to provide more details about the removal of PowerShell 2.0 from production versions of Windows 11 in the coming months.
In the meantime, enterprise administrators are advised to review their systems for any reliance on PowerShell 2.0 and begin updating automation scripts to use PowerShell 5.1 or newer. This change will require careful evaluation of older applications and admin tools that may still depend on legacy cmdlets or .NET Framework 2.0 components.
IT teams should prioritize updating PowerShell scripts, ensuring they function properly across newer environments and include solid error handling.
This transition period offers a good opportunity to adopt modern PowerShell security practices such as script signing, configuring execution policies, and deploying Just Enough Administration (JEA) to tighten access control.
Found this article interesting? Follow us on X(Twitter) ,Threads and FaceBook to read more exclusive content we post.
