Updating PowerShell on Windows: Available Methods

Updating PowerShell on Windows: A practical guide and official methods

Update PowerShell in Windows It is necessary to distinguish between two different products. Windows PowerShell 5.1 is part of the operating system and only receives security patches through Windows Update. PowerShell 7 is installed separately and uses the executable. pwsh.exe and can be updated with WinGet, Microsoft Store, an MSI package, a ZIP file, or the .NET global tool.

Quick response

And PowerShell 7 is already installed, open Windows Terminal and run:

winget upgrade --id Microsoft.PowerShell --exact --source winget

If it's not already installed, replace upgrade by installFor administration, remoting, or installation for all users, the MSI is more complete than the default MSIX package.

Updating does not fix all errors

If PowerShell is slow to open, crashes, or displays errors, the cause could also be related to the startup profile, an incompatible module, a corporate policy, antivirus software, environment variables, or corrupted files. Updating may provide fixes, but it shouldn't be considered a solution for every problem.

Windows PowerShell 5.1 and PowerShell 7 are not the same application

Feature	Windows PowerShell 5.1	PowerShell 7
Executable	`powershell.exe`	`pwsh.exe`
Motor	.NET Framework 4.x	Modern and cross-platform .NET
Update	Windows Update; security maintenance	WinGet, Store/MSIX, MSI, ZIP o .NET
Usual route	`C:\Windows\System32\WindowsPowerShell\v1.0`	`C:\Program Files\PowerShell\7`
State	Included for compatibility; no new features	Asset development and support

Installing PowerShell 7 does not replace or uninstall Windows PowerShell 5.1. Both can coexist because they use different executables, folders, profiles, and module paths. This separation allows you to retain older tools that are still needed. Windows PowerShell while using the features modern versions of PowerShell 7.

Versions in effect as of July 2026

PowerShell 7.6.4 LTS: current long-term support version and package that WinGet offers by default.
PowerShell 7.5.9 Stable: short cycle version, supported until November 10, 2026.
PowerShell 7.4.18 LTS: Previous LTS version, also supported until November 10, 2026.
PowerShell 7.7 Preview: test branch without production support.

¿Stable o LTS?

The naming convention can be confusing because PowerShell 7.6 LTS is newer than PowerShell 7.5 Stable. For most users and production teams, 7.6 LTS is the more sensible choice due to its longer maintenance cycle.

Check which version you have installed

Open the console you normally use and run:

$PSVersionTable | Select-Object PSEdition, PSVersion

PSEdition Desktop and version 5.1: you are in Windows PowerShell.
PSEdition Core and version 7.x: you are in PowerShell 7.
If you installed PowerShell 7 but are still seeing 5.1, you probably opened powershell.exe instead of pwsh.exe.

where.exe powershell where.exe pwsh

Which method should be used

Method	Best use	Updates	Limitations
WinGet MSIX	PC personal	WinGet o Store	Per user; without PowerShell remoting
WinGet MSI	Administration and full team	WinGet or Microsoft Update	Requires administrator
MSI from GitHub	Offline the company	Microsoft Update if enabled	Choosing the right architecture
Microsoft Store	Graphical installation	Automatic	MSIX limitations
ZIP	Portable or multiple versions	Manuals	Without PATH or automatic access
.NET Global Tool	Developers	dotnet tool	Requires .NET SDK

1. Install or update PowerShell using WinGet

Microsoft recommends WinGet as the preferred method for installing PowerShell on client computers. You can run it from Windows Terminal, Command Prompt, Windows PowerShell, or PowerShell 7.

Run as administrator option to open a console in Windows — Open as administrator when you are going to install the MSI for the whole computer.

Update the fonts and locate the official package

winget source update winget search --id Microsoft.PowerShell --exact

PowerShell search using WinGet — The filter by exact ID prevents confusing the stable package with the Preview package.

Microsoft.PowerShell identifier displayed by WinGet — The official ID is Microsoft.PowerShell.

First time installation

Since PowerShell 7.6, the standard command installs the MSIX package:

winget install --id Microsoft.PowerShell --exact --source winget

To install the traditional MSI:

winget install --id Microsoft.PowerShell --exact --source winget --installer-type wix

Upgrading an existing installation

winget upgrade --id Microsoft.PowerShell --exact --source winget

If you use MSI and want to keep that type of installation:

winget upgrade --id Microsoft.PowerShell --exact --source winget --installer-type wix

Installing PowerShell using WinGet — WinGet displays the source, the chosen package, and the progress.

Check the type of installation before changing it

MSIX is installed per user, while MSI is typically installed for the computer. Check first. winget list --id Microsoft.PowerShell --exact to avoid creating unnecessary parallel facilities.

2. Download and install PowerShell from GitHub

The official repository publishes signed installers. This method is appropriate when you need to retain the installer, work offline, choose the architecture, or deploy it with enterprise tools.

Open the Official PowerShell page on GitHub.
Download win-x64.msi for most PCs or win-arm64.msi for Windows over ARM.
For general use, choose the latest revision of the current LTS branch.
Do not use Preview in production.

PowerShell packages published on GitHub — Check the branch, architecture, and extension of the package.

Important MSI options

Add PowerShell to Path: allows you to start PowerShell 7 with pwsh.
Enable updating through Microsoft Update: Enable updates via Windows Update, WSUS, or Configuration Manager.
Register Windows Event Logging Manifest: Logs PowerShell events.
Context menu: Adds optional shortcuts in the Explorer.
Enable PowerShell Remoting: Activate it only if you really need it and understand its settings.

MSI PowerShell Assistant in Windows — The MSI allows you to control PATH, Microsoft Update, logs, and remoting.

PowerShell installation complete — Open a new console to reload PATH.

PowerShell 7.7 changes the distribution

Microsoft indicates that PowerShell 7.7 will no longer publish MSI files. WinGet will install MSIX files. This particularly affects administrators who rely on all-user installations, remote deployments, or MSI deployments.

3. Install or update from the Microsoft Store

The Microsoft Store offers a graphical installation and automatic updates. It is suitable for an individual user who uses PowerShell locally.

Open Microsoft Store.
Search PowerShell and verify that the publisher is Microsoft Corporation.
Credit install.
To force an update, open Library and use Get updates.

Microsoft Store on Windows 11 — Microsoft Store manages the MSIX installation and its updates.

PowerShell en Microsoft Store — Check the product and its publisher before installing.

Store/MSIX limitations

It is installed for a single user, does not support PowerShell remoting, and restricts certain write operations. $PSHOME, including profiles for all users and some LocalMachine scope settings.

4. Use the portable ZIP package

The ZIP file is useful for testing a version, keeping multiple 7.x branches in separate folders, or running PowerShell without a conventional installation.

Download the x64 or Arm64 ZIP from GitHub.
Unlock the file if Windows marks it as coming from the Internet.
Extract the content.
Execute pwsh.exe from the folder.
Manually add a shortcut or path to your PATH if needed.

The ZIP file does not update automatically.

You must download each new version. It also doesn't configure requirements, access, PATH, Microsoft Update, or remoting.

5. Install as a global .NET tool

Developer-oriented method using the .NET SDK:

dotnet tool install --global PowerShell

To update:

dotnet tool update --global PowerShell

How to update Windows PowerShell 5.1

Windows PowerShell 5.1 does not become PowerShell 7. It is a component of Windows and receives security updates through Windows Update.

Open Configuration.
Enter Windows Update.
Credit Check for updates.
Install the cumulative updates and restart if prompted.

Even if Windows is updated, Windows PowerShell will still display version 5.1. To use PowerShell 7, open the application. PowerShell 7 or execute pwsh.

Using Windows PowerShell 5.1 and PowerShell 7 at the same time

The coexistence is intentional. Windows PowerShell 5.1 may still be required for legacy modules, Windows PowerShell ISE, or .NET Framework-based tools. PowerShell 7 is preferable for newer scripts and modern automation.

Perfiles de Windows PowerShell 5.1 y PowerShell 7 en Windows Terminal — Windows Terminal can display separate profiles for both editions.

Abrir Windows PowerShell 5.1

powershell

Abrir PowerShell 7

pwsh

Check for update

$PSVersionTable | Select-Object PSEdition, PSVersion, OS

winget list --id Microsoft.PowerShell --exact

Get-Command pwsh | Select-Object Name, Source, Version

Troubleshooting

WinGet is not recognized

Update App Installer WinGet is not available natively from the Microsoft Store. It is not included with Windows Server 2022 or earlier; Windows Server 2025 includes it with Desktop Experience.

WinGet cannot find PowerShell

winget source update winget search --id Microsoft.PowerShell --exact --source winget

If the source remains damaged, from an administrative console:

winget source reset --force winget source update

pwsh is not recognized

Close and reopen Windows Terminal. If you installed the MSI, try:

"C:\Program Files\PowerShell\7\pwsh.exe"

PowerShell takes a long time to start

pwsh -NoProfile

If it opens correctly, check the file indicated by $PROFILEMake a copy before modifying it and check module imports, network access, and prompt customizations.

One module works in 5.1 but fails in 7

Look for a compatible version. When the module allows it, test the compatibility layer:

Import-Module NombreDelModulo -UseWindowsPowerShell

Safety before updating

Descarga solo desde Microsoft Store, WinGet, Microsoft Learn o PowerShell/PowerShell en GitHub.
Do not use portals that repackage the installer.
Copy profiles and scripts before changing branches or installer types.
Test critical scripts before migrating scheduled tasks from Windows PowerShell 5.1.
Do not enable remoting or reduce security controls for a basic installation.

Frequently Asked Questions

¿Instalar PowerShell 7 elimina Windows PowerShell 5.1?

No. They are installed in different folders and use different executables.

Which version is recommended in 2026?

For most users and production systems, PowerShell 7.6 LTS, always in its latest maintenance release.

MSI or Microsoft Store?

Store/MSIX is convenient for personal use. MSI is more suitable for all users, remote access, and advanced management.

Does PowerShell update automatically?

Store/MSIX can be updated automatically. MSI can use Microsoft Update if enabled. ZIP requires manual updating.

Do I need administrator privileges?

Not for all installations. MSIX per user can be installed without elevation; MSI for equipment and system changes usually do require it.

Does updating improve performance?

It can provide fixes and security, but a slow console also requires checking profiles, modules, network, and antivirus. Use pwsh -NoProfile to isolate the beginning.

Conclusion

The simplest way to Update PowerShell on Windows It's about using WinGet with the exact ID Microsoft.PowerShellFor everyday use, MSIX is sufficient; for administration, remoting, or deployment for all users, MSI offers more complete integration.

Windows PowerShell 5.1 will remain installed and will be maintained through Windows Update. After installing PowerShell 7, open pwsh, verify $PSVersionTable and test your modules and scripts before migrating important automations.

Official sources consulted