| Service | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| Microsoft.PowerShell.Core | About Signing (5.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/5.1/Microsoft.PowerShell.Core/About/about_Signing.md | --- description: Explains how to sign scripts so that they comply with the PowerShell execution policies. Locale: en-US Previously updated : 01/21/2022 Last updated : 03/14/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-5.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Signing If PowerShell displays this message when you run a script that you did not write, treat the file as you would treat any unsigned script. Review the code to determine whether you can trust the script. -## Enable strong private key protection for your certificate +## Enable strong protection for your private key -If you have a private certificate on your computer, malicious programs might be +If you have a private key and certificate on your computer, malicious programs might be able to sign scripts on your behalf, which authorizes PowerShell to run them. To prevent automated signing on your behalf, use Certificate Manager-`Certmgr.exe` to export your signing certificate to a `.pfx` file. Certificate +`Certmgr.exe` to export your signing key and certificate to a `.pfx` file. Certificate Manager is included in the Microsoft .NET SDK, the Microsoft Windows SDK, and-in internet Explorer. +in Internet Explorer. To export the certificate: |
| Microsoft.PowerShell.Core | About Signing (7.0) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.0/Microsoft.PowerShell.Core/About/about_Signing.md | --- description: Explains how to sign scripts so that they comply with the PowerShell execution policies. Locale: en-US Previously updated : 03/07/2022 Last updated : 03/14/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Signing If PowerShell displays this message when you run a script that you did not write, treat the file as you would treat any unsigned script. Review the code to determine whether you can trust the script. -## Enable strong private key protection for your certificate +## Enable strong protection for your private key -If you have a private certificate on your computer, malicious programs might be +If you have a private key and certificate on your computer, malicious programs might be able to sign scripts on your behalf, which authorizes PowerShell to run them. To prevent automated signing on your behalf, use Certificate Manager-`Certmgr.exe` to export your signing certificate to a `.pfx` file. Certificate +`Certmgr.exe` to export your signing key and certificate to a `.pfx` file. Certificate Manager is included in the Microsoft .NET SDK, the Microsoft Windows SDK, and-in internet Explorer. +in Internet Explorer. To export the certificate: |
| Microsoft.PowerShell.Core | About Signing (7.1) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.1/Microsoft.PowerShell.Core/About/about_Signing.md | --- description: Explains how to sign scripts so that they comply with the PowerShell execution policies. Locale: en-US Previously updated : 03/07/2022 Last updated : 03/14/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.1&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Signing If PowerShell displays this message when you run a script that you did not write, treat the file as you would treat any unsigned script. Review the code to determine whether you can trust the script. -## Enable strong private key protection for your certificate +## Enable strong protection for your private key -If you have a private certificate on your computer, malicious programs might be +If you have a private key and certificate on your computer, malicious programs might be able to sign scripts on your behalf, which authorizes PowerShell to run them. To prevent automated signing on your behalf, use Certificate Manager-`Certmgr.exe` to export your signing certificate to a `.pfx` file. Certificate +`Certmgr.exe` to export your signing key and certificate to a `.pfx` file. Certificate Manager is included in the Microsoft .NET SDK, the Microsoft Windows SDK, and-in internet Explorer. +in Internet Explorer. To export the certificate: |
| Microsoft.PowerShell.Core | About Signing (7.2) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.2/Microsoft.PowerShell.Core/About/about_Signing.md | --- description: Explains how to sign scripts so that they comply with the PowerShell execution policies. Locale: en-US Previously updated : 03/07/2022 Last updated : 03/14/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.2&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Signing If PowerShell displays this message when you run a script that you did not write, treat the file as you would treat any unsigned script. Review the code to determine whether you can trust the script. -## Enable strong private key protection for your certificate +## Enable strong protection for your private key -If you have a private certificate on your computer, malicious programs might be +If you have a private key and certificate on your computer, malicious programs might be able to sign scripts on your behalf, which authorizes PowerShell to run them. To prevent automated signing on your behalf, use Certificate Manager-`Certmgr.exe` to export your signing certificate to a `.pfx` file. Certificate +`Certmgr.exe` to export your signing key and certificate to a `.pfx` file. Certificate Manager is included in the Microsoft .NET SDK, the Microsoft Windows SDK, and-in internet Explorer. +in Internet Explorer. To export the certificate: |
| Microsoft.PowerShell.Core | About Signing (7.3) | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/7.3/Microsoft.PowerShell.Core/About/about_Signing.md | --- description: Explains how to sign scripts so that they comply with the PowerShell execution policies. Locale: en-US Previously updated : 03/07/2022 Last updated : 03/14/2022 online version: https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_signing?view=powershell-7.3&WT.mc_id=ps-gethelp schema: 2.0.0 Title: about Signing If PowerShell displays this message when you run a script that you did not write, treat the file as you would treat any unsigned script. Review the code to determine whether you can trust the script. -## Enable strong private key protection for your certificate +## Enable strong protection for your private key -If you have a private certificate on your computer, malicious programs might be +If you have a private key and certificate on your computer, malicious programs might be able to sign scripts on your behalf, which authorizes PowerShell to run them. To prevent automated signing on your behalf, use Certificate Manager-`Certmgr.exe` to export your signing certificate to a `.pfx` file. Certificate +`Certmgr.exe` to export your signing key and certificate to a `.pfx` file. Certificate Manager is included in the Microsoft .NET SDK, the Microsoft Windows SDK, and-in internet Explorer. +in Internet Explorer. To export the certificate: |
| install | Installing Powershell On Macos | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/install/Installing-PowerShell-on-macOS.md | From the command line 1. Run `sudo xattr -rd com.apple.quarantine powershell-7.2.1-osx-x64.pkg`. Include the full path to the `.pkg` file.-1. Install the package as you normally wou +1. Install the package as you normally would. > [!NOTE] > This is a known issue related to package notarization that will be addressed in the future. |
| whats-new | What S New In Powershell 73 | https://github.com/MicrosoftDocs/PowerShell-Docs/commits/staging/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-73.md | --- Title: What's New in PowerShell 7.3-preview.1 description: New features and changes released in PowerShell 7.3-preview.1 Previously updated : 02/09/2022 Last updated : 03/14/2022 --- # What's New in PowerShell 7.3 PowerShell 7.3 is the next preview release, built on .NET 6.0. PowerShell 7.3-preview.1 includes the following features, updates, and breaking changes. +Improved error handling + - Set `$?` correctly for command expression with redirections (#16046) - Fix a casting error when using `$PSNativeCommandUseErrorActionPreference` (#15993) - Make the native command error handling optionally honor `ErrorActionPreference` (#15897)+- Specify the executable path as `TargetObject` for non-zero exit code ErrorRecord (#16108) (Thanks @rkeithhill!) ++Tab completion improvements + - Fix tab completion within the script block specified for the `ValidateScriptAttribute`. (#14550) (Thanks @MartinGC94!)+- Added tab completion for loop labels after `break`/`continue` (#16438) (Thanks @MartinGC94!) ++Updated cmdlets + - Add `-HttpVersion` parameter to web cmdlets (#15853) (Thanks @hayhay27!) - Add support to web cmdlets for open-ended input tags (#16193) (Thanks @farmerau!) - Fix `ConvertTo-Json -Depth` to allow 100 at maximum (#16197) (Thanks @KevRitchie!)-- Specify the executable path as `TargetObject` for non-zero exit code ErrorRecord (#16108) (Thanks @rkeithhill!)-- Invoke-Command: improve handling of variables with $using: expression (#16113) (Thanks @dwtaber!)+- Improve variable handling when calling `Invoke-Command` with the `$using:` expression (#16113) (Thanks @dwtaber!) +- Add `-StrictMode` to `Invoke-Command` to allow specifying strict mode when invoking command locally - Add `clean` block to script block as a peer to `begin`, `process`, and `end` to allow easy resource cleanup (#15177)+ (#16545) (Thanks @Thomas-Yu!) +- Add `-Options` to the PSRP over SSH commands to allow passing OpenSSH options directly (#12802) (Thanks @BrannenGH!) For a complete list of changes, see the [Change Log][CHANGELOG] in the GitHub repository. ## Experimental Features -> [!NOTE] -> There is a known issue in 7.3.0-preview.1 - Alpine Linux packages are missing the -> `powershell.config.json` file, causing experimental features to be disabled by default. For -> details, see Issue #16636. - PowerShell 7.3 introduces the following experimental features: - [PSExec][exp-psexec] - Adds the new `Switch-Process` cmdlet (alias `exec`) to provide `exec` PowerShell 7.3 introduces the following experimental features: - [PSNativeCommandErrorActionPreference][exp-error] - Adds the `$PSNativeCommandUseErrorActionPreference` variable to enable errors produced by native commands to be PowerShell errors.+- [PSAMSIMethodInvocationLogging][exp-amsi] - Extends the data that is sent to AMSI for inspection to + include all invocations of .NET method members. For more information about the Experimental Features, see [Using Experimental Features][exp]. For more information about the Experimental Features, see [Using Experimental Fe <!-- reference links --> -[CHANGELOG]: https://github.com/PowerShell/PowerShell/releases/tag/v7.3.0-preview.1 +[CHANGELOG]: https://github.com/PowerShell/PowerShell/releases/tag/v7.3.0-preview.2 [exp-clean]: ../learn/experimental-features.md#pscleanblock [exp-psexec]: ../learn/experimental-features.md#psexec [exp-strict]: ../learn/experimental-features.md#psstrictmodeassignment [exp-error]: ../learn/experimental-features.md#psnativecommanderroractionpreference+[exp-amsi]: ../learn/experimental-features.md?#psamsimethodinvocationlogging |