PowerShell can also be used to run scripts and automate and perform administrative tasks. Continue down below to learn what is new in this release and then download it from the direct download links.
Changes and Improvements
PowerShell 7.3.5
[Build and Packaging Improvements] Updated the ThirdPartyNotice. Add PoolNames variable group to the compliance pipeline. Updated cgmanifest.json. Update to .NET 7.0.304. Disable SBOM signing for CI and add extra files for packaging tests. Increase timeout to make subsystem tests more reliable. Increase the timeout when waiting for the event log. Implement IDisposable in NamedPipeClient. Always regenerate files wxs fragment. Bump Microsoft.PowerShell.MarkdownRender. Delete symbols on Linux as well. Add prompt to fix conflict during backport. Add backport function to release tools. Add an explicit manual stage for changelog update. Update the team member list in releaseTools.psm1. Verify that packages have license data. Fix the regex used for package name check-in vPack build. Make the vPack PAT library more obvious. Update the metadata.json to mark 7.3 releases as the latest for the stable channel.
PowerShell 7.2.12 LTS
[Build and Packaging Improvements] Disable SBOM signing for CI and add extra files for packaging tests. Update ThirdPartyNotices. Update the cgmanifest. Add PoolNames variable group to the compliance pipeline. Add a tool to trigger license information gathering for NuGet modules. Update to .NET 6.0.410. Always regenerate files wxs fragment. Add prompt to fix conflict during backport. Add backport function to release tools. Do not remove penimc_cor3.dll from the build. Remove unnecessary native dependencies from the package. Delete symbols on Linux as well. Bump Microsoft.PowerShell.MarkdownRender. Backport compliance changes. Delete the charset regex test. Fix the issue with the merge of 19068. Update the team member list in releaseTools.psm1. Verify that packages have license data. Update experimental-feature.json. Fix the regex used for package name check-in vPack build. Make the vPack PAT library more obvious. Add an explicit manual stage for changelog update.
Let us continue to see how to download and install PowerShell 7.3.5 or 7.2.12 LTS.
Download PowerShell 7.3.5
You can download PowerShell 7.3.5 from the direct download links below.
For Windows 11, 10, 8.1, and 7
PowerShell-7.3.5 for Windows 64-bit.msi [101 MB] PowerShell-7.3.5 for Windows 32-bit.msi [93.1 MB]
For MacOS
PowerShell-7.3.5 for MacOS 64-bit.pkg [65.3 MB] PowerShell-7.3.5 for MacOS ARM64.pkg [62.5 MB]
For Linux
PowerShell-7.3.5 for RedHat Linux.rpm [65.7 MB] PowerShell-7.3.5 for Debian.deb [66.1 MB] For more download options, please check out this download page.
Download PowerShell 7.2.12 LTS
You can download PowerShell 7.2.12 from the direct download links below.
For Windows 11, 10, 8.1, and 7
PowerShell-7.2.12 for Windows 64-bit.msi [101 MB] PowerShell-7.2.12 for Windows 32-bit.msi [92.4 MB]
For MacOS
PowerShell-7.2.12 LTS for MacOS 64-bit.pkg [63.8 MB] PowerShell-7.2.12 LTS for MacOS ARM64.pkg [60.3 MB]
For Linux
PowerShell-7.2.12 LTS for RedHat Linux.rpm [64.6 MB] PowerShell-7.2.12 LTS for Debian.deb [65 MB] For more download options, please check out this download page.
Install PowerShell 7.3.5 or 7.2.12 LTS
Here is how you can install Windows PowerShell on Windows 11, 10, 8.1, and Windows 7: Learn more about PowerShell and PowerShell Core. You can also download and install PowerShell over the network. The installation wizard will now run. Select the optional features to install, such as adding PowerShell to environment variables, enabling PowerShell remoting, adding PowerShell to the context menu, etc. Leave default settings and proceed with the installation
How to uninstall PowerShell
If you do not require PowerShell in the future then you may remove it from your computer. Here is how: The selected version of PowerShell will now be removed from your computer. If asked for confirmation, click Yes.
Final Analysis
The stable release of PowerShell 7.3.5 does not have any significant improvements over its previous versions. However, it is a significant upgrade if you are using PowerShell 6 or any older versions. Either way, there would be no harm in upgrading right now. Additionally, since it is a stable release, most of the glitches and kinks would have already been addressed. If you are a coder, we would suggest that you always test out the recent PowerShell releases to keep up with the latest features and improvements.
