@@ -91,7 +91,7 @@ Latest stable release:
9191
9292Once downloaded, double-click the installer file and follow the prompts.
9393
94- ### Install the MSI package from the command line
94+ ### Install the MSI package with command- line options
9595
9696MSI packages can be installed from the command line allowing administrators to deploy packages
9797without user interaction. The MSI package includes the following properties to control the
@@ -131,7 +131,7 @@ The following example shows how to silently install PowerShell with all the inst
131131
132132``` powershell
133133$msiParams = @(
134- '/package PowerShell-7.6.0 -win-x64.msi'
134+ '/package PowerShell-7.6.1 -win-x64.msi'
135135 '/quiet'
136136 'ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1'
137137 'ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1'
@@ -141,12 +141,12 @@ $msiParams = @(
141141 'ENABLE_MU=1'
142142 'ADD_PATH=1'
143143)
144- msiexec.exe @msiParams`
144+ msiexec.exe @msiParams
145145```
146146
147147For a full list of command-line options for ` Msiexec.exe ` , see [ Command line options] [ 05 ] .
148148
149- ### Install from the ZIP package
149+ ### Install the ZIP package
150150
151151<a id =" zip " ></a >PowerShell binary ZIP archives are provided to enable advanced deployment scenarios.
152152Download one of the following ZIP archives from the [ current release] [ 21 ] page.
@@ -178,7 +178,7 @@ The dotnet tool installer adds `$HOME\.dotnet\tools` to your `$Env:PATH` environ
178178However, the currently running shell doesn't have the updated ` $Env:PATH ` . You can start PowerShell
179179from a new shell by typing ` pwsh ` .
180180
181- ### Install using the MSIX package
181+ ### Install the MSIX package
182182
183183<a id =" msstore " ></a >PowerShell can be installed from the [ Microsoft Store] [ 22 ] or by manually
184184downloading the MSIX package.
@@ -196,7 +196,7 @@ releases page and double-click the file to install it.
196196- Latest stable - [ PowerShell-7.5.6.msixbundle] [ 14 ]
197197- Previous LTS - [ PowerShell-7.4.15.msixbundle] [ 13 ]
198198
199- Alternately , you can use the following command to install the MSIX package from the command line:
199+ Alternatively , you can use the following command to install the MSIX package from the command line:
200200
201201``` powershell
202202Add-AppxPackage -Path ".\PowerShell-7.6.1.msixbundle"
@@ -278,8 +278,9 @@ If you aren't sure how PowerShell was installed, you can check the value of the
278278which always points to the directory containing PowerShell that the current session is running.
279279
280280- If the value is ` $HOME\.dotnet\tools ` , PowerShell was installed with the [ .NET Global tool] [ 08 ] .
281- - If the value is ` $Env:ProgramFiles\PowerShell\7 ` , PowerShell was installed using the
282- [ MSI package] [ 09 ] . You can verify this by checking the ** Programs and Features** Control Panel.
281+ - If the value is ` $Env:ProgramFiles\PowerShell\7 ` , PowerShell was probably installed using the [ MSI
282+ package] [ 09 ] . You can verify this by looking for PowerShell in the ** Programs and Features**
283+ Control Panel.
283284- If the value starts with ` $Env:ProgramFiles\WindowsApps\ ` , PowerShell was installed using the
284285 [ MSIX package] [ 10 ] .
285286- If the value is anything else, it's likely that PowerShell was installed as a [ ZIP package] [ 12 ] .
@@ -297,6 +298,10 @@ following command to upgrade PowerShell using WinGet:
297298winget upgrade --id Microsoft.PowerShell
298299```
299300
301+ If available in the new version, Winget uses the same package format (MSI or MSIX) that was used to
302+ install the current version of PowerShell. Alternatively, you can manually download and install
303+ the package you want.
304+
300305## Uninstall PowerShell 7
301306
302307The process of uninstalling PowerShell 7 depends on the installation method you used.
0 commit comments