diff --git a/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md b/reference/docs-conceptual/install/Installing-PowerShell-on-Windows.md index 17c50326236d..b3efbb801137 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: 12/12/2024 +ms.date: 01/23/2025 title: Installing PowerShell on Windows --- # Installing PowerShell on Windows @@ -55,7 +55,7 @@ winget search Microsoft.PowerShell ```Output Name Id Version Source ----------------------------------------------------------------- -PowerShell Microsoft.PowerShell 7.4.6.0 winget +PowerShell Microsoft.PowerShell 7.4.7.0 winget PowerShell Preview Microsoft.PowerShell.Preview 7.5.0.101 winget ``` @@ -79,9 +79,9 @@ winget install --id Microsoft.PowerShell.Preview --source winget To install PowerShell on Windows, use the following links to download the install package from GitHub. -- [PowerShell-7.4.6-win-x64.msi][28] -- [PowerShell-7.4.6-win-x86.msi][30] -- [PowerShell-7.4.6-win-arm64.msi][36] +- [PowerShell-7.4.7-win-x64.msi][28] +- [PowerShell-7.4.7-win-x86.msi][30] +- [PowerShell-7.4.7-win-arm64.msi][36] Once downloaded, double-click the installer file and follow the prompts. @@ -151,7 +151,7 @@ installation options: The following example shows how to silently install PowerShell with all the install options enabled. ```powershell -msiexec.exe /package PowerShell-7.4.6-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1 +msiexec.exe /package PowerShell-7.4.7-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1 ``` For a full list of command-line options for `Msiexec.exe`, see @@ -162,9 +162,9 @@ For a full list of command-line options for `Msiexec.exe`, see PowerShell binary ZIP archives are provided to enable advanced deployment scenarios. Download one of the following ZIP archives from the [current release][23] page. -- [PowerShell-7.4.6-win-x64.zip][29] -- [PowerShell-7.4.6-win-x86.zip][31] -- [PowerShell-7.4.6-win-arm64.zip][27] +- [PowerShell-7.4.7-win-x64.zip][29] +- [PowerShell-7.4.7-win-x86.zip][31] +- [PowerShell-7.4.7-win-arm64.zip][27] Depending on how you download the file you may need to unblock the file using the `Unblock-File` cmdlet. Unzip the contents to the location of your choice and run `pwsh.exe` from there. Unlike @@ -261,7 +261,7 @@ If there is an available upgrade, the output indicates the latest available vers > [!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.6. To upgrade from an +> 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. > @@ -275,7 +275,7 @@ Windows 10 IoT Enterprise comes with Windows PowerShell, which we can use to dep ```powershell # Replace the placeholder information for the following variables: $deviceip = ' -$zipfile = 'PowerShell-7.4.6-win-x64.zip' +$zipfile = 'PowerShell-7.4.7-win-x64.zip' # Connect to the built-in instance of Windows PowerShell $session = New-PSSession -ComputerName $ipaddr -Credential $credential # Copy the file to the Nano Server instance @@ -360,7 +360,7 @@ Copy-Item $zipfile c:\ -ToSession $session # Enter the interactive remote session Enter-PSSession $session # Extract the ZIP file -Expand-Archive -Path C:\PowerShell-7.4.6-win-x64.zip -DestinationPath 'C:\Program Files\PowerShell 7' +Expand-Archive -Path C:\PowerShell-7.4.7-win-x64.zip -DestinationPath 'C:\Program Files\PowerShell 7' ``` If you want WSMan-based remoting, follow the instructions to create a remoting endpoint using the @@ -415,13 +415,13 @@ can't support those methods. [22]: https://aka.ms/powershell-release?tag=preview [23]: https://aka.ms/powershell-release?tag=stable [24]: https://github.com/ms-iot/iot-adk-addonkit/blob/master/Tools/IoTCoreImaging/Docs/Import-PSCoreRelease.md#Import-PSCoreRelease -[27]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/PowerShell-7.4.6-win-arm64.zip -[28]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/PowerShell-7.4.6-win-x64.msi -[29]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/PowerShell-7.4.6-win-x64.zip -[30]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/PowerShell-7.4.6-win-x86.msi -[31]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/PowerShell-7.4.6-win-x86.zip +[27]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/PowerShell-7.4.7-win-arm64.zip +[28]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/PowerShell-7.4.7-win-x64.msi +[29]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/PowerShell-7.4.7-win-x64.zip +[30]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/PowerShell-7.4.7-win-x86.msi +[31]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/PowerShell-7.4.7-win-x86.zip [32]: https://www.microsoft.com/download/details.aspx?id=50410 [33]: https://www.microsoft.com/store/apps/9MZ1SNWT0N5D [34]: microsoft-update-faq.yml [35]: https://techcommunity.microsoft.com/t5/windows-server-insiders/announcing-windows-server-preview-build-26085/m-p/4098829 -[36]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/PowerShell-7.4.6-win-arm64.msi +[36]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/PowerShell-7.4.7-win-arm64.msi diff --git a/reference/docs-conceptual/install/Installing-PowerShell-on-macOS.md b/reference/docs-conceptual/install/Installing-PowerShell-on-macOS.md index d70bc591ca46..b9dea379f42b 100644 --- a/reference/docs-conceptual/install/Installing-PowerShell-on-macOS.md +++ b/reference/docs-conceptual/install/Installing-PowerShell-on-macOS.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on macOS -ms.date: 12/12/2024 +ms.date: 01/23/2025 title: Installing PowerShell on macOS --- @@ -117,23 +117,23 @@ install package from the [releases][09] page onto your computer. The links to th are: - PowerShell 7.4 - - x64 processors - [powershell-7.4.6-osx-x64.pkg][20] - - Arm64 processors - [powershell-7.4.6-osx-arm64.pkg][18] + - x64 processors - [powershell-7.4.7-osx-x64.pkg][20] + - Arm64 processors - [powershell-7.4.7-osx-arm64.pkg][18] - PowerShell 7.5-rc.1 - - x64 processors - [powershell-7.5.0-rc.1-osx-x64.pkg][24] - - Arm64 processors - [powershell-7.5.0-rc.1-arm64.pkg][22] + - x64 processors - [powershell-7.5.0-osx-x64.pkg][24] + - Arm64 processors - [powershell-7.5.0-arm64.pkg][22] You can double-click the file and follow the prompts, or install it from the terminal using the following commands. Change the name of the file to match the file you downloaded. ```sh -sudo installer -pkg ./Downloads/powershell-7.4.6-osx-x64.pkg -target / +sudo installer -pkg ./Downloads/powershell-7.4.7-osx-x64.pkg -target / ``` If you are running on macOS Big Sur 11.5 or higher you may receive the following error message when installing the package: -> "powershell-7.4.6-osx-x64.pkg" cannot be opened because Apple cannot check it for malicious +> "powershell-7.4.7-osx-x64.pkg" cannot be opened because Apple cannot check it for malicious > software. There are two ways to work around this issue: @@ -146,7 +146,7 @@ Using the Finder From the command line -1. Run `sudo xattr -rd com.apple.quarantine ./Downloads/powershell-7.4.6-osx-x64.pkg`. If you are using +1. Run `sudo xattr -rd com.apple.quarantine ./Downloads/powershell-7.4.7-osx-x64.pkg`. If you are using PowerShell 7 or higher, you can use the `Unblock-File` cmdlet. Include the full path to the `.pkg` file. 1. Install the package as you normally would. @@ -186,18 +186,18 @@ Download the install package from the [releases][09] page onto your computer. Th current versions are: - PowerShell 7.4 (LTS) - - x64 processors - [powershell-7.4.6-osx-x64.tar.gz][21] - - Arm64 processors - [powershell-7.4.6-osx-arm64.tar.gz][19] + - x64 processors - [powershell-7.4.7-osx-x64.tar.gz][21] + - Arm64 processors - [powershell-7.4.7-osx-arm64.tar.gz][19] - PowerShell 7.5-preview - - x64 processors - [powershell-7.5.0-rc.1-osx-x64.tar.gz][25] - - Arm64 processors - [powershell-7.5.0-rc.1-osx-arm64.tar.gz][23] + - x64 processors - [powershell-7.5.0-osx-x64.tar.gz][25] + - Arm64 processors - [powershell-7.5.0-osx-arm64.tar.gz][23] Use the following commands to install PowerShell from the binary archive. Change the download URL to match the version you want to install. ```sh # Download the powershell '.tar.gz' archive -curl -L -o /tmp/powershell.tar.gz https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-osx-x64.tar.gz +curl -L -o /tmp/powershell.tar.gz https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-osx-x64.tar.gz # Create the target folder where powershell is placed sudo mkdir -p /usr/local/microsoft/powershell/7 @@ -276,12 +276,12 @@ support those methods. [11]: https://docs.brew.sh/Manpage#link-ln-options-formula [12]: https://github.com/Homebrew [13]: https://github.com/Homebrew/homebrew-cask -[18]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-osx-arm64.pkg -[19]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-osx-arm64.tar.gz -[20]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-osx-x64.pkg -[21]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-osx-x64.tar.gz -[22]: https://github.com/PowerShell/PowerShell/releases/download/v7.5.0-rc.1/powershell-7.5.0-rc.1-osx-arm64.pkg -[23]: https://github.com/PowerShell/PowerShell/releases/download/v7.5.0-rc.1/powershell-7.5.0-rc.1-osx-arm64.tar.gz -[24]: https://github.com/PowerShell/PowerShell/releases/download/v7.5.0-rc.1/powershell-7.5.0-rc.1-osx-x64.pkg -[25]: https://github.com/PowerShell/PowerShell/releases/download/v7.5.0-rc.1/powershell-7.5.0-rc.1-osx-x64.tar.gz +[18]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-osx-arm64.pkg +[19]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-osx-arm64.tar.gz +[20]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-osx-x64.pkg +[21]: https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-osx-x64.tar.gz +[22]: https://github.com/PowerShell/PowerShell/releases/download/7.5.0/powershell-7.5.0-osx-arm64.pkg +[23]: https://github.com/PowerShell/PowerShell/releases/download/7.5.0/powershell-7.5.0-osx-arm64.tar.gz +[24]: https://github.com/PowerShell/PowerShell/releases/download/7.5.0/powershell-7.5.0-osx-x64.pkg +[25]: https://github.com/PowerShell/PowerShell/releases/download/7.5.0/powershell-7.5.0-osx-x64.tar.gz [26]: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html diff --git a/reference/docs-conceptual/install/PowerShell-Support-Lifecycle.md b/reference/docs-conceptual/install/PowerShell-Support-Lifecycle.md index df0a2f646cc0..494e8ab5134a 100644 --- a/reference/docs-conceptual/install/PowerShell-Support-Lifecycle.md +++ b/reference/docs-conceptual/install/PowerShell-Support-Lifecycle.md @@ -1,6 +1,6 @@ --- description: Details the policies governing support for PowerShell. -ms.date: 01/17/2025 +ms.date: 01/23/2025 ms.topic: lifecycle title: PowerShell Support Lifecycle --- @@ -110,38 +110,31 @@ guarantees of responsiveness or fixes. The PowerShell support lifecycle follows the [support lifecycle of .NET][06]. The following table lists the end-of-support dates for the current versions of PowerShell: -| Version | Release Date | End-of-support | -| --------- | ------------------ | ------------------ | -| 7.4 (LTS) | November 16, 2023 | November 10, 2026 | +| Version | Release Date | End-of-support | .NET Version | +| ------------------------ | :----------: | :------------: | ------------------------- | +| PowerShell 7.6 (preview) | Future date | Future date | Built on [.NET 9.0.0][14] | +| PowerShell 7.5 | 23-Jan-2025 | 12-May-2026 | Built on [.NET 9.0.0][14] | +| PowerShell 7.4 (LTS) | 16-Nov-2023 | 10-Nov-2026 | Built on [.NET 8.0.0][13] | The following table lists the end-of-support dates for retired versions of PowerShell: -| Version | Release Date | End-of-support | -| --------- | ------------------ | ------------------ | -| 7.3 | November 9, 2022 | May 8, 2024 | -| 7.2 (LTS) | November 8, 2021 | November 8, 2024 | -| 7.0 (LTS) | March 4, 2020 | December 3, 2022 | -| 7.1 | November 11, 2020 | May 8, 2022 | -| 6.2 | March 28, 2019 | September 4, 2020 | -| 6.1 | September 13, 2018 | September 28, 2019 | -| 6.0 | January 20, 2018 | February 13, 2019 | +| Version | Release Date | End-of-support | .NET Version | +| -------------------- | :----------: | :------------: | ---------------------------- | +| PowerShell 7.3 | 09-Nov-2022 | 08-May-2024 | Built on [.NET 7.0][12] | +| PowerShell 7.2 (LTS) | 08-Nov-2021 | 08-Nov-2024 | Built on [.NET 6.0][11] | +| PowerShell 7.0 (LTS) | 04-Mar-2020 | 03-Dec-2022 | Built on [.NET 5.0][10] | +| PowerShell 7.1 | 11-Nov-2020 | 08-May-2022 | Built on [.NET Core 3.1][09] | +| PowerShell 6.2 | 29-Mar-2019 | 04-Sep-2020 | Built on [.NET Core 2.1][08] | +| PowerShell 6.1 | 13-Sep-2018 | 28-Sep-2019 | Built on [.NET Core 2.1][08] | +| PowerShell 6.0 | 20-Jan-2018 | 13-Feb-2019 | Built on [.NET Core 2.0][07] | -## Release history +## Windows PowerShell release history -The following table contains a historical timeline of the major releases of PowerShell. +The following table contains a historical timeline of the major releases of Windows PowerShell. +Microsoft no longer supports Windows PowerShell versions lower than 5.1. | Version | Release Date | Note | | ------------------------ | :----------: | -------------------------------------------------------------------------- | -| PowerShell 7.6 (preview) | Future | Built on [.NET 9.0.0][14] | -| PowerShell 7.5 (RC) | Future | Built on [.NET 9.0.0][14] | -| PowerShell 7.4 (LTS) | Nov-2023 | Built on [.NET 8.0.0][13] | -| PowerShell 7.3 | Nov-2022 | Built on [.NET 7.0][12] | -| PowerShell 7.2 (LTS) | Nov-2021 | Built on [.NET 6.0][11] | -| PowerShell 7.1 | Nov-2020 | Built on [.NET 5.0][10] | -| PowerShell 7.0 (LTS) | Mar-2020 | Built on [.NET Core 3.1][09] | -| PowerShell 6.2 | Mar-2019 | Built on [.NET Core 2.1][08] | -| PowerShell 6.1 | Sep-2018 | Built on [.NET Core 2.1][08] | -| PowerShell 6.0 | Jan-2018 | Built on [.NET Core 2.0][07]. Installable on Windows, Linux, and macOS | | Windows PowerShell 5.1 | Aug-2016 | Released in Windows 10 Anniversary Update and Windows Server 2016, WMF 5.1 | | Windows PowerShell 5.0 | Feb-2016 | Released in Windows Management Framework (WMF) 5.0 | | Windows PowerShell 4.0 | Oct-2013 | Released in Windows 8.1 and with Windows Server 2012 R2, WMF 4.0 | diff --git a/reference/docs-conceptual/install/community-support.md b/reference/docs-conceptual/install/community-support.md index be9938ee73cb..288c633b403e 100644 --- a/reference/docs-conceptual/install/community-support.md +++ b/reference/docs-conceptual/install/community-support.md @@ -1,6 +1,6 @@ --- description: PowerShell can run on Linux distributions that aren't officially supported by Microsoft. -ms.date: 08/27/2024 +ms.date: 01/23/2025 title: Community support for PowerShell on Linux --- # Community support for PowerShell on Linux @@ -77,9 +77,9 @@ the following article provides information on how to install PowerShell on openS Download the tar.gz package from the [releases][09] page onto your Raspberry Pi computer. The links to the current versions are: -- PowerShell 7.4.6 - latest LTS release - - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-linux-arm32.tar.gz` - - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-linux-arm64.tar.gz` +- PowerShell 7.4.7 - latest LTS release + - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-linux-arm32.tar.gz` + - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-linux-arm64.tar.gz` Use the following shell commands to download and install the package. This script detects whether you're running a 32-bit or 64-bit OS and installs the latest stable version of PowerShell for that diff --git a/reference/docs-conceptual/install/install-alpine.md b/reference/docs-conceptual/install/install-alpine.md index 50a4d10009b8..48798b98ac5f 100644 --- a/reference/docs-conceptual/install/install-alpine.md +++ b/reference/docs-conceptual/install/install-alpine.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Alpine Linux -ms.date: 12/16/2024 +ms.date: 01/23/2025 title: Installing PowerShell on Alpine Linux --- # Installing PowerShell on Alpine Linux @@ -20,8 +20,8 @@ check the list of [Supported versions][02] below. Installation on Alpine is based on downloading tar.gz package from the [releases][03] page. The URL to the package depends on the version of PowerShell you want to install. -- PowerShell 7.4.6 - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-linux-musl-x64.tar.gz` -- PowerShell 7.5.0-rc.1 - `https://github.com/PowerShell/PowerShell/releases/download/v7.5.0-rc.1/powershell-7.5.0-rc.1-linux-musl-x64.tar.gz` +- PowerShell 7.4.7 - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-linux-musl-x64.tar.gz` +- PowerShell 7.5.0 - `https://github.com/PowerShell/PowerShell/releases/download/7.5.0/powershell-7.5.0-linux-musl-x64.tar.gz` Then, in the terminal, execute the following shell commands to install PowerShell 7.4: @@ -47,7 +47,7 @@ apk -X https://dl-cdn.alpinelinux.org/alpine/edge/main add --no-cache \ openssh-client \ # Download the powershell '.tar.gz' archive -curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-linux-musl-x64.tar.gz -o /tmp/powershell.tar.gz +curl -L https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-linux-musl-x64.tar.gz -o /tmp/powershell.tar.gz # Create the target folder where powershell will be placed sudo mkdir -p /opt/microsoft/powershell/7 diff --git a/reference/docs-conceptual/install/install-debian.md b/reference/docs-conceptual/install/install-debian.md index 4a9639f1d871..a2b40f3bf4a2 100644 --- a/reference/docs-conceptual/install/install-debian.md +++ b/reference/docs-conceptual/install/install-debian.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Debian Linux -ms.date: 12/12/2024 +ms.date: 01/23/2025 title: Installing PowerShell on Debian --- # Installing PowerShell on Debian @@ -70,9 +70,9 @@ package from the [releases][02] page onto your Debian machine. The link to the current version is: - PowerShell 7.4 (LTS) universal package for supported versions of Debian - - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell_7.4.6-1.deb_amd64.deb` + - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell_7.4.7-1.deb_amd64.deb` - PowerShell 7.5-preview universal package for supported versions of Debian - - `https://github.com/PowerShell/PowerShell/releases/download/v7.5.0-rc.1/powershell-preview_7.5.0-rc.1-1.deb_amd64.deb` + - `https://github.com/PowerShell/PowerShell/releases/download/7.5.0/powershell-preview_7.5.0-1.deb_amd64.deb` The following shell script downloads and installs the current release of PowerShell. You can change the URL to download the version of PowerShell that you want to install. @@ -88,17 +88,17 @@ sudo apt-get update sudo apt-get install -y wget # Download the PowerShell package file -wget https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell_7.4.6-1.deb_amd64.deb +wget https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell_7.4.7-1.deb_amd64.deb ################################### # Install the PowerShell package -sudo dpkg -i powershell_7.4.6-1.deb_amd64.deb +sudo dpkg -i powershell_7.4.7-1.deb_amd64.deb # Resolve missing dependencies and finish the install (if necessary) sudo apt-get install -f # Delete the downloaded package file -rm powershell_7.4.6-1.deb_amd64.deb +rm powershell_7.4.7-1.deb_amd64.deb # Start PowerShell pwsh diff --git a/reference/docs-conceptual/install/install-other-linux.md b/reference/docs-conceptual/install/install-other-linux.md index ad813cbb8a9d..84a2c695a454 100644 --- a/reference/docs-conceptual/install/install-other-linux.md +++ b/reference/docs-conceptual/install/install-other-linux.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on various Linux distributions -ms.date: 08/20/2024 +ms.date: 01/23/2025 title: Alternate ways to install PowerShell on Linux --- # Alternate ways to install PowerShell on Linux @@ -132,16 +132,16 @@ archive. The following example shows the steps for installing the x64 binary archive. You must choose the correct binary archive that matches the processor type for your platform. -- `powershell-7.4.6-linux-arm32.tar.gz` -- `powershell-7.4.6-linux-arm64.tar.gz` -- `powershell-7.4.6-linux-x64.tar.gz` +- `powershell-7.4.7-linux-arm32.tar.gz` +- `powershell-7.4.7-linux-arm64.tar.gz` +- `powershell-7.4.7-linux-x64.tar.gz` Use the following shell commands to download and install PowerShell from the `tar.gz` binary archive. Change the URL to match the version of PowerShell you want to install. ```sh # Download the powershell '.tar.gz' archive -curl -L -o /tmp/powershell.tar.gz https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-linux-x64.tar.gz +curl -L -o /tmp/powershell.tar.gz https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-linux-x64.tar.gz # Create the target folder where powershell will be placed sudo mkdir -p /opt/microsoft/powershell/7 diff --git a/reference/docs-conceptual/install/install-rhel.md b/reference/docs-conceptual/install/install-rhel.md index 5c183ea1c0d8..bdca3471d456 100644 --- a/reference/docs-conceptual/install/install-rhel.md +++ b/reference/docs-conceptual/install/install-rhel.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Red Hat Enterprise Linux (RHEL) -ms.date: 12/12/2024 +ms.date: 01/23/2025 title: Installing PowerShell on Red Hat Enterprise Linux (RHEL) --- # Installing PowerShell on Red Hat Enterprise Linux (RHEL) @@ -64,10 +64,10 @@ package from the [releases][02] page onto your RHEL machine. The link to the current version is: -- PowerShell 7.4.6 universal package for supported versions of RHEL - - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-1.rh.x86_64.rpm` -- PowerShell 7.5.0-rc.1 universal package for supported versions of RHEL - - `https://github.com/PowerShell/PowerShell/releases/download/v7.5.0-rc.1/powershell-preview-7.5.0_preview.2-1.rh.x86_64.rpm` +- PowerShell 7.4.7 universal package for supported versions of RHEL + - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-1.rh.x86_64.rpm` +- PowerShell 7.5.0 universal package for supported versions of RHEL + - `https://github.com/PowerShell/PowerShell/releases/download/7.5.0/powershell-preview-7.5.0_preview.2-1.rh.x86_64.rpm` The following shell script downloads and installs the current preview release of PowerShell. You can change the URL to download the version of PowerShell that you want to install. @@ -75,7 +75,7 @@ change the URL to download the version of PowerShell that you want to install. On RHEL 8 or 9: ```sh -sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell-7.4.6-1.rh.x86_64.rpm +sudo dnf install https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell-7.4.7-1.rh.x86_64.rpm ``` ## Uninstall PowerShell diff --git a/reference/docs-conceptual/install/install-ubuntu.md b/reference/docs-conceptual/install/install-ubuntu.md index 9132352ccd0d..c1889baccc47 100644 --- a/reference/docs-conceptual/install/install-ubuntu.md +++ b/reference/docs-conceptual/install/install-ubuntu.md @@ -1,6 +1,6 @@ --- description: Information about installing PowerShell on Ubuntu -ms.date: 12/12/2024 +ms.date: 01/23/2025 title: Installing PowerShell on Ubuntu --- # Installing PowerShell on Ubuntu @@ -82,9 +82,9 @@ package from the [releases][05] page onto your Ubuntu machine. The link to the current version is: - PowerShell 7.4 (LTS) universal package for supported versions of Ubuntu - - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell_7.4.6-1.deb_amd64.deb` -- PowerShell 7.5.0-rc.1 universal package for supported versions of Ubuntu - - `https://github.com/PowerShell/PowerShell/releases/download/v7.5.0-rc.1/powershell-preview_7.5.0-rc.1-1.deb_amd64.deb` + - `https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell_7.4.7-1.deb_amd64.deb` +- PowerShell 7.5.0 universal package for supported versions of Ubuntu + - `https://github.com/PowerShell/PowerShell/releases/download/7.5.0/powershell-preview_7.5.0-1.deb_amd64.deb` The following shell script downloads and installs the current preview release of PowerShell. You can change the URL to download the version of PowerShell that you want to install. @@ -100,17 +100,17 @@ sudo apt-get update sudo apt-get install -y wget # Download the PowerShell package file -wget https://github.com/PowerShell/PowerShell/releases/download/v7.4.6/powershell_7.4.6-1.deb_amd64.deb +wget https://github.com/PowerShell/PowerShell/releases/download/v7.4.7/powershell_7.4.7-1.deb_amd64.deb ################################### # Install the PowerShell package -sudo dpkg -i powershell_7.4.6-1.deb_amd64.deb +sudo dpkg -i powershell_7.4.7-1.deb_amd64.deb # Resolve missing dependencies and finish the install (if necessary) sudo apt-get install -f # Delete the downloaded package file -rm powershell_7.4.6-1.deb_amd64.deb +rm powershell_7.4.7-1.deb_amd64.deb # Start PowerShell Preview pwsh diff --git a/reference/docs-conceptual/install/microsoft-update-faq.yml b/reference/docs-conceptual/install/microsoft-update-faq.yml index e4aa99133979..b29e9272fc2c 100644 --- a/reference/docs-conceptual/install/microsoft-update-faq.yml +++ b/reference/docs-conceptual/install/microsoft-update-faq.yml @@ -1,6 +1,6 @@ ### YamlMime:FAQ metadata: - ms.date: 08/20/2024 + ms.date: 01/23/2025 title: Microsoft Update for PowerShell FAQ description: Frequently asked questions about the using Microsoft Update to update PowerShell ms.topic: faq @@ -108,7 +108,7 @@ sections: doesn't show the check box options. To enable MU updates run the following command: ```powershell - msiexec.exe /fmu .\PowerShell-7.4.6-win-x64.msi USE_MU=1 ENABLE_MU=1 + msiexec.exe /fmu .\PowerShell-7.4.7-win-x64.msi USE_MU=1 ENABLE_MU=1 ``` For more information about running `msiexec.exe` from the command line, see diff --git a/reference/docs-conceptual/learn/experimental-features.md b/reference/docs-conceptual/learn/experimental-features.md index 1f52ccbaa599..60db76186c09 100644 --- a/reference/docs-conceptual/learn/experimental-features.md +++ b/reference/docs-conceptual/learn/experimental-features.md @@ -1,6 +1,6 @@ --- description: Lists the currently available experimental features and how to use them. -ms.date: 09/24/2024 +ms.date: 01/23/2025 title: Using Experimental Features in PowerShell --- # Using Experimental Features in PowerShell @@ -15,14 +15,14 @@ breaking changes. > [!CAUTION] > Experimental features aren't intended to be used in production since the changes are allowed to be > breaking. Experimental features aren't officially supported. However, we appreciate any feedback -> and bug reports. You can file issues in the [GitHub source repository][26]. +> and bug reports. You can file issues in the [GitHub source repository][16]. For more information about enabling or disabling these features, see -[about_Experimental_Features][06]. +[about_Experimental_Features][05]. ## Experimental feature lifecycle -The [Get-ExperimentalFeature][30] cmdlet returns all experimental features available to PowerShell. +The [Get-ExperimentalFeature][19] cmdlet returns all experimental features available to PowerShell. Experimental features can come from modules or the PowerShell engine. Module-based experimental features are only available after you import the module. In the following example, the **PSDesiredStateConfiguration** isn't loaded, so the `PSDesiredStateConfiguration.InvokeDscResource` @@ -44,7 +44,7 @@ PSSerializeJSONLongEnumAsNumber True PSEngine Serialize enums based on long PSSubsystemPluginModel True PSEngine A plugin model for registering and un-registering… ``` -Use the [Enable-ExperimentalFeature][29] and [Disable-ExperimentalFeature][28] cmdlets to enable or +Use the [Enable-ExperimentalFeature][18] and [Disable-ExperimentalFeature][17] cmdlets to enable or disable a feature. You must start a new PowerShell session for this change to be in effect. Run the following command to enable the `PSCommandNotFoundSuggestion` feature: @@ -82,38 +82,18 @@ Legend - The ![Discontinued][03] icon indicates the version of PowerShell where the experimental feature was removed -| Name | 7.2 | 7.4 | 7.5 (preview) | +| Name | 7.4 | 7.5 | 7.6 (preview) | | --------------------------------------------------- | :-----------------: | :-----------------: | :-----------------: | -| [PSCommandNotFoundSuggestion][10] | ![Experimental][02] | ![Experimental][02] | ![Mainstream][01] | -| [PSDesiredStateConfiguration.InvokeDscResource][14] | ![Experimental][02] | ![Experimental][02] | ![Experimental][02] | -| [PSNativePSPathResolution][21] | ![Experimental][02] | | | -| [PSSubsystemPluginModel][23] | ![Experimental][02] | ![Experimental][02] | ![Experimental][02] | -| [PSNativeCommandArgumentPassing][18] | ![Experimental][02] | | | -| [PSAnsiRenderingFileInfo][09] | ![Experimental][02] | | | -| [PSLoadAssemblyFromNativeCode][16] | ![Experimental][02] | ![Experimental][02] | ![Experimental][02] | -| [PSNativeCommandErrorActionPreference][19] | | ![Mainstream][01] | | -| [PSFeedbackProvider][15] | | ![Experimental][02] | ![Experimental][02] | -| [PSModuleAutoLoadSkipOfflineFiles][17] | | ![Experimental][02] | ![Mainstream][01] | -| [PSCommandWithArgs][11] | | ![Experimental][02] | ![Mainstream][01] | -| [PSNativeWindowsTildeExpansion][22] | | | ![Experimental][02] | -| [PSRedirectToVariable][24] | | | ![Experimental][02] | -| [PSSerializeJSONLongEnumAsNumber][25] | | | ![Experimental][02] | - -### PSAnsiRenderingFileInfo - -> [!NOTE] -> This feature became mainstream in PowerShell 7.3. - -The ANSI formatting features were added in PowerShell 7.2. This feature adds the `$PSStyle.FileInfo` -member and enables coloring of specific file types. - -- `$PSStyle.FileInfo.Directory` - Built-in member to specify the color for directories -- `$PSStyle.FileInfo.SymbolicLink` - Built-in member to specify the color for symbolic links -- `$PSStyle.FileInfo.Executable` - Built-in member to specify the color for executables. -- `$PSStyle.FileInfo.Extension` - Use this member to define the colors for different file - extensions. The **Extension** member pre-includes extensions for archive and PowerShell files. - -For more information, see [about_Automatic_Variables][05]. +| [PSCommandNotFoundSuggestion][06] | ![Experimental][02] | ![Mainstream][01] | ![Mainstream][01] | +| [PSDesiredStateConfiguration.InvokeDscResource][08] | ![Experimental][02] | ![Experimental][02] | ![Experimental][02] | +| [PSSubsystemPluginModel][15] | ![Experimental][02] | ![Experimental][02] | ![Experimental][02] | +| [PSLoadAssemblyFromNativeCode][10] | ![Experimental][02] | ![Experimental][02] | ![Experimental][02] | +| [PSFeedbackProvider][09] | ![Experimental][02] | ![Experimental][02] | ![Experimental][02] | +| [PSModuleAutoLoadSkipOfflineFiles][11] | ![Experimental][02] | ![Mainstream][01] | ![Mainstream][01] | +| [PSCommandWithArgs][07] | ![Experimental][02] | ![Mainstream][01] | ![Mainstream][01] | +| [PSNativeWindowsTildeExpansion][12] | | ![Experimental][02] | ![Experimental][02] | +| [PSRedirectToVariable][13] | | ![Experimental][02] | ![Experimental][02] | +| [PSSerializeJSONLongEnumAsNumber][14] | | ![Experimental][02] | ![Experimental][02] | ### PSCommandNotFoundSuggestion @@ -211,132 +191,6 @@ always kept on disk. This feature was added in PowerShell 7.4-preview.1. -### PSNativeCommandArgumentPassing - -> [!NOTE] -> This feature became mainstream in PowerShell 7.3. - -When this experimental feature is enabled PowerShell uses the `ArgumentList` property of the -`StartProcessInfo` object rather than our current mechanism of reconstructing a string when invoking -a native executable. - -> [!CAUTION] -> The new behavior is a **breaking change** from current behavior. This may break scripts and -> automation that work around the various issues when invoking native applications. Historically, -> quotes must be escaped and it isn't possible to provide empty arguments to a native application. -> Use the [stop-parsing token][08] (`--%`) or the [`Start-Process`][32] cmdlet to sidestep native -> argument passing when needed. - -This feature adds a new `$PSNativeCommandArgumentPassing` preference variable that controls this -behavior. This variable allows you to select the behavior at runtime. The valid values are `Legacy`, -`Standard`, and `Windows`. The default behavior is platform specific. On Windows platforms, the -default setting is `Windows` and non-Windows platforms default to `Standard`. - -`Legacy` is the historic behavior. The behavior of `Windows` and `Standard` mode are the same -except, in `Windows` mode, invocations of the following files automatically use the `Legacy` style -argument passing. - - -- `cmd.exe` -- `find.exe` -- `cscript.exe` -- `wscript.exe` -- `sqlcmd.exe` - Added in PowerShell 7.3.1 -- ending with `.bat` -- ending with `.cmd` -- ending with `.js` -- ending with `.vbs` -- ending with `.wsf` - -If the `$PSNativeCommandArgumentPassing` is set to either `Legacy` or `Standard`, the parser doesn't -check for these files. - -The default behavior is platform specific. On Windows platforms, the default setting is `Windows` -and non-Windows platforms is `Standard`. - -> [!NOTE] -> The following examples use the `TestExe.exe` tool. You can build `TestExe` from the source code. -> See [TestExe][27] in the PowerShell source repository. - -New behaviors made available by this change: - -- Literal or expandable strings with embedded quotes the quotes are preserved: - - ```powershell - PS> $a = 'a" "b' - PS> TestExe -echoargs $a 'c" "d' e" "f - Arg 0 is - Arg 1 is - Arg 2 is - ``` - -- Empty strings as arguments are preserved: - - ```powershell - PS> TestExe -echoargs '' a b '' - Arg 0 is <> - Arg 1 is - Arg 2 is - Arg 3 is <> - ``` - -For more examples of the new behavior, see [about_Parsing][07]. - -PowerShell 7.3 also added the ability to trace parameter binding for native commands. For more -information, see [Trace-Command][34]. - -### PSNativeCommandErrorActionPreference - - - -> [!NOTE] -> This feature became mainstream in PowerShell 7.4. - -Native commands usually return an exit code to the calling application that's zero for success or -non-zero for failure. However, native commands currently don't participate in the PowerShell error -stream. Redirected **stderr** output isn't interpreted the same as the PowerShell error stream. Many -native commands use stderr as an information or verbose stream, thus only the exit code matters. -Users working with native commands in their scripts need to check the exit status after each call -using similar to the following example: - -```powershell -if ($LASTEXITCODE -ne 0) { - throw "Command failed. See above errors for details" -} -``` - -However, this example doesn't support all cases where `$?` can be false from a cmdlet or function -error, making `$LASTEXITCODE` stale. - -This feature implements the `$PSNativeCommandUseErrorActionPreference` preference variable that -controls how native commands errors are handled in PowerShell. This allows native command failures -to produce error objects that are added to the PowerShell error stream and may terminate execution -of the script without extra handling. - -`$PSNativeCommandUseErrorActionPreference` is set to `$false` by default. With the preference set to -`$true` you get the following behavior: - -- When `$ErrorActionPreference = 'Stop'`, scripts will break when a native command returns a - non-zero exit code. -- When `$ErrorActionPreference = 'Continue'` (the default), you will see PowerShell error messages - for native command errors, but scripts won't break. - -### PSNativePSPathResolution - -> [!NOTE] -> This experimental feature was removed in PowerShell 7.3 and is no longer supported. - -If a PSDrive path that uses the FileSystem provider is passed to a native command, the resolved file -path is passed to the native command. This means a command like `code temp:/test.txt` now works as -expected. - -Also, on Windows, if the path starts with `~`, that's resolved to the full path and passed to the -native command. In both cases, the path is normalized to the directory separators for the relevant -operating system. - -- If the path isn't a PSDrive or `~` (on Windows), then path normalization doesn't occur -- If the path is in single quotes, then it's not resolved and treated as literal - ### PSRedirectToVariable > [!NOTE] @@ -376,7 +230,7 @@ the PSReadLine module to provide custom prediction plugins. In future, **Job**, **CommandCompleter**, **Remoting** and other components could be separated into subsystem assemblies outside of `System.Management.Automation.dll`. -The experimental feature includes a new cmdlet, [Get-PSSubsystem][31]. This cmdlet is only available +The experimental feature includes a new cmdlet, [Get-PSSubsystem][20]. This cmdlet is only available when the feature is enabled. This cmdlet returns information about the subsystems that are available on the system. @@ -405,7 +259,7 @@ This feature was added in PowerShell 7.5-preview.2. ### PSSerializeJSONLongEnumAsNumber -This feature enables the cmdlet [ConvertTo-Json][33] to serialize any enum values based on +This feature enables the cmdlet [ConvertTo-Json][21] to serialize any enum values based on `Int64/long` or `UInt64/ulong` as a numeric value rather than the string representation of that enum value. This aligns the behavior of enum serialization with other enum base types where the cmdlet serializes enums as their numeric value. Use the **EnumsAsStrings** parameter to serialize as the @@ -438,30 +292,20 @@ For example: [02]: ../../media/shared/construction-sign-1f6a7.svg [03]: ../../media/shared/cross-mark-274c.svg [04]: /powershell/dsc/overview?view=dsc-3.0&preserve-view=true -[05]: /powershell/module/microsoft.powershell.core/about/about_automatic_variables -[06]: /powershell/module/microsoft.powershell.core/about/about_experimental_features -[07]: /powershell/module/microsoft.powershell.core/about/about_parsing -[08]: /powershell/module/microsoft.powershell.core/about/about_parsing#the-stop-parsing-token -[09]: #psansirenderingfileinfo -[10]: #pscommandnotfoundsuggestion -[11]: #pscommandwithargs -[14]: #psdesiredstateconfigurationinvokedscresource -[15]: #psfeedbackprovider -[16]: #psloadassemblyfromnativecode -[17]: #psmoduleautoloadskipofflinefiles -[18]: #psnativecommandargumentpassing -[19]: #psnativecommanderroractionpreference -[21]: #psnativepspathresolution -[22]: #psnativewindowstildeexpansion -[23]: #pssubsystempluginmodel -[24]: #psredirecttovariable -[25]: #psserializejsonlongenumasnumber -[26]: https://github.com/PowerShell/PowerShell/issues/new/choose -[27]: https://github.com/PowerShell/PowerShell/tree/master/test/tools/TestExe -[28]: xref:Microsoft.PowerShell.Core.Disable-ExperimentalFeature -[29]: xref:Microsoft.PowerShell.Core.Enable-ExperimentalFeature -[30]: xref:Microsoft.PowerShell.Core.Get-ExperimentalFeature -[31]: xref:Microsoft.PowerShell.Core.Get-PSSubsystem -[32]: xref:Microsoft.PowerShell.Management.Start-Process -[33]: xref:Microsoft.PowerShell.Utility.ConvertTo-Json -[34]: xref:Microsoft.PowerShell.Utility.Trace-Command +[05]: /powershell/module/microsoft.powershell.core/about/about_experimental_features +[06]: #pscommandnotfoundsuggestion +[07]: #pscommandwithargs +[08]: #psdesiredstateconfigurationinvokedscresource +[09]: #psfeedbackprovider +[10]: #psloadassemblyfromnativecode +[11]: #psmoduleautoloadskipofflinefiles +[12]: #psnativewindowstildeexpansion +[13]: #psredirecttovariable +[14]: #psserializejsonlongenumasnumber +[15]: #pssubsystempluginmodel +[16]: https://github.com/PowerShell/PowerShell/issues/new/choose +[17]: xref:Microsoft.PowerShell.Core.Disable-ExperimentalFeature +[18]: xref:Microsoft.PowerShell.Core.Enable-ExperimentalFeature +[19]: xref:Microsoft.PowerShell.Core.Get-ExperimentalFeature +[20]: xref:Microsoft.PowerShell.Core.Get-PSSubsystem +[21]: xref:Microsoft.PowerShell.Utility.ConvertTo-Json diff --git a/reference/docs-conceptual/learn/shell/running-commands.md b/reference/docs-conceptual/learn/shell/running-commands.md index 61d271b6f8b9..41a911ad2ccb 100644 --- a/reference/docs-conceptual/learn/shell/running-commands.md +++ b/reference/docs-conceptual/learn/shell/running-commands.md @@ -2,7 +2,7 @@ description: > This article shows how to run commands in PowerShell. title: Running commands in the shell -ms.date: 08/22/2022 +ms.date: 01/23/2025 --- # Running commands in the shell @@ -73,8 +73,8 @@ For more information, see the following articles: - [about_Parsing][1] - [about_Quoting_Rules][2] -PowerShell 7.2 introduced a new experimental feature `PSnativeCommandArgumentPassing` that improved -native command handling. For more information, see [PSnativeCommandArgumentPassing][3]. +PowerShell 7.2 introduced a new experimental feature `PSNativeCommandArgumentPassing` that improved +native command handling. For more information, see [`$PSNativeCommandArgumentPassing`][3]. ### Handling output and errors @@ -97,9 +97,9 @@ Many native commands write to **stderr** as an alternative stream for additional behavior can cause confusion in PowerShell when looking through errors and the additional output information can be lost if `$ErrorActionPreference` is set to a state that mutes the output. -PowerShell 7.3 added a new experimental feature `PSnativeCommandErrorActionPreference` that allows +PowerShell 7.3 added a new experimental feature `PSNativeCommandErrorActionPreference` that allows you to control whether output to `stderr` is treated as an error. For more information, see -[PSnativeCommandErrorActionPreference][6]. +[`$PSNativeCommandUseErrorActionPreference`][6]. ## Running PowerShell commands @@ -154,10 +154,10 @@ For more information, see [Invoke-Item][9]. [1]: /powershell/module/microsoft.powershell.core/about/about_parsing#passing-arguments-to-native [2]: /powershell/module/microsoft.powershell.core/about/about_quoting_rules -[3]: ../experimental-features.md#psnativecommandargumentpassing +[3]: /powershell/module/microsoft.powershell.core/about/about_preference_variables#psnativecommandargumentpassing [4]: /powershell/module/microsoft.powershell.core/about/about_redirection [5]: /powershell/module/microsoft.powershell.core/about/about_output_streams -[6]: ../experimental-features.md#psnativecommanderroractionpreference +[6]: /powershell/module/microsoft.powershell.core/about/about_preference_variables#psnativecommanduseerroractionpreference [7]: /powershell/module/microsoft.powershell.core/about/about_operators#call-operator- [8]: /powershell/module/microsoft.powershell.management/start-process [9]: /powershell/module/microsoft.powershell.management/invoke-item diff --git a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-72.md b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-72.md index bfca41ea6b31..42c314585fa0 100644 --- a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-72.md +++ b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-72.md @@ -1,7 +1,7 @@ --- title: What's New in PowerShell 7.2 description: New features and changes released in PowerShell 7.2 -ms.date: 01/20/2023 +ms.date: 01/23/2025 --- # What's New in PowerShell 7.2 @@ -146,9 +146,9 @@ Install-Module -Name PSDesiredStateConfiguration -Repository PSGallery -MaximumV [01]: ../learn/experimental-features.md -[02]: ../learn/experimental-features.md#psansirenderingfileinfo +[02]: /powershell/module/microsoft.powershell.core/about/about_ansi_terminals#psstyle [03]: ../learn/experimental-features.md#psloadassemblyfromnativecode -[04]: ../learn/experimental-features.md#psnativecommandargumentpassing +[04]: /powershell/module/microsoft.powershell.core/about/about_preference_variables#psnativecommandargumentpassing [05]: /powershell/module/microsoft.powershell.core/about/about_ansi_terminals [06]: /powershell/module/microsoft.powershell.utility/import-powershelldatafile [07]: /powershell/scripting/install/installing-powershell-core-on-linux diff --git a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-73.md b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-73.md index 77eb7f6671bd..e927e6259f25 100644 --- a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-73.md +++ b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-73.md @@ -1,7 +1,7 @@ --- title: What's New in PowerShell 7.3 description: New features and changes released in PowerShell 7.3 -ms.date: 02/27/2023 +ms.date: 01/23/2025 --- # What's New in PowerShell 7.3 @@ -147,8 +147,8 @@ For more information about the Experimental Features, see [Using Experimental Fe [01]: ../learn/experimental-features.md -[06]: ../learn/experimental-features.md#psnativecommanderroractionpreference -[08]: ../learn/experimental-features.md#psnativecommandargumentpassing +[06]: /powershell/module/microsoft.powershell.core/about/about_preference_variables#psnativecommanduseerroractionpreference +[08]: /powershell/module/microsoft.powershell.core/about/about_preference_variables#psnativecommandargumentpassing [09]: https://github.com/dotnet/runtime/issues/66746 [10]: https://github.com/PowerShell/PowerShell/issues/17018 [11]: https://github.com/PowerShell/PowerShell/releases/tag/v7.3.0 diff --git a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-74.md b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-74.md index 338e2e2dc31b..0e1752d8d0d4 100644 --- a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-74.md +++ b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-74.md @@ -1,13 +1,13 @@ --- title: What's New in PowerShell 7.4 description: New features and changes released in PowerShell 7.4 -ms.date: 06/19/2024 +ms.date: 01/23/2025 --- # What's New in PowerShell 7.4 -PowerShell 7.4 includes the following features, updates, and breaking changes. PowerShell 7.4 is -built on .NET 8.0.0. +PowerShell 7.4.7 includes the following features, updates, and breaking changes. PowerShell 7.4.7 is +built on .NET 8.0.12. For a complete list of changes, see the [CHANGELOG][chg] in the GitHub repository. diff --git a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-75.md b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-75.md index 6faf74fe3c19..c07c55a9db2a 100644 --- a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-75.md +++ b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-75.md @@ -1,13 +1,13 @@ --- title: What's New in PowerShell 7.5 description: New features and changes released in PowerShell 7.5 -ms.date: 12/05/2024 +ms.date: 01/23/2025 --- # What's New in PowerShell 7.5 -PowerShell 7.5-rc.1 includes the following features, updates, and breaking changes. PowerShell -7.5 is built on .NET 9.0.100 GA release. +PowerShell 7.5.0 includes the following features, updates, and breaking changes. PowerShell +7.5 is built on .NET 9.0.1 GA release. For a complete list of changes, see the [CHANGELOG][chg] in the GitHub repository. @@ -24,9 +24,9 @@ For a complete list of changes, see the [CHANGELOG][chg] in the GitHub repositor ## Updated modules -PowerShell 7.5-rc.1 includes the following updated modules: +PowerShell 7.5.0 includes the following updated modules: -- **Microsoft.PowerShell.PSResourceGet** v1.1.0-RC2 +- **Microsoft.PowerShell.PSResourceGet** v1.1.0 - **PSReadLine** v2.3.6 ## Tab completion improvements