keepcalculator

06 Numbers and Powers

V6 2 7 Release of PowerShell: What It Means

Card No. 06·6163 · Updated · Standard formula, shown below

The “V6 2 7 release of PowerShell” refers to PowerShell Core 6.2.7, a maintenance update to the cross-platform version of Microsoft’s scripting language and automation framework. This specific patch release, issued in September 2020, fixed bugs and security issues without adding new features. If you are running PowerShell Core 6.2.x, upgrading to 6.2.7 is recommended for stability and security.

Background: PowerShell Core and the 6.x Line

PowerShell 6.0, released in 2018, marked a major departure: it was built on .NET Core instead of the Windows-only .NET Framework, making it available on Linux and macOS. Microsoft branded this version “PowerShell Core” to distinguish it from the classic Windows PowerShell 5.1. The 6.x series was the first to be open-source and cross-platform, but it also had a shorter support lifecycle than the Windows-only versions.

Version 6.2, released in March 2019, was the last minor version in the 6.x line. It introduced several improvements, including better error handling and support for newer operating systems. The 6.2.x updates were strictly servicing releases: they addressed bugs, security vulnerabilities, and compatibility issues without changing the feature set.

What Changed in 6.2.7

PowerShell Core 6.2.7 was a patch release, meaning it contained only bug fixes and security updates. According to the official changelog, notable fixes included:

  • Resolved a bug where the `Get-Content` cmdlet could fail on certain file paths on Linux.
  • Fixed an issue with `Start-Job` that could cause a hang when the job output was too large.
  • Updated the underlying .NET Core runtime to a newer patch version, addressing several security vulnerabilities.
  • Improved compatibility with newer versions of OpenSSL on Linux.

No new cmdlets or features were added in 6.2.7. The focus was purely on stability and security.

How to Check Your Current Version

Before upgrading, you should verify which version of PowerShell you are running. Open a PowerShell prompt and type:

$PSVersionTable.PSVersion

This command returns the version number. If it starts with 6.2 and is lower than 6.2.7, you should update. If you are on 7.x, you are already on a newer major version and do not need 6.2.7.

How to Install or Upgrade to 6.2.7

The installation method depends on your operating system:

  • Windows: Download the MSI package from the official GitHub releases page and run it. The installer will replace your existing PowerShell Core 6.2.x installation.
  • Linux (Ubuntu/Debian): Use the package manager: sudo apt-get update && sudo apt-get install -y powershell (after adding the Microsoft repository).
  • macOS: Use Homebrew: brew update && brew install powershell or brew upgrade powershell if already installed.

After installation, confirm the new version with the same $PSVersionTable command.

Common Problems and Solutions

Users upgrading to 6.2.7 sometimes encounter issues:

  • Scripts that worked in 5.1 fail in 6.x: PowerShell Core is not fully backward-compatible. Some cmdlets and modules are missing or behave differently. Check the official “Breaking Changes” documentation for the 6.0 release.
  • Modules not loading: Modules written for Windows PowerShell may not work in Core. Look for a Core-compatible version or use the Compatibility module.
  • Execution policy errors on Linux/macOS: The execution policy is not enforced the same way as on Windows. You may need to set it explicitly with Set-ExecutionPolicy.

If you encounter a bug that is not fixed in 6.2.7, consider upgrading to PowerShell 7.x, which is the actively maintained version.

Why You Should Upgrade to PowerShell 7 Instead

PowerShell 7 was released in March 2020, and it is the successor to 6.2. It is built on .NET Core 3.1 (and later .NET 5/6/7/8), which is faster and more compatible with modern libraries. PowerShell 7 also brings back many features that were missing in 6.x, such as:

  • Parallel execution with ForEach-Object -Parallel.
  • New operators like ternary and null-coalescing.
  • Improved compatibility with Windows PowerShell modules.

Microsoft’s support policy for PowerShell Core 6.2 ended in September 2020, the same month 6.2.7 was released. This means no further updates will be provided for the 6.x line. For long-term support, you should move to PowerShell 7.x, which is supported under the .NET support policy.

Cost and Licensing

PowerShell Core is free and open-source, licensed under the MIT License. There is no cost to download, use, or redistribute it. This applies to all versions, including 6.2.7 and 7.x. The only cost is the time to install and learn it.

Alternatives to PowerShell Core

If you are not tied to Microsoft’s ecosystem, there are other cross-platform shells and scripting tools:

  • Bash: The default on Linux and macOS, powerful for text processing and system administration.
  • Zsh: An extended Bash with better scripting and autocompletion.
  • Python: Not a shell, but a general-purpose language often used for automation tasks that would require complex shell scripts.

However, if you already use Windows and need to manage Microsoft services (Active Directory, Exchange, Azure), PowerShell remains the most integrated choice.

Frequently Asked Questions

Is PowerShell 6.2.7 the latest version?

No. The latest stable version is PowerShell 7.x (as of 2025, 7.4 or newer). 6.2.7 was the final release of the 6.x series, which is now out of support.

Can I run PowerShell 6.2.7 alongside Windows PowerShell 5.1?

Yes. PowerShell Core installs as a separate executable (pwsh.exe on Windows) and does not replace Windows PowerShell. You can run both side by side, but scripts may behave differently between them.

Will my existing PowerShell scripts work in 6.2.7?

Most scripts written for Windows PowerShell 5.1 will work, but some may fail due to missing cmdlets or modules. Test your scripts after upgrading. The Compatibility module can help load Windows PowerShell modules in Core.

How do I uninstall PowerShell 6.2.7?

On Windows, use “Add or Remove Programs” and select PowerShell 6.2.7. On Linux, use sudo apt-get remove powershell (or your package manager’s remove command). On macOS, brew uninstall powershell.

Is PowerShell Core 6.2.7 secure?

It was secure at the time of release, but since it is no longer supported, new security vulnerabilities will not be patched. For production environments, upgrade to PowerShell 7.x to receive security updates.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →