To update PowerShell 7 on Windows 11, open Terminal or Command Prompt and run winget upgrade --id Microsoft.PowerShell --exact, then open a new PowerShell 7 window and check the version. The newest release is PowerShell 7.6.6, part of the 7.6 long-term support line. The built-in Windows PowerShell 5.1 is different: it gets its security fixes through Windows Update and can’t be upgraded to version 7.
These steps cover Windows 11 on x64 and Arm PCs. The WinGet commands also work on Windows 10 version 1809 or later, but Windows 10 reached end of support on October 14, 2025, so its Windows updates have stopped unless the PC is enrolled in Extended Security Updates.
Check Which PowerShell You Have
Windows 11 can have two separate products installed side by side. Windows PowerShell 5.1 comes with Windows. PowerShell 7 is a newer, cross-platform version you install yourself. Installing or updating PowerShell 7 never replaces Windows PowerShell 5.1.
- Open the PowerShell window you normally use. Type
$PSVersionTableand press Enter. This only displays information and changes nothing. - Read PSVersion and PSEdition. Version 5.1 with edition Desktop means Windows PowerShell. A 7.x version with edition Core means PowerShell 7.
- Write down the version number. To show only the number, run
$PSVersionTable.PSVersion. You’ll compare it after the update.

Microsoft’s automatic-variable reference explains that $PSVersionTable describes the session you are in, not every PowerShell on the PC. To open PowerShell 7, search Start for PowerShell 7 (not Windows PowerShell), or press Windows + R, type pwsh, and select OK.
Find Out How PowerShell 7 Was Installed
Microsoft recommends updating PowerShell 7 the same way you installed it. If you don’t remember, open PowerShell 7, type $PSHOME, and press Enter. The folder it shows tells you the method:
| $PSHOME shows | Install method | How to update |
|---|---|---|
| C:\Program Files\PowerShell\7 | MSI installer | WinGet, a newer MSI, or Microsoft Update |
| A folder starting with C:\Program Files\WindowsApps | MSIX (Microsoft Store or WinGet) | Microsoft Store or WinGet |
| A folder under your user profile ending in .dotnet\tools | .NET global tool | dotnet tool update |
| Any other folder | ZIP download | Download a newer ZIP |

Which Version Is Current
Microsoft’s PowerShell support lifecycle page lists these supported releases:
| Release | Type | Support ends |
|---|---|---|
| PowerShell 7.6 (latest 7.6.6) | Long-term support (LTS) | November 14, 2028 |
| PowerShell 7.5 (latest 7.5.11) | Stable | November 10, 2026 |
| PowerShell 7.4 (latest 7.4.20) | Long-term support (LTS) | November 10, 2026 |
LTS means a release gets security and bug fixes for a longer period. If you’re on 7.4 or 7.5, plan to move to 7.6 before November 10, 2026. The WinGet steps below install the newest version, 7.6.6, in one step. Microsoft also lists a 7.7 preview; previews install alongside the stable version and aren’t meant for everyday use.
Before You Update
- Save open scripts and close every PowerShell 7 window, including PowerShell 7 tabs in Windows Terminal. The installer can’t replace files that are in use.
- Run the update from Command Prompt or a Windows PowerShell 5.1 tab rather than from PowerShell 7 itself.
- Be ready to approve a User Account Control prompt. On a work PC, IT may manage PowerShell and block manual updates.
If a command asks for elevation, here are quick ways to run as administrator in Windows 11.
Update PowerShell 7 With WinGet
WinGet, the Windows Package Manager, is built into Windows 11. Microsoft’s upgrade-command documentation supports targeting one package by its ID, so this command updates PowerShell and nothing else.
- Open Terminal or Command Prompt. Right-click Start and select Terminal, or search Start for Command Prompt.
- Check for an update. Type
winget list --id Microsoft.PowerShell --upgrade-availableand press Enter. If an update exists, WinGet shows your installed version and the available version. If it says no installed package was found, you’re either up to date or PowerShell 7 was installed another way (see Troubleshooting). - Run the upgrade. Type
winget upgrade --id Microsoft.PowerShell --exactand press Enter. The first time you use WinGet, it may ask you to accept the source agreements; type Y and press Enter. - Approve the User Account Control prompt if one appears. WinGet downloads the installer and shows a progress bar.

- Wait for “Successfully installed.” WinGet lists the version it installed.
- Open a new PowerShell 7 window. Run
$PSVersionTable.PSVersionand confirm it matches the version WinGet reported. A window that was open before the update still shows the old version.
According to Microsoft’s PowerShell installation guide, WinGet keeps the package format you already have (MSI or MSIX) when that format is available for the new version. For a quick list of other apps WinGet can update, here’s how to find installed programs in Windows 11.
Install PowerShell 7 If You Only Have Version 5.1
If $PSVersionTable showed 5.1 and you need PowerShell 7, you’re installing a new product, not updating. Run winget install --id Microsoft.PowerShell --source winget. Since version 7.6.0, this installs the MSIX package by default. If you need the traditional MSI version (for example, for remoting or all-user settings), run winget install --id Microsoft.PowerShell --source winget --installer-type wix instead.
When it finishes, search Start for PowerShell 7 or run pwsh in a new window. If a new window says pwsh is not recognized, check whether the PowerShell 7 folder is listed in your Path in the Windows 11 environment variables window.
Keep Windows PowerShell available for older scripts or modules that require it. Typing powershell.exe opens Windows PowerShell 5.1, and pwsh.exe opens PowerShell 7. For more on the difference, see Microsoft’s Windows PowerShell update-message FAQ.
Some admin modules, such as the Active Directory module, come from the RSAT tools for Windows 11 rather than from a PowerShell update.
Other Ways to Update PowerShell 7
Microsoft Store
The Store version of PowerShell updates itself automatically. To update right away, open Microsoft Store, select Library in the lower-left corner, and select Get updates. If the Store is missing or won’t open, follow these Microsoft Store troubleshooting steps.
The Store and MSIX version is installed for your account only and runs in a protected app folder. It doesn’t support PowerShell remoting through WinRM and can’t change machine-wide settings such as Set-ExecutionPolicy -Scope LocalMachine. Use the MSI if you need those.
Download a newer MSI installer
- Close all PowerShell 7 windows.
- Open the PowerShell releases page on GitHub, which Microsoft’s install guide links to.
- Under Assets, download PowerShell-7.6.6-win-x64.msi for most PCs, or the win-arm64.msi file for an Arm PC such as a Snapdragon laptop.
- Double-click the file and select Next through the setup screens. Leave the option that adds PowerShell to the Path environment variable turned on, and check both Microsoft Update boxes if you want future updates to arrive automatically.

- Select Install, approve the prompt, then select Finish. The new stable version replaces the older one in the same folder.
Starting with PowerShell 7.7 there is no MSI package, so later releases will come as MSIX packages only.
Microsoft Update (MSI installs only)
An MSI install can receive PowerShell 7 updates along with your other Windows updates. Microsoft’s Microsoft Update for PowerShell FAQ explains the two check boxes in setup: the first lets PowerShell receive updates, and the second turns on Microsoft Update for other Microsoft software. Check both.
To turn on the system part later, open Settings > Windows Update > Advanced options and turn on Receive updates for other Microsoft products. The steps for updating other Microsoft products when you update Windows walk through that switch.
Keep these limits in mind:
- A new release can take up to two weeks to appear, and Microsoft doesn’t guarantee that timing. It’s delivered as an optional update, even when it contains a security fix.
- Microsoft Update keeps you on your current release line. If you run 7.4, it offers 7.4 updates and won’t jump you to 7.6 for you while 7.4 is supported. Use WinGet or a new MSI to move up now.
- On a work PC, Group Policy, WSUS, or Configuration Manager can override the setup check boxes.
ZIP or .NET tool installs
For a ZIP install, download the new ZIP from the GitHub releases page, extract it to a new folder, and point your shortcuts and Path entry to it. ZIP installs don’t update on their own and don’t add a Start menu shortcut. For a .NET global tool install, run dotnet tool update --global PowerShell. Then check $PSVersionTable.PSVersion.
Update Built-In Windows PowerShell 5.1
Open Settings > Windows Update, select Check for updates, and restart when asked after saving your work. Windows PowerShell 5.1 is a Windows component that is no longer being developed and receives only security updates through Windows Update. There is no separate download, and its build number changes with your Windows build.
Every Windows PowerShell 5.1 window shows a message inviting you to install the latest PowerShell. It appears even on a fully updated PC and doesn’t mean anything is missing. To start without it, run powershell.exe -NoLogo.
When WinGet Isn’t Recognized or Finds Nothing
“winget is not recognized”
WinGet comes with App Installer, which Microsoft Store keeps updated. Open Microsoft Store, search for App Installer, and install or update it. On a brand-new user account, Windows may still be registering WinGet; Microsoft’s WinGet setup guide gives this command to request registration from PowerShell: Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe. Then open a new window and try again. If WinGet still won’t work, use the Store or MSI method instead.
WinGet finds no installed package or no upgrade
WinGet can only update installs it recognizes. A ZIP copy, a .NET tool install, or an IT-deployed copy uses its own method. A “no upgrade” message can also mean you already have the newest version, so compare your version with the table above.
“A newer version was found, but the install technology is different”
This means the new version uses a different package format from the one you have, usually MSI versus MSIX. Uninstall PowerShell 7 with winget uninstall --id Microsoft.PowerShell, then install it again with the WinGet install command above (add --installer-type wix if you want the MSI).
The MSI installer says files are in use
A PowerShell 7 window or Terminal tab is still open. Close them all, or let setup finish and restart when it asks. If you started the MSI from PowerShell 7, closing that window can close setup too, so start the MSI from File Explorer instead.
The version still says 5.1
You’re in Windows PowerShell, not PowerShell 7. Open PowerShell 7 from Start. If Windows Terminal always opens Windows PowerShell, open Terminal, press Ctrl + , to open Settings, select Startup, change Default profile to PowerShell, and select Save.
Confirm the Update and Undo It if Needed
Open a new PowerShell 7 window, run $PSVersionTable.PSVersion, and then run a script you use often to make sure it still works. Releases within the same line, such as 7.6.5 to 7.6.6, are fix updates. Moving from 7.4 or 7.5 to 7.6 can change behavior, so test important scripts first.
To go back, uninstall PowerShell 7 from Settings > Apps > Installed apps or with the tool you installed it with, then install the version you need. With WinGet, add --version and the version number to the install command. Never delete Windows PowerShell system files.
PowerShell Update Questions
Can I upgrade Windows PowerShell 5.1 to PowerShell 7?
No. They’re separate products. PowerShell 7 installs in its own folder and runs alongside 5.1, which stays on Windows and keeps receiving security fixes through Windows Update.
Does PowerShell 7 update automatically?
Only in some cases. The Microsoft Store version updates itself, and an MSI install updates through Microsoft Update if you checked the update boxes during setup. WinGet, ZIP, and .NET tool installs update when you run the update command.
Will Update-Module update PowerShell itself?
No. Update-Module updates modules you installed from the PowerShell Gallery. Update-Module -Name PowerShellGet updates only the PowerShellGet module.
Do I need administrator rights?
For the MSI, yes, because it installs into Program Files for all users, and you’ll see a User Account Control prompt. The MSIX package (the Store version, and the WinGet default since 7.6.0) installs for your account only and usually doesn’t need an administrator.
Should I install the preview version?
Only if you want to test upcoming features. The 7.7 preview installs alongside the stable version, in its own folder, and Microsoft Update never moves a preview to a stable release.
If you use Command Prompt alongside PowerShell, here’s every way to open Command Prompt in Windows 11.

Matthew Burleigh is the founder, head writer, and editor of Solve Your Tech, which he launched in 2012. He has written technology tutorials since 2008 and worked in IT since 2003, including small-business support, IT management, and consulting. He holds Bachelor’s and Master’s degrees in Computer Science from Arizona State University.
Matthew writes practical guides for Windows, iPhone and iPad, Microsoft Office, Outlook, Google apps, and Android. Solve Your Tech’s guides are checked step by step against the device or app maker’s own documentation and tested on his own devices whenever he has the hardware or software, with clear steps, sources, and update dates.
Read more about Matthew and how Solve Your Tech writes and updates its guides, or report a correction.