MC1133898 – PowerShell 2.0 removal in Windows

Product:

Azure Active Directory, Exchange, Windows, Windows Server

Platform:

Developer, Online, Windows Desktop, World tenant

Status:

Launched

Change type:

Admin impact

Links:

27891

Details:

Windows PowerShell 2.0 is removed from Windows 11, version 24H2 starting with the August 2025 non-security update. It's also removed from Windows Server 2025 starting with the September 2025 security update. Windows Insider preview builds already reflect this change as of July 2025. Windows PowerShell 2.0 is over 14 years old, lacks many security enhancements of the later versions, and has been deprecated since 2017. By using the newer and supported PowerShell 7 or PowerShell 5.1, you can help ensure that scripts run safer. If you have legacy scripts or software that explicitly depend on PowerShell 2.0, you'll need to either update them or use a workaround to prevent disruptions.

When will this happen:
2017: PowerShell 2.0 was deprecated.
July 2025: PowerShell 2.0 is removed from Windows Insider preview builds.
August 2025 Windows non-security update: PowerShell 2.0 is removed from Windows 11, version 24H2 and later.
September 2025 Windows security update: PowerShell 2.0 is removed from Windows Server 2025 and later.

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2025-08-13

updated:
2025-08-13

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

linked item details

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

Removal of PowerShell 2.0
Legacy scripts or software that depend on PowerShell 2.0 will fail to execute, leading to potential disruptions in automated tasks and processes.
   - roles: System Administrators, Developers
   - references: https://devblogs.microsoft.com/powershell/windows-powershell-2-0-deprecation/, https://learn.microsoft.com/windows/whats-new/deprecated-features

Incompatibility with legacy systems
Existing applications that rely on PowerShell 2.0 may not function correctly, causing operational delays and increased support requests.
   - roles: IT Support, Application Managers
   - references: https://devblogs.microsoft.com/powershell/windows-powershell-2-0-deprecation/, https://support.microsoft.com/topic/fe6d1edc-2ed2-4c33-b297-afe82a64200a

Increased workload for IT teams
IT teams will need to allocate resources to update or replace outdated scripts and software that depend on PowerShell 2.0, diverting attention from other critical tasks.
   - roles: IT Managers, System Administrators
   - references: https://devblogs.microsoft.com/powershell/windows-powershell-2-0-deprecation/, https://blogs.windows.com/windows-insider/2025/07/03/announcing-windows-11-insider-preview-build-27891-canary-channel/

User experience degradation
Users relying on automated scripts for daily tasks may experience interruptions, leading to frustration and decreased productivity.
   - roles: End Users, Business Analysts
   - references: https://devblogs.microsoft.com/powershell/windows-powershell-2-0-deprecation/, https://learn.microsoft.com/windows/whats-new/deprecated-features

Security vulnerabilities
Continued use of unsupported PowerShell 2.0 may expose the organization to security risks, as it lacks modern security enhancements.
   - roles: Security Analysts, System Administrators
   - references: https://devblogs.microsoft.com/powershell/windows-powershell-2-0-deprecation/, https://learn.microsoft.com/windows/whats-new/deprecated-features

Configutation Options**

XXXXXXX ... paid membership only

Opportunities**

XXXXXXX ... free basic plan only

Potentional Risks**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

explanation for non-techies**

The removal of Windows PowerShell 2.0 from upcoming Windows updates is like upgrading from an old car to a new one. Imagine you've been driving a car from 2009. It gets you from point A to point B, but it lacks modern safety features like airbags, backup cameras, and efficient fuel consumption. Similarly, PowerShell 2.0, introduced over 14 years ago, lacks the security enhancements and functionalities of its newer versions, such as PowerShell 5.1 and 7.

In the same way that car manufacturers eventually stop producing parts for older models, Microsoft is phasing out PowerShell 2.0. This change is part of a broader effort to streamline and secure the Windows ecosystem. Most users won't notice this change because newer versions of PowerShell are already available and offer improved performance and security.

However, if your organization relies on scripts or software that specifically require PowerShell 2.0, it's like having custom parts that only fit your old car. You'll need to update these scripts or find alternative solutions to ensure they continue to work smoothly. Microsoft recommends migrating to PowerShell 5.1 or 7, which are backward-compatible with most commands and modules from PowerShell 2.0.

If you're using software that depends on PowerShell 2.0, consider upgrading to newer versions of that software, just as you would replace outdated parts in your car with more efficient ones. This will help prevent any disruptions when PowerShell 2.0 is officially removed from Windows 11 and Windows Server in 2025.

For those who want to dive deeper into the technical details or need guidance on updating scripts, there are resources available online, much like a mechanic's manual for fixing and upgrading your vehicle. These resources provide step-by-step instructions to ensure a smooth transition to newer PowerShell versions.