@@ -8,7 +8,7 @@ title: Installing PowerShell on Windows
8
8
There are multiple ways to install PowerShell in Windows. Each install method is designed to support
9
9
different scenarios and workflows. Choose the method that best suits your needs.
10
10
11
- - [ Winget ] [ 14 ] - Recommended way to install PowerShell on Windows clients
11
+ - [ WinGet ] [ 14 ] - Recommended way to install PowerShell on Windows clients
12
12
- [ MSI package] [ 11 ] - Best choice for Windows Servers and enterprise deployment scenarios
13
13
- [ ZIP package] [ 15 ] - Easiest way to "side load" or install multiple versions
14
14
- Use this method for Windows Nano Server, Windows IoT, and Arm-based systems
@@ -18,16 +18,16 @@ different scenarios and workflows. Choose the method that best suits your needs.
18
18
19
19
[ !INCLUDE [ Latest version] ( ../../includes/latest-install.md )]
20
20
21
- ## <a id =" winget " >Install PowerShell using Winget (recommended)</a >
21
+ ## <a id =" winget " >Install PowerShell using WinGet (recommended)</a >
22
22
23
- Winget , the Windows Package Manager, is a command-line tool enables users to discover, install,
23
+ WinGet , the Windows Package Manager, is a command-line tool enables users to discover, install,
24
24
upgrade, remove, and configure applications on Windows client computers. This tool is the client
25
25
interface to the Windows Package Manager service. The ` winget ` command-line tool is bundled with
26
26
Windows 11 and modern versions of Windows 10 by default as the ** App Installer** .
27
27
28
28
> [ !NOTE]
29
29
> See the [ winget documentation] [ 09 ] for a list of system requirements and install instructions.
30
- > ` Winget ` isn't available on Windows Server 2022 or earlier versions. Windows Server 2025 Preview
30
+ > ` winget ` isn't available on Windows Server 2022 or earlier versions. Windows Server 2025 Preview
31
31
> Build 26085 and later includes ` winget ` for ** Windows Server with Desktop Experience** only.
32
32
33
33
The following commands can be used to install PowerShell using the published ` winget ` packages:
@@ -229,15 +229,15 @@ session is running.
229
229
230
230
- If the value is ` $HOME\.dotnet\tools ` , PowerShell was installed with the [ .NET Global tool] [ 10 ] .
231
231
- If the value is ` $Env:ProgramFiles\PowerShell\7 ` , PowerShell was installed as an
232
- [ MSI package] [ 11 ] or with [ Winget ] [ 14 ] on a computer with an X86 or x64 processor.
232
+ [ MSI package] [ 11 ] or with [ WinGet ] [ 14 ] on a computer with an X86 or x64 processor.
233
233
- If the value starts with ` $Env:ProgramFiles\WindowsApps\ ` , PowerShell was installed as a
234
- [ Microsoft Store package] [ 12 ] or with [ Winget ] [ 14 ] on computer with an ARM processor.
234
+ [ Microsoft Store package] [ 12 ] or with [ WinGet ] [ 14 ] on computer with an ARM processor.
235
235
- If the value is anything else, it's likely that PowerShell was installed as a [ ZIP package] [ 15 ] .
236
236
237
237
If you installed via the MSI package, that information also appears in the
238
238
** Programs and Features** Control Panel.
239
239
240
- To determine whether PowerShell may be upgraded with Winget , run the following command:
240
+ To determine whether PowerShell may be upgraded with WinGet , run the following command:
241
241
242
242
``` powershell
243
243
winget list --name PowerShell --upgrade-available
@@ -382,6 +382,7 @@ can't support those methods.
382
382
[ 13 ] : #powershell-remoting
383
383
[ 14 ] : #winget
384
384
[ 15 ] : #zip
385
+ [ 18 ] : https://github.com/PowerShell/PowerShell/releases/latest
385
386
[ 19 ] : https://github.com/ms-iot/iot-adk-addonkit/blob/master/Tools/IoTCoreImaging/Docs/Import-PSCoreRelease.md#Import-PSCoreRelease
386
387
[ 20 ] : https://github.com/PowerShell/PowerShell/releases/download/v7.5.0/PowerShell-7.5.0-win-arm64.msi
387
388
[ 21 ] : https://github.com/PowerShell/PowerShell/releases/download/v7.5.0/PowerShell-7.5.0-win-arm64.zip
0 commit comments