Installing PowerShell on Windows
There are multiple ways to install PowerShell in Windows. Each install method is designed to support different scenarios and workflows. Choose the method that best suits your needs.
- Winget - Recommended way to install PowerShell on Windows clients
- MSI package - Best choice for Windows Servers and enterprise deployment scenarios
- ZIP package - Easiest way to "side load" or install multiple versions
- Use this method for Windows Nano Server, Windows IoT, and Arm-based systems
- .NET Global tool - A good choice for .NET developers that install and use other global tools
- Microsoft Store package - An easy way to install for casual users of PowerShell but has limitations
The installation commands in this article are for the latest stable release of PowerShell. To install a different version of PowerShell, adjust the command to match the version you need. The following links direct you to the release page for each version in the PowerShell repository on GitHub.
- Stable release: https://aka.ms/powershell-release?tag=stable
- LTS release: https://aka.ms/powershell-release?tag=lts
- Preview release: https://aka.ms/powershell-release?tag=preview
Download links for every package are found in the Assets section of the Release page. The Assets section may be collapsed, so you may need to click to expand it.
Install PowerShell using Winget (recommended)
Winget, the Windows Package Manager, is a command-line tool enables users to discover, install,
upgrade, remove, and configure applications on Windows client computers. This tool is the client
interface to the Windows Package Manager service. The
winget command-line tool is bundled with
Windows 11 and modern versions of Windows 10 by default as the App Installer.
See the winget documentation for a list of system requirements and install instructions.
Winget doesn't currently run on Windows servers.
The following commands can be used to install PowerShell using the published
Search for the latest version of PowerShell
winget search Microsoft.PowerShell
Name Id Version Source -------------------------------------------------------------- PowerShell Microsoft.PowerShell 220.127.116.11 winget PowerShell Preview Microsoft.PowerShell.Preview 18.104.22.168 winget
Install PowerShell or PowerShell Preview using the
winget install --id Microsoft.Powershell --source winget winget install --id Microsoft.Powershell.Preview --source winget
On Windows systems using X86 or X64 processor,
winget installs the MSI package. On systems using
the Arm64 processor,
winget install the Microsoft Store (MSIX) package. For more information,
see Installing from the Microsoft Store.
Installing the MSI package
To install PowerShell on Windows, use the following links to download the install package from GitHub.
Once downloaded, double-click the installer file and follow the prompts.
The installer creates a shortcut in the Windows Start Menu.
- By default the package is installed to
- You can launch PowerShell via the Start Menu or
PowerShell 7.3 installs to a new directory and runs side-by-side with Windows PowerShell 5.1. PowerShell 7.3 is an in-place upgrade that replaces PowerShell 7.0 and lower.
- PowerShell 7.3 is installed to
$env:ProgramFiles\PowerShell\7folder is added to
- Folders for previously released versions are deleted
If you need to run PowerShell 7.3 side-by-side with other versions, use the ZIP install method to install the other version to a different folder.
Support for Microsoft Update in PowerShell 7.2 and newer
PowerShell 7.2 and newer has support for Microsoft Update. When you enable this feature, you'll get the latest PowerShell 7 updates in your traditional Microsoft Update (MU) management flow, whether that's with Windows Update for Business, WSUS, Microsoft Endpoint Configuration Manager, or the interactive MU dialog in Settings.
The PowerShell 7.3 MSI package includes following command-line options:
USE_MU- This property has two possible values:
1(default) - Opts into updating through Microsoft Update, WSUS, or Configuration Manager
0- Don't opt into updating through Microsoft Update, WSUS, or Configuration Manager
1(default) - Opts into using Microsoft Update for Automatic Updates
0- Don't opt into using Microsoft Update
Enabling updates may have been set in a previous installation or manual configuration. Using
ENABLE_MU=0 doesn't remove the existing settings. Also, this setting can be overruled by Group
Policy settings controlled by your administrator.
For more information, see the PowerShell Microsoft Update FAQ.
Install the MSI package from the command line
MSI packages can be installed from the command line allowing administrators to deploy packages without user interaction. The MSI package includes the following properties to control the installation options:
ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL- This property controls the option for adding the
Open PowerShellitem to the context menu in Windows Explorer.
ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL- This property controls the option for adding the
Run with PowerShellitem to the context menu in Windows Explorer.
ENABLE_PSREMOTING- This property controls the option for enabling PowerShell remoting during installation.
REGISTER_MANIFEST- This property controls the option for registering the Windows Event Logging manifest.
ADD_PATH- This property controls the option for adding PowerShell to the Windows PATH environment variable.
DISABLE_TELEMETRY- This property controls the option for disabling PowerShell's telemetry by setting the
The following example shows how to silently install PowerShell with all the install options enabled.
msiexec.exe /package PowerShell-7.3.3-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1
For a full list of command-line options for
Command line options.
Installing the ZIP package
PowerShell binary ZIP archives are provided to enable advanced deployment scenarios. Download one of the following ZIP archives from the current release page.
Depending on how you download the file you may need to unblock the file using the
cmdlet. Unzip the contents to the location of your choice and run
pwsh.exe from there. Unlike
installing the MSI packages, installing the ZIP archive doesn't check for prerequisites. For
remoting over WSMan to work properly, ensure that you've met the prerequisites.
Use this method to install the ARM-based version of PowerShell on computers like the Microsoft
Surface Pro X. For best results, install PowerShell to the to
Install as a .NET Global tool
If you already have the .NET Core SDK installed, you can install PowerShell as a .NET Global tool.
dotnet tool install --global PowerShell
The dotnet tool installer adds
$HOME\.dotnet\tools to your
$env:PATH environment variable.
However, the currently running shell doesn't have the updated
$env:PATH. You can start PowerShell
from a new shell by typing
Installing from the Microsoft Store
PowerShell 7.3 can be installed from the Microsoft Store. You can find the PowerShell release in the Microsoft Store site or in the Store application in Windows.
Benefits of the Microsoft Store package:
- Automatic updates built right into Windows
- Integrates with other software distribution mechanisms like Intune and Configuration Manager
- Can install on Windows systems using x86, x64, or Arm64 processors
By default, Windows Store packages run in an application sandbox that virtualizes access to some filesystem and registry locations. Changes to virtualized file and registry locations don't persist outside of the application sandbox.
This sandbox all blocks any changes to the application's root folder. Any system-level configuration
settings stored in
$PSHOME can't be modified. This includes the WSMAN configuration. This prevents
remote sessions from connecting to Store-based installs of PowerShell. User-level configurations and
SSH remoting are supported.
The following commands need write to
$PSHOME. These commands aren't supported in a Microsoft Store
instance of PowerShell.
Update-Help -Scope AllUsers
Enable-ExperimentalFeature -Scope AllUsers
Set-ExecutionPolicy -Scope LocalMachine
For more information, see Understanding how packaged desktop apps run on Windows.
Changes for PowerShell 7.2
Beginning in PowerShell 7.2, the PowerShell package is now exempt from file and registry virtualization. Changes to virtualized file and registry locations now persist outside of the application sandbox. However, changes to the application's root folder are still blocked.
You must be running on Windows build 1903 or higher for this exemption to work.
Installing a preview version
Preview releases of PowerShell 7 install to
$env:ProgramFiles\PowerShell\7-preview so they can be
run side-by-side with non-preview releases of PowerShell. PowerShell 7.4 is the next preview
Upgrading an existing installation
For best results when upgrading, you should use the same install method you used when you first installed PowerShell. Each installation method installs PowerShell in a different location. If you aren't sure how PowerShell was installed, you can compare the installed location with the package information in this article. If you installed via the MSI package, that information appears in the Programs and Features Control Panel.
When upgrading, PowerShell won't upgrade from an LTS version to a non-LTS version. It only upgrades to the latest version of LTS, for example, from 7.2.3 to 7.2.10. To upgrade from an LTS release to a newer stable version or the next LTS, you need to install the new version with the MSI for that release.
When the installed version isn't an LTS version, PowerShell upgrades to the latest stable version.
Deploying on Windows 10 IoT Enterprise
Windows 10 IoT Enterprise comes with Windows PowerShell, which we can use to deploy PowerShell 7.
# Replace the placeholder information for the following variables: $deviceip = '<device ip address' $zipfile = 'PowerShell-7.3.3-win-arm64.zip' $downloadfolder = 'u:\users\administrator\Downloads' # The download location is local to the device. # There should be enough space for the zip file and the unzipped contents. # Create PowerShell session to target device Set-Item -Path WSMan:\localhost\Client\TrustedHosts $deviceip $S = New-PSSession -ComputerName $deviceIp -Credential Administrator # Copy the ZIP package to the device Copy-Item $zipfile -Destination $downloadfolder -ToSession $S #Connect to the device and expand the archive Enter-PSSession $S Set-Location u:\users\administrator\Downloads Expand-Archive .\PowerShell-7.3.3-win-arm64.zip # Set up remoting to PowerShell 7 Set-Location .\PowerShell-7.3.3-win-arm64 # Be sure to use the -PowerShellHome parameter otherwise it tries to create a new # endpoint with Windows PowerShell 5.1 .\Install-PowerShellRemoting.ps1 -PowerShellHome .
When you set up PowerShell Remoting you get an error message and are disconnected from the device. PowerShell has to restart WinRM. Now you can connect to PowerShell 7 endpoint on device.
# Be sure to use the -Configuration parameter. If you omit it, you connect to Windows PowerShell 5.1 Enter-PSSession -ComputerName $deviceIp -Credential Administrator -Configuration PowerShell.7.3.3
Deploying on Windows 10 IoT Core
Windows 10 IoT Core adds Windows PowerShell when you include IOT_POWERSHELL feature, which we can use to deploy PowerShell 7. The steps defined above for Windows 10 IoT Enterprise can be followed for IoT Core as well.
For adding the latest PowerShell in the shipping image, use Import-PSCoreRelease command to include the package in the workarea and add OPENSRC_POWERSHELL feature to your image.
For ARM64 architecture, Windows PowerShell isn't added when you include IOT_POWERSHELL. So the
zip based install doesn't work. You need to use
Import-PSCoreRelease command to add it in
Deploying on Nano Server
These instructions assume that the Nano Server is a "headless" OS that has a version of PowerShell already running on it. For more information, see the Nano Server Image Builder documentation.
PowerShell binaries can be deployed using two different methods.
- Offline - Mount the Nano Server VHD and unzip the contents of the zip file to your chosen location within the mounted image.
- Online - Transfer the zip file over a PowerShell Session and unzip it in your chosen location.
In both cases, you need the Windows x64 ZIP release package. Run the commands within an "Administrator" instance of PowerShell.
Offline Deployment of PowerShell
- Use your favorite zip utility to unzip the package to a directory within the mounted Nano Server image.
- Unmount the image and boot it.
- Connect to the built-in instance of Windows PowerShell.
- Follow the instructions to create a remoting endpoint using the "another instance technique".
Online Deployment of PowerShell
Deploy PowerShell to Nano Server using the following steps.
# Replace the placeholder information for the following variables: $ipaddr = '<Nano Server IP address>' $credential = Get-Credential # <An Administrator account on the system> $zipfile = 'PowerShell-7.3.3-win-x64.zip' # Connect to the built-in instance of Windows PowerShell $session = New-PSSession -ComputerName $ipaddr -Credential $credential # Copy the file to the Nano Server instance Copy-Item $zipfile c:\ -ToSession $session # Enter the interactive remote session Enter-PSSession $session # Extract the ZIP file Expand-Archive -Path C:\PowerShell-7.3.3-win-x64.zip -DestinationPath 'C:\Program Files\PowerShell 7'
If you want WSMan-based remoting, follow the instructions to create a remoting endpoint using the "another instance technique".
PowerShell supports the PowerShell Remoting Protocol (PSRP) over both WSMan and SSH. For more information, see:
The following prerequisites must be met to enable PowerShell remoting over WSMan on older versions of Windows.
- Install the Windows Management Framework (WMF) 5.1 (as necessary). For more information about WMF, see WMF Overview.
- Install the Universal C Runtime on Windows versions predating Windows 10. It's available via direct download or Windows Update. Fully patched systems already have this package installed.
Supported versions of Windows
The following table is a list of PowerShell releases and the versions of Windows they're supported on. These versions are supported until either the version of PowerShell reaches end-of-support or the version of Windows reaches end-of-support.
- The icon indicates that the version of the OS or PowerShell is still supported
- The icon indicates the version of PowerShell is no longer supported on that version of the OS
- The icon indicates that we haven't finished testing PowerShell on that OS
- The icon indicates that the version of the OS or PowerShell isn't supported
- When both the version of the OS and the version of PowerShell have a icon, that combination is supported
|Windows||7.2 (LTS-current)||7.3||7.4 (preview)|
|Windows Server 2016, 2019, or 2022|
|Windows Server 2012 R2|
|Windows Server Core (2012 R2 or higher)|
|Windows Server Nano (1809 or higher)|
|Windows 10 1607+|
Support for a specific version of Windows is determined by the Microsoft Support Lifecycle policies. For more information, see:
PowerShell is supported on Windows for the following processor architectures.
|Windows||7.2 (LTS-current)||7.3||7.4 (preview)|
|Nano Server Version 1803+||x64||x64||x64|
|Windows Server 2012 R2+||x64, x86||x64, x86||x64, x86|
|Windows Server Core 2012 R2+||x64, x86||x64, x86||x64, x86|
|Windows 10 or 11 Client||x64, x86, Arm64||x64, x86, Arm64||x64, x86, Arm64|
You can check the version that you are using by running
Microsoft supports the installation methods in this document. There may be other third-party methods of installation available from other sources. While those tools and methods may work, Microsoft can't support those methods.
Submit and view feedback for