Microsoft Retires PowerShell 2.0 in Windows 11

Why is Microsoft Removing PowerShell 2.0 Now?

The move to remove PowerShell 2.0 from Windows 11 is strategic and long overdue. Microsoft is making this move to embrace modern, secure, and efficient system tools.

PowerShell 2.0 has many inherent security issues tied to the deprecated framework and its reliance on deprecated encryption & validation protocols.

Recommended: PowerShell Code Signing Best Practices for Signing Your Script

It is also outdated itself and has not been updated since 2017, which keeps it from being productive in any of the current APIs and frameworks that we use today. Its legacy performance is holding back the use of newer tools and is introducing a security penalty during execution.

For some time now, Microsoft has indicated they were not prepared to remove PowerShell 2.0 until dependencies were sorted out (the dependencies that Microsoft mentioned have mostly gone away, or are not used anymore), and have now transitioned to the stage where they can completely move users away from the application.

Timeline of PowerShell 2.0

PowerShell has had a long journey since its inception. Here’s a brief timeline highlighting major milestones:

Year	Event
2006	PowerShell 1.0 released
2009	PowerShell 2.0 introduced with Windows 7
2017	Microsoft officially deprecates PowerShell 2.0
2025	PowerShell 2.0 removed from Windows 11 Insider Build 27891

This progression underscores Microsoft’s move toward modernization and phasing out legacy systems.

What Versions Are Recommended Now?

PowerShell 2.0 is end of life; consumers should upgrade to PowerShell 5.1 or PowerShell 7.x.

PowerShell 5.1 is widely deployed and provided with many client systems, operating systems related to Windows 10 and 11, as PowerShell 5.1 is only for Windows.

For the next evolution of tools with enhanced capability and flexibility for scripting, Microsoft recommends PowerShell 7.x, the open-source, cross-platform version of PowerShell for Windows, Linux, and macOS.

PowerShell 7.x enhances operational capabilities with cross-platform compatibility, newer modules, and there is continual support for updating modules as well.

PowerShell 7.x leverages greater performance, improved error handling, and devops features, whereas it works with the current deployments in a typical CI/CD pipeline. PowerShell 7.x can be downloaded from its GitHub repository.

How to Check Your PowerShell Version?

To assess the version of PowerShell that you are using, you can do the following:

Open your PowerShell terminal session and type:

$PSVersionTable.PSVersion

This command displays the installed version. If it shows 2.0, consider upgrading to avoid compatibility issues and security risks.

Windows 11 Insider Build 27891: What Else is New?

Microsoft’s latest Update Insider Preview Build 27891 is more than the removal of PowerShell 2.0; there are many overall improvements to system stability and usability:

• All of the newly promoted features aside, you can now use the “Reset this PC” feature that would not work after some upgrades.
• Visual changes included putting the acrylic effect back into the Taskbar (to maintain their Fluent Design direction), and an improvement fixed a bug in Windows Update that would hang at 2%.
• Languages such as Arabic and Vietnamese can produce text in Task Manager and other system interfaces, which they have never been able to produce, fixing some internationalization bugs.
• There is also a small usability improvement in File Explorer, when accessing folders in the address bar through the “…” menu, the full navigation path is now shown without truncating.
• As well as the productivity improvements, the bugs that caused the system to crash when opening properties for the microphone or Bluetooth in Settings have been fixed.
• Task Manager correctly arrives at the exit call without calculating CPU utility. The System Idle Process no longer shows zero usage.

Microsoft Store Update

Users of Microsoft Store who are using version 22406.xxxx.x or greater can now install apps and games directly from the featured section of the homepage. 

This simplified process was made possible by using Microsoft’s Control Feature Roll-out method, which gradually introduces features for testing and feedback to monitor performance and community response.

By separating the updates, we can now enhance user experience and confirmation of system stability on the entire Insider ecosystem.  

Known Issues

The update is meant to benefit users in a variety of ways, while it also possesses a couple of known issues. While on Copilot+ PC users may be having some troubles with Windows Hello, including a loss of PIN or Biometric Authentication, with associated error code 0xd0000225, and fixed by resetting the PIN.

Users may also at times, have some issues with Remote desktop connections on ARM64 based PC and heavier graphical issues may occur.

Some UI elements may appear to not be completely localized or may not exist in other languages. Other settings menu items such as the Power & Battery for example, may crash. Microsoft recommends submitting issues through the Feedback Hub using WIN + F.

What Does This Mean for IT Teams?

The disappearance of PowerShell 2 should be a wake-up call for IT administrators. It’s time to review your systems for deprecated scripts and begin updating them to use a more secure version of PowerShell.

Focusing on application compatibility in Windows 11 should be the primary focus, along with removing dependencies on the deprecated modules before Microsoft leaves us high and dry. If we are using the newer PowerShell versions, we have a better chance of continuous operations and eliminating risks.

As TechRadar points out, this is part of Microsoft’s larger strategy to simplify Windows (also, a move to improve security). PowerShell 2.0 is clearly an obsolete component—removing it is best practice when doing any type of software lifecycle operation.

“Deprecation of legacy shells such as PowerShell 2.0 is critical due to the reduction of attack surface,” says Richard Speed at The Register.

Windows Security Best Practice:

• Eliminating obsolete components will make code security increasingly important. Code signing is a great way to ensure software integrity.
• Code signing is a process of digitally signing executables and scripts. The digital signature validates the developer’s identity and assures that the code has not changed since being signed.
• Advantages to using branded code signing certificates include: assurance of software authenticity, tamper alerts, increased user trust, and compliance requirements in many enterprise environments.

The Microsoft Developer Guide states, “Customers are also more likely to trust, and therefore install, signed software.”

Protect your Software with Code Signing Certificates

With Microsoft sunsetting old tools, like PowerShell 2.0 soon, securing your software is more important than it ever has been. Make sure your applications and scripts stay trustworthy with branded code signing certificates.

Code signing certificates will guarantee your software is authentic, tamper-proof, and trusted by users. It doesn’t matter if you’re porting from PowerShell 2.0 to PowerShell 7.x or other versions, updating or deploying software with code signing is one of the best cybersecurity practices. It’s better to be ahead of a cyber threat or compliance issue than to be faced with one.

Search