diff --git a/reference/7.4/Microsoft.PowerShell.Core/About/about_Execution_Policies.md b/reference/7.4/Microsoft.PowerShell.Core/About/about_Execution_Policies.md index c8c92bb14c29..3346c4fa2eb6 100644 --- a/reference/7.4/Microsoft.PowerShell.Core/About/about_Execution_Policies.md +++ b/reference/7.4/Microsoft.PowerShell.Core/About/about_Execution_Policies.md @@ -1,7 +1,7 @@ --- description: Describes the PowerShell execution policies and explains how to manage them. Locale: en-US -ms.date: 02/14/2025 +ms.date: 03/13/2025 no-loc: [Bypass, Default, Restricted, Undefined, Unrestricted, Process, Scope, MachinePolicy, about_Group_Policy_Settings] online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.4&WT.mc_id=ps-gethelp schema: 2.0.0 @@ -66,12 +66,11 @@ execution policies are as follows: - `Default` - Sets the default execution policy. - - **Restricted** for Windows clients. - - **RemoteSigned** for Windows servers. + - **RemoteSigned** for Windows clients and servers. - `RemoteSigned` - - The default execution policy for Windows server computers. + - The default execution policy for Windows computers. - Scripts can run. - Requires a digital signature from a trusted publisher on scripts and configuration files that are downloaded from the internet which includes @@ -85,7 +84,6 @@ execution policies are as follows: - `Restricted` - - The default execution policy for Windows client computers. - Permits individual commands, but does not allow scripts. - Prevents running of all script files, including formatting and configuration files (`.ps1xml`), module script files (`.psm1`), and diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Execution_Policies.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Execution_Policies.md index e4f3e3791869..73bb4921dbd4 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_Execution_Policies.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_Execution_Policies.md @@ -1,7 +1,7 @@ --- description: Describes the PowerShell execution policies and explains how to manage them. Locale: en-US -ms.date: 02/14/2025 +ms.date: 03/13/2025 no-loc: [Bypass, Default, Restricted, Undefined, Unrestricted, Process, Scope, MachinePolicy, about_Group_Policy_Settings] online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.5&WT.mc_id=ps-gethelp schema: 2.0.0 @@ -66,12 +66,11 @@ execution policies are as follows: - `Default` - Sets the default execution policy. - - **Restricted** for Windows clients. - - **RemoteSigned** for Windows servers. + - **RemoteSigned** for Windows clients and servers. - `RemoteSigned` - - The default execution policy for Windows server computers. + - The default execution policy for Windows computers. - Scripts can run. - Requires a digital signature from a trusted publisher on scripts and configuration files that are downloaded from the internet which includes @@ -85,7 +84,6 @@ execution policies are as follows: - `Restricted` - - The default execution policy for Windows client computers. - Permits individual commands, but does not allow scripts. - Prevents running of all script files, including formatting and configuration files (`.ps1xml`), module script files (`.psm1`), and diff --git a/reference/7.6/Microsoft.PowerShell.Core/About/about_Execution_Policies.md b/reference/7.6/Microsoft.PowerShell.Core/About/about_Execution_Policies.md index f43cf313e866..9578aae8bebd 100644 --- a/reference/7.6/Microsoft.PowerShell.Core/About/about_Execution_Policies.md +++ b/reference/7.6/Microsoft.PowerShell.Core/About/about_Execution_Policies.md @@ -1,7 +1,7 @@ --- description: Describes the PowerShell execution policies and explains how to manage them. Locale: en-US -ms.date: 02/14/2025 +ms.date: 03/13/2025 no-loc: [Bypass, Default, Restricted, Undefined, Unrestricted, Process, Scope, MachinePolicy, about_Group_Policy_Settings] online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.6&WT.mc_id=ps-gethelp schema: 2.0.0 @@ -66,12 +66,11 @@ execution policies are as follows: - `Default` - Sets the default execution policy. - - **Restricted** for Windows clients. - - **RemoteSigned** for Windows servers. + - **RemoteSigned** for Windows clients and servers. - `RemoteSigned` - - The default execution policy for Windows server computers. + - The default execution policy for Windows computers. - Scripts can run. - Requires a digital signature from a trusted publisher on scripts and configuration files that are downloaded from the internet which includes @@ -85,7 +84,6 @@ execution policies are as follows: - `Restricted` - - The default execution policy for Windows client computers. - Permits individual commands, but does not allow scripts. - Prevents running of all script files, including formatting and configuration files (`.ps1xml`), module script files (`.psm1`), and diff --git a/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md b/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md index a65550b84101..129c9ce04c0a 100644 --- a/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md +++ b/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Windows -ms.date: 01/27/2025 +ms.date: 03/13/2025 title: Installing PowerShell on Windows --- # Installing PowerShell on Windows @@ -240,19 +240,15 @@ If you installed via the MSI package, that information also appears in the To determine whether PowerShell may be upgraded with WinGet, run the following command: ```powershell -winget list --name PowerShell --upgrade-available +winget list --id Microsoft.PowerShell --upgrade-available ``` -If there is an available upgrade, the output indicates the latest available version. +If there is an available upgrade, the output indicates the latest available version. Use the +following command to upgrade PowerShell using WinGet: -> [!NOTE] -> 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.4.3 to 7.4.7. 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. +```powershell +winget upgrade --id Microsoft.PowerShell +``` ## Deploying on Windows 10 IoT Enterprise