Windows PowerShell 5.1 and PowerShell 7 are separate products. Windows PowerShell 5.1 is the Windows-only shell built on .NET Framework; PowerShell 7 is its newer, cross-platform continuation, built on modern .NET. Installing PowerShell 7 does not remove or replace 5.1, so the right choice depends mainly on whether the scripts and modules you rely on work in the newer shell.
What is Windows PowerShell?
Windows PowerShell is Microsoft’s Windows-only command shell and scripting environment. Its latest version is 5.1, which uses the full .NET Framework and no longer receives new features. Microsoft says it is supported according to the lifecycle of the Windows version on which it runs. Microsoft’s Windows PowerShell overview explicitly distinguishes it from the newer PowerShell product.
PowerShell 7 is the modern continuation: it is built on newer .NET and runs on Windows, Linux, and macOS. On Windows, both products can be installed at once. They have distinct executable names, installation locations, profiles, module paths, remoting endpoints, and event logs, so having PowerShell 7 does not mean Windows PowerShell 5.1 has disappeared. Microsoft’s Windows installation guide covers how the products coexist.
Windows PowerShell 5.1 vs. PowerShell 7
| What differs | Windows PowerShell 5.1 | PowerShell 7 |
|---|---|---|
| Operating systems | Windows only | Windows, Linux, and macOS |
| .NET foundation | Full .NET Framework | Modern .NET |
| Executable on Windows | powershell.exe |
pwsh.exe (also launched by entering pwsh in a terminal) |
| Product relationship | Windows-bundled product; 5.1 is its latest version | Separate product that can be installed alongside 5.1 |
| Modules and scripts | Needed by some Windows-specific or legacy workflows | Many workflows work, but compatibility must be checked for the specific modules and scripts |
Microsoft describes Windows PowerShell and PowerShell as “two separate products.” For more detail on behavior differences, see the PowerShell version differences guide.
Recommended Free Tools
#1 Best Overall
- Book - powershell for sysadmins: workflow automation made easy
- Language: english
- Binding: paperback
How to tell which shell you are using
Check the executable name or ask the running shell for its version:
powershell.exestarts Windows PowerShell 5.1.pwsh.exestarts PowerShell 7; in a terminal, you can usually launch it by typingpwsh.- Run
$PSVersionTable.PSVersionin either shell to see the version of the current session.
The executable matters when launching scripts from shortcuts, scheduled tasks, terminal profiles, or other applications: a command that starts one product does not automatically start the other. Windows PowerShell ISE is a separate editor and works only with Windows PowerShell 5.1.
Which version should you use?
Use PowerShell 7 for new or cross-platform work
PowerShell 7 is the sensible starting point for new scripts when the required modules and commands support it. It is the cross-platform product, and Microsoft continues to publish its releases and support information on the PowerShell support lifecycle page.
Keep Windows PowerShell 5.1 for dependencies that require it
Some older or Windows-specific modules still require Windows PowerShell. If an essential module or workflow fails in PowerShell 7, continue running that task in 5.1 while you check whether the module has a supported alternative or a compatible version. Do not assume a script is portable simply because its commands look the same: scripts that call .NET methods directly can behave differently across the two .NET foundations.
Rank #3
Test the workflow, not just the script file
Before changing a production task or a team’s default shell, test the actual script together with its required modules, credentials, remoting, scheduled-task settings, and any .NET calls. Microsoft’s migration guide identifies differences including executable names, module paths, profiles, remoting endpoints, and event logs. A script that opens successfully may still depend on a module, endpoint, or path configured only for the other product.
Can PowerShell 7 run Windows PowerShell modules?
Sometimes. PowerShell 7 includes a Windows Compatibility feature that can make some Windows PowerShell modules available through implicit remoting. It starts a background Windows PowerShell 5.1 process, creates a session named WinPSCompatSession, and exposes compatible commands in the PowerShell 7 session. This is a bridge, not a guarantee that every module will work exactly as it does when loaded directly in 5.1.
Check the required module and its commands in the intended workflow before relying on the feature. Some modules still need to run directly in Windows PowerShell 5.1. Microsoft documents the feature and its limitations in the Windows PowerShell compatibility reference.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to install PowerShell 7 on Windows
Microsoft documents several Windows installation methods. Its guide recommends WinGet for client computers and describes MSI as suitable for Windows Server and enterprise deployment. Choose based on your device, deployment needs, and package requirements; check the current guide for availability and prerequisites.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
| Method | Best fit described by Microsoft | Consideration |
|---|---|---|
| WinGet | Windows client computers | Check the current guide for package availability and requirements. |
| MSI | Windows Server and enterprise deployment | Useful for managed installation scenarios. |
| MSIX | Casual users | Has limitations; confirm they fit your use case. |
| ZIP | Side-loading or keeping multiple versions | Requires using the extracted installation as appropriate for your setup. |
| .NET Global Tool | Developers already using .NET global tools | Best suited to that existing developer workflow. |
Follow the current PowerShell installation instructions for Windows for exact commands, supported packages, and system requirements. After installation, start PowerShell 7 with pwsh; Windows PowerShell remains available as powershell.exe.
PowerShell support and current versions
PowerShell 7 releases have different support tracks, and their status changes over time. Microsoft’s lifecycle page, retrieved on October 4, 2026, lists PowerShell 7.5.11 as the current Stable release and 7.6.6 as the current LTS release. It also lists 7.4.20, the previous LTS, as supported until November 10, 2026. Treat these as dated version facts rather than permanent recommendations: consult the lifecycle page for the current status before choosing a release. Microsoft says support ends when either the PowerShell version or its target operating system reaches end of life.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
