MC1133898: PowerShell 2.0 removal in Windows

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. 

 How this will affect your organization: This removal is part of a broader effort to clean up legacy code, reduce the complexity of the PowerShell ecosystem, and improve Windows security. For most users and organizations, this change will be uneventful – newer versions of PowerShell (5.1 and 7.x) continue to be available and supported. However, if you have legacy scripts or software that explicitly depends on PowerShell 2.0, you will need to take action (update them or use a workaround) to prevent any disruptions.  What you need to do to prepare: 

• Recommended: Migrate scripts and tools to newer PowerShell versions. Microsoft primary guidance is to update anything using PowerShell 2.0 to use PowerShell 5.1 or PowerShell 7. PowerShell 5.x introduced many improvements and is backward-compatible for almost all commands and modules. The PowerShell team article provides a guide for this migration. 
• Update or replace outdated software. In some cases, the fix might be to upgrade the software that needed PowerShell 2.0. For example, if an old installer fails, look for a newer version of that product. 
• See Additional information for more resources. 

 Additional information: 

• Read PowerShell 2.0 removal in Windows for further details. 
• Developers’ quick guide to PowerShell migration. 
• Consult the comprehensive list of deprecated features for Windows client. 
• Visit the original 2017 deprecation announcement.