PowerShell 7.7 is out, and it brings one change that catches many Windows users off guard: Microsoft no longer ships an MSI installer for it. If you used to grab the .msi file from GitHub and click through a setup wizard, that route is closed for this release. You now install PowerShell 7.7 through an MSIX package, either by hand, through the Microsoft Store, or with a single winget command.
This guide walks you through all three methods on Windows 11, shows you how to confirm the version, and explains the MSIX limits you should know about before you rely on it for remoting or system-wide settings.
What's New in PowerShell 7.7 for Windows 11 Users
PowerShell 7.7 runs on .NET 11 and works on Windows, Linux and macOS, including ARM64 hardware such as Windows on ARM laptops. Key additions include:
- New-TemporaryDirectory, a new cmdlet that creates a temp folder in one step
- Join-Path -Extension, which lets you set or swap a file extension while building a path
- -ExcludeProperty support in formatting cmdlets, so you can hide specific columns from output
- New-Guid now returns time-sortable version 7 UUIDs by default instead of random version 4 values
- Security hardening for Constrained Language Mode, remoting and JSON schema validation
- Fixes for tab completion, file handling and the interactive console
Microsoft also lists breaking changes in this release, so test your existing scripts before you roll 7.7 into production.
PowerShell 7.7 vs 7.6 LTS: Which One Should You Install?
PowerShell follows two support tracks. Long-Term Support (LTS) builds get fixes for a longer period and suit servers and business machines. Standard Term Support (STS) builds arrive faster with new features but drop out of support sooner.
| Release | Track | Best for |
|---|---|---|
| PowerShell 7.7 | STS | Users who want the newest cmdlets and fixes |
| PowerShell 7.6 | LTS | Production, enterprise and long-lived scripts |
If you manage servers that need the MSI package or inbound remoting, stay on 7.6 LTS for now.
Why Microsoft Removed the MSI Installer in PowerShell 7.7
Earlier releases offered an MSI package that installed for all users, supported silent deployment and allowed remoting. PowerShell 7.7 drops that file entirely. Microsoft now treats MSIX as the main package for Windows, and winget, the Store and the GitHub download all deliver it.
This matters for two groups. Home and everyday users lose nothing, since MSIX installs cleanly with one click. Admins who depend on the MSI for server rollouts, all-users profiles or inbound remoting need a plan. You can keep PowerShell 7.6 LTS on its MSI, or run a ZIP build from a separate folder. The limits section below explains exactly what the MSIX package blocks.
PowerShell 7.7 System Requirements on Windows 11
Check these points before you start:
- Windows 11 (and supported Windows 10 builds) on x64 or ARM64 hardware.
- Winget, which comes built into Windows 11 through App Installer. You need nothing extra for the winget method.
- No admin rights for most installs, because the MSIX package installs for the current user only.
- Free disk space for the package and a working internet connection.
PowerShell 7.7 does not replace Windows PowerShell 5.1. Both stay on your PC and run side by side.
How to Install PowerShell 7.7 on Windows 11 With Winget
Winget is the fastest option and the one Microsoft recommends for client PCs.
- Right-click the Start button and choose Terminal. You can also open Command Prompt from Start.
- Check which version winget can see:
winget search --id Microsoft.PowerShell --exact- Install the stable package:
winget install --id Microsoft.PowerShell --source winget- Approve the prompt if Windows asks for permission, then wait for the Successfully installed message.
- Close the window and open a fresh one so the new command becomes available.
Since PowerShell 7.7, winget pulls only the MSIX package. The old --installer-type wix switch no longer gives you an MSI for this version.
If winget reports "No available upgrade found," your PC already runs the newest release.
How to Install PowerShell 7.7 From the Microsoft Store
The Store version also uses MSIX and keeps itself up to date in the background.
- Open Microsoft Store from the Start menu.
- Search for PowerShell and open the listing published by Microsoft.
- Click Get (or Install).
- When the download finishes, click Open, or launch PowerShell 7 from Start.
Pick this route if you want hands-off automatic updates and don't plan to use the PC as a remoting target.
How to Install PowerShell 7.7 Manually With the MSIX Bundle
Use this method if you prefer to download the file yourself, or if you need to install on a machine without Store access.
- Visit the PowerShell releases page on GitHub.
- Locate the v7.7.0 release and expand Assets. Click Show all assets if the list looks short.
- Download PowerShell-7.7.0.msixbundle.
- Open your Downloads folder and double-click the file.
- Click Install in the App Installer window.
You can also install the bundle from a terminal opened in your Downloads folder:
Add-AppxPackage -Path ".\PowerShell-7.7.0.msixbundle"How to Open PowerShell 7.7 (pwsh vs powershell.exe)
Windows PowerShell opens with powershell.exe. PowerShell 7 opens with pwsh.exe. You have several ways to launch the new shell:
- Open Start, type PowerShell 7, and select it. The new version uses a black icon, while Windows PowerShell 5.1 keeps its blue icon.
- Press Win + R, type
pwsh, and press Enter. - Type
pwshinside Command Prompt or Windows PowerShell to switch shells in the same window. - In Windows Terminal, click the down arrow next to the tabs and choose PowerShell.
How to Check Your PowerShell 7.7 Version
Open a new PowerShell 7 window and run:
$PSVersionTableCheck the PSVersion line. It should read 7.7.0, and PSEdition should read Core. If you see 5.1 and Desktop, you opened Windows PowerShell by mistake.
To see where the current session runs from, type:
$PSHOMEA path that starts with C:\Program Files\WindowsApps\ confirms an MSIX install.
Once 7.7 runs, put it to work. You can install the Exchange Online PowerShell module, explore the Microsoft Graph command line tools, or try these PowerShell commands to clean up Windows.
Why Does Windows Still Show PowerShell 5.1?
Installing PowerShell 7.7 never upgrades the built-in Windows PowerShell. The old engine stays in its own folder and keeps working, so your existing scripts and tools that call powershell.exe run as before. Microsoft updates 5.1 only through Windows Update.
If a window reports version 5.1, you launched the old shell. Open the PowerShell 7 entry from Start or type pwsh to reach the new one. An already open session also keeps its loaded version until you close and reopen it.
How to Set PowerShell 7.7 as the Default in Windows Terminal
Windows Terminal adds a PowerShell 7 profile on its own, but new tabs keep opening the old default until you change it.
- Open Windows Terminal.
- Click the down arrow next to the tabs and select Settings.
- Go to Startup.
- Under Default profile, choose PowerShell (not Windows PowerShell).
- Click Save.
New tabs now start in PowerShell 7.7.
MSIX Limitations: Remoting, All-Users Profiles and Execution Policy
The MSIX format runs PowerShell inside an app container that blocks writes to its own install folder ($PSHOME). That design causes a few restrictions:
- No inbound remoting. Other machines can't open WSMan remote sessions into an MSIX install. Outbound SSH remoting still works.
- No all-users profiles. You can't create
$PROFILE.AllUsersAllHostsor$PROFILE.AllUsersCurrentHost. Current-user profiles work fine. - Single user only. Each Windows account needs its own install.
- These commands fail because they need write access to
$PSHOME: Register-PSSessionConfigurationUpdate-Help -Scope AllUsersEnable-ExperimentalFeature -Scope AllUsersSet-ExecutionPolicy -Scope LocalMachine
If your work depends on any of these, keep PowerShell 7.6 LTS installed through its MSI package, or use the ZIP build in a separate folder. Microsoft covers the details in its PowerShell installation documentation.
How to Update PowerShell 7.7 on Windows 11
Always update with the same method you used to install. For winget installs, run:
winget list --id Microsoft.PowerShell --upgrade-available
winget upgrade --id Microsoft.PowerShellThe first command tells you if a newer build exists. The second installs it. Close any open PowerShell 7 windows first. Store installs update on their own.
How to Uninstall PowerShell 7.7
- Winget: run
winget uninstall --id Microsoft.PowerShell. - Store or MSIX bundle: open Start, search PowerShell 7, right-click it and choose Uninstall.
Windows PowerShell 5.1 stays on your PC after you remove PowerShell 7.
PowerShell 7.7 Install Not Working? Fixes for Winget, pwsh and Version Errors
Winget isn't recognized. Make sure App Installer is present, or follow our guide to install WinGet in PowerShell. Then register it from Windows PowerShell:
Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbweReopen the terminal and try the install command again.
pwsh isn't recognized after install. Close every terminal window and open a new one. Open sessions don't pick up new commands until you restart them.
The MSI file is missing from GitHub. That is expected. PowerShell 7.7 ships without an MSI, so download the .msixbundle file instead.
Remoting or Set-ExecutionPolicy -Scope LocalMachine fails. The MSIX sandbox blocks these actions. Install PowerShell 7.6 LTS from its MSI package if you need them.
Frequently Asked Questions
Does Microsoft still offer an MSI installer for PowerShell 7.7?
No. Starting with 7.7, Microsoft ships PowerShell for Windows as an MSIX package only. Winget, the Store and the GitHub download all deliver MSIX.
Is PowerShell 7.7 an LTS release?
No. PowerShell 7.7 is a Standard Term Support release. PowerShell 7.6 holds the current LTS slot.
Will installing PowerShell 7.7 remove Windows PowerShell 5.1?
No. Both versions live in separate folders, use separate profiles and run side by side.
Do I need admin rights to install PowerShell 7.7?
The MSIX package installs for your user account, so you usually don't need an elevated prompt for winget or the Store.
Can I install PowerShell 7.7 on Windows 10?
Yes. The same winget, Store and MSIX steps work on supported Windows 10 builds. You can also install PowerShell 7 on Windows 10 and 11 with our stable release guide.
How do I check which PowerShell version I'm running?
Run $PSVersionTable and read the PSVersion value. For PowerShell 7.7, it shows 7.7.0.
Related Guides
- How to Install PowerShell 7 on Windows 10 and 11
- How to Install WinGet in PowerShell
- PowerShell Commands to Clean Up Windows and Speed It Up Without a Cleaner App
- How to Allow an App Through Windows 11 Firewall (Security, Settings, PowerShell)
- PowerShell for macOS Is Now Notarized: No More GateKeeper Warnings
