Microsoft released a Win11/10 command-line tool PowerShell 7.2.0 RC1 beta

Windows PowerShell is a command-line shell and scripting environment, allowing command-line users and scriptwriters to take advantage of the powerful features of the .NET Framework. PowerShell can help system administrators and advanced users immediately automate the tasks of managing operating systems (Linux, macOS, and Windows) and processes.

Moreover, the users can use PowerShell commands to manage computers from the command line, and can also use PowerShell providers to access data storage, such as registry and certificate storage, like a file system. Now Microsoft has released a beta version of PowerShell 7.2.0 RC1.

Stay tuned with us via Telegram

Here is the update

• General cmdlet updates and repairs
  COM calls locked by the AppLocker system are not allowed
• Configure Microsoft.ApplicationInsights to not send cloud role names
• Add-Type in NoLanguage mode is not allowed on locked devices
• Make the attribute name of the color VT100 sequence consistent with the document
• Error using Move-Item to move the directory to itself
• Change FileSystemInfo.Target from CodeProperty to AliasProperty, pointing to FileSystemInfo.LinkTarget
• test
• Delete the obsolete Docker-based PowerShell release package test

Build and packaging improvements

Upgrade .NET SDK to 6.0.100-rc.2

• Update .NET 6 to 6.0.100-rc.2.21505.57 version

• Repair RPM packaging (internal 17704)

• Update ThirdPartyNotices.txt

• Update the pipeline YAML file to use the ubuntu-latest image

• Add script to generate cgmanifest.json

• Update the versions of Microsoft.PowerShell.Native and Microsoft.PowerShell.MarkdownRender packages

• Add cgmanifest.json to generate the correct third-party notification file

• Upload stable build info only for the stable version

• Do not upload .dep or .tar.gz for RPM because there is no

• Ensure that the RPM license is recognized

• Add conditions, only generate release files in local development and build

• Ensure that the psoptions.json and manifest.spdx.json files always exist in the package

• Repair CI script and split out an ARM to run

• Update the vPack task version to 12

• Sign third-party executable files

• Add software bill of materials in the main package

• Upgrade the set-value package for markdown testing

• Fix spelling issues in Microsoft Update

• Move the vPack build to the 1ES pool

If you select “Update via Windows Update”, the updated application will be released via Windows Update.