PowerShell is a cross-platform scripting solution available on Windows, MacOS and Linux. Starting with PowerShell version 7.0, developers have switched to stricter lifecycle support, in line with the .NET release. Here’s what’s new in today’s press releases.
What’s New in PowerShell 7.2.0 Preview 3
- 📈 Performance: Avoid assigning tables from Directory.GetDirectories and Directory.GetFiles directories.
- 📈 Performance: avoid string.ToLowerInvariant() from GetEnvironmentVariableAsBool() to avoid loading libicu at startup.
- Performance: Find the PowerShell version in PSVersionInfo using the build attribute instead of FileVersionInfo.
- ✅ Correction: Get date – %u format Behavior according to ISO 8601
- ✅ Bug fixing: With PSDesiredStateConfiguration v3, the module allows to compile Get-DscResource, Invoke-DscResource and DSC configurations on all platforms supported by PowerShell (using DSC class resources).
- ✅ Bug fixing: Write progress in ConsoleHost when redirecting output and correcting tests.
- ✅ Bug fixing: Experimental PSAnsiProgress feature: added a minimal progress bar with ANSI rendering.
- ✅ Fix: web commands correctly build URIs from the body when using -NoProxy
- ✅ Fix: Updated ICommandPredictor to include more comments and make it easier to correlate comments (#14649).
- ✅ Bug fixing: Color reset after writing verbose, debugging and warning messages.
- ✅ Bug fixing: Using a variable for nested ForEach objects -Parallel
- ✅ Correction: When formatting, if the collection is changed, do not lower the whole pipe.
- ✅ Bug fixing: Improved parameter completion for attributes.
- ✅ Bug fixing: Write correct error messages for Get-Command ‘ ‘.
- ✅ Fixed: Typographical error in the ProxyURINotSupplied resource string.
- ✅ Fixed: $PSS style support added for checkers and hyperlinks.
- Fix: $PSStyle codes blinking
What’s new in PowerShell 7.1.2.
- Fixed strange signature for files in subdirectories.
- Update the .NET SDK to version 5.0.103.
- Release of a global toolkit for stable releases
What’s new in PowerShell 7.0.4?
- Remove MyGet strings from Test-Nuget.config
- Update the WXS file for version 7.0.4.
- Update .NET dependencies for version 7.0.4.
- Fixed a bug for the 7.0.4 “Get-Module” test.
- Fix folder creation errors
- Disabling the call test of the WMF connection
- Using PowerShell Core to create and test packages in an IC build
- Disable library-dependent testing for the macro.
- Use a ribbon in any nuget.config in the official builds.
- RPMs signed with a corrected path are loaded from the version compilation.
- Syntax error in a Windows packaging script fixed
- Set the AppLocker Enforce mode to a higher priority than the UMCI Audit mode.
- Error correction with an unsigned module
- Move macros and NuGet to the PRES signature.
- Moving the Windows package signature to use the PRES
- Moving Linux to the PRES signature
- Migration of a third-party signatory to the ESRP
- Do not make a small greenhouse
- Go to PRES signature for Windows files
- Fixed interruptions in daily packet assembly due to macro signature changes.
- Sign individual files in a package
- Use the Authenticode certificate to sign the MSIX
- Sign MSIX files for memory
- Use a temporary private path in the workspace if $env:HOME is not defined.
- Fixed a bug in the MSIX package that used the semantic version string to determine if a preview was released.
- Add default help content to the assets folder
You can find more information on GitHub.
Support us.
Winero is counting on your support. With these options, you can help the site continue to provide you with interesting and useful content and software:
Posted by Sergey Tkachenko on February 12, 2021 in Windows 10.
About Sergei Tkachenko
Sergey Tkachenko is a Russian software developer who founded Winaero in 2011. In this blog Sergey writes about everything related to Microsoft, Windows and popular software. Follow him on Telegram, Twitter and YouTube.
Frequently asked questions
Where can I download PowerShell?
To download the package, launch your browser and go to the PowerShell Github exit page. Scroll down to the Assets section and click on the MSI package share to download it. Make sure you select the correct package for your version of Windows, x64 for 64-bit systems and x86 for 32-bit systems.
What version of PowerShell do I have?
The PowerShell version is removed under the value in the registry key path HKLM:{SOFTWAREMicrosoftPowerShellEngine. This registry key has a value called PowerShellVersion that can be referenced using Get-ItemProperty.
What is the latest version of PowerShell?
PowerShell 7 currently supports the following operating systems on x64, including: Windows 8.1 and 10. Windows Server 2012, 2012 R2, 2016, and 2019. macOS 10.13+.
Related Tags:
powershell 8,powershell 7 ise,hps github com powershell powershell,powershell 7 tutorial,windows terminal powershell 7,new powershell,powershell master github,powershell help github,github powershell issues,github powershell login,github powershell tutorial,powershell 7 download,powershell 5.1 download,powershell core vs powershell,powershell versions,github powershell,the lazy administrator powershell,intune terraform,windows server knowledge base,petri it knowledgebase forums,petri knowledgebase,powershell 7 release date,appveyor multiple images,appveyor worker image,appveyor ubuntu image,appveyor build image,appveyor memory,appveyor update,powershell-7.0.0-win-x64.msi download,powershell 7.0 download,powershell-7.1.0-win-x64.msi download,powershell 7.0.3 download,powershell-7.0.3-win-x64.msi download,powershell 7 github,powershell-7.0.1-win-x64.msi download
