@@ -8,7 +8,7 @@ title: Installing PowerShell on Windows
88There are multiple ways to install PowerShell in Windows. Each install method is designed to support
99different scenarios and workflows. Choose the method that best suits your needs.
1010
11- - [ Winget ] [ 14 ] - Recommended way to install PowerShell on Windows clients
11+ - [ WinGet ] [ 14 ] - Recommended way to install PowerShell on Windows clients
1212- [ MSI package] [ 11 ] - Best choice for Windows Servers and enterprise deployment scenarios
1313- [ ZIP package] [ 15 ] - Easiest way to "side load" or install multiple versions
1414 - 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.
1818
1919[ !INCLUDE [ Latest version] ( ../../includes/latest-install.md )]
2020
21- ## <a id =" winget " >Install PowerShell using Winget (recommended)</a >
21+ ## <a id =" winget " >Install PowerShell using WinGet (recommended)</a >
2222
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,
2424upgrade, remove, and configure applications on Windows client computers. This tool is the client
2525interface to the Windows Package Manager service. The ` winget ` command-line tool is bundled with
2626Windows 11 and modern versions of Windows 10 by default as the ** App Installer** .
2727
2828> [ !NOTE]
2929> 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
3131> Build 26085 and later includes ` winget ` for ** Windows Server with Desktop Experience** only.
3232
3333The following commands can be used to install PowerShell using the published ` winget ` packages:
@@ -229,15 +229,15 @@ session is running.
229229
230230- If the value is ` $HOME\.dotnet\tools ` , PowerShell was installed with the [ .NET Global tool] [ 10 ] .
231231- 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.
233233- 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.
235235- If the value is anything else, it's likely that PowerShell was installed as a [ ZIP package] [ 15 ] .
236236
237237If you installed via the MSI package, that information also appears in the
238238** Programs and Features** Control Panel.
239239
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:
241241
242242``` powershell
243243winget list --name PowerShell --upgrade-available
@@ -382,6 +382,7 @@ can't support those methods.
382382[ 13 ] : #powershell-remoting
383383[ 14 ] : #winget
384384[ 15 ] : #zip
385+ [ 18 ] : https://github.com/PowerShell/PowerShell/releases/latest
385386[ 19 ] : https://github.com/ms-iot/iot-adk-addonkit/blob/master/Tools/IoTCoreImaging/Docs/Import-PSCoreRelease.md#Import-PSCoreRelease
386387[ 20 ] : https://github.com/PowerShell/PowerShell/releases/download/v7.5.0/PowerShell-7.5.0-win-arm64.msi
387388[ 21 ] : https://github.com/PowerShell/PowerShell/releases/download/v7.5.0/PowerShell-7.5.0-win-arm64.zip
0 commit comments