PowerShell Core 6.1.6 is a minor servicing release of the open-source, cross-platform PowerShell that Microsoft shipped on September 26, 2019. It contains only bug fixes and small improvements over 6.1.5, with no new features or breaking changes. This article explains what 6.1.6 is, why it matters, how it fits into the PowerShell release history, and what you should consider before using it.
Background: PowerShell Core vs. Windows PowerShell
PowerShell Core is the modern, cross-platform edition of PowerShell built on .NET Core, whereas Windows PowerShell 5.1 is the legacy edition built on the full .NET Framework. Microsoft introduced PowerShell Core 6.0 in January 2018 as the first version to run on Linux and macOS, in addition to Windows. The “Core” name reflects that it uses the cross-platform .NET Core runtime, not that it is a reduced feature set—it actually includes many new features and improvements over Windows PowerShell, though some Windows-specific cmdlets and modules are not available.
Version 6.1.6 is part of the 6.1 servicing branch, which was a minor update to 6.1 that added a few new features and compatibility improvements. The 6.1 line was supported until September 2019, and 6.1.6 was one of the last releases before the team moved on to PowerShell 7.0.
What’s in the 6.1.6 Release?
As a servicing release, 6.1.6 focused on stability and bug fixes. The official changelog lists several fixes, including:
- Fixed an issue where the
Get-Helpcmdlet could fail on some systems. - Fixed a bug in the
Start-Jobcmdlet that caused a crash when running on Linux. - Improved the
ConvertFrom-Jsoncmdlet to handle certain date formats correctly. - Addressed a memory leak in the
WSManremoting provider.
There were no new cmdlets, no changes to the language, and no breaking changes. The release was primarily aimed at users who rely on PowerShell Core for automation and need a stable, patched version.
How to Get PowerShell Core 6.1.6
You can download the installer for Windows, macOS, or Linux from the official GitHub releases page. The installer packages are available as MSI for Windows, PKG for macOS, and various package formats (deb, rpm, tar.gz) for Linux distributions. After installation, you can verify the version by running:
$PSVersionTable.PSVersion
This should output 6.1.6. If you are using a package manager, you can also install it via winget on Windows, brew on macOS, or apt/dnf on Linux, though the package repositories may not always have the latest servicing release.
How to Choose Between PowerShell Core 6.1.6 and Other Versions
Choosing the right PowerShell version depends on your platform and compatibility needs. Here are the main options as of 2024:
- PowerShell 7.x (current): The latest stable version, built on .NET 8 (for 7.4+). It is the recommended version for all new work, as it includes all features from 6.x and 7.0-7.3, plus ongoing improvements.
- PowerShell 6.1.6: Only if you are stuck on an older system that requires .NET Core 2.1 or if you have a specific script that breaks in 7.x. Otherwise, it is obsolete.
- Windows PowerShell 5.1: Still included with Windows and supported for legacy modules. It is not cross-platform and lacks many newer features.
For most users, the best choice is to use the latest PowerShell 7.x. If you are evaluating 6.1.6, be aware that it is no longer supported and will not receive security updates.
Common Problems and Misconceptions
One common misconception is that PowerShell Core 6.1.6 is the same as PowerShell 6.1.5, just with a different version number. In reality, it includes specific bug fixes that can affect real-world scenarios. For example, the memory leak fix in WSMan remoting is crucial for long-running automation jobs that use remoting.
Another issue users face is that some Windows-only modules (like ActiveDirectory or DnsClient) do not work in PowerShell Core. This is because those modules rely on the full .NET Framework. If you need those modules, you must use Windows PowerShell 5.1 or run PowerShell Core with the WindowsCompatibility module, which is not perfect.
Also, note that PowerShell Core 6.1.6 does not support the #requires statement with the -Version parameter for versions above 6.1.6, so scripts that specify #requires -Version 7 will fail.
Comparison: 6.1.6 vs. 7.0
PowerShell 7.0 was released in March 2020, just a few months after 6.1.6. It was a major upgrade that brought:
- Compatibility with Windows PowerShell modules via the
WindowsPSCompatmodule. - New operators like
??(null-coalescing) and??=. - Pipeline chaining with
&&and||. - Improved performance and reduced memory usage.
For example, a script that uses the null-coalescing operator will only run on PowerShell 7+, not on 6.1.6. If you are writing new scripts, targeting 7.x is the way to go.
Costs and Licensing
PowerShell Core is free and open-source, licensed under the MIT License. There is no cost to download, use, or modify it. This applies to all versions, including 6.1.6. However, support costs can be a factor: Microsoft only provides support for the latest version, so using 6.1.6 means you are on your own if you encounter issues.
Safety and Security Considerations
Using an unsupported version like 6.1.6 carries security risks. Since it is no longer patched, any vulnerabilities discovered after September 2019 remain unaddressed. For example, if a security flaw is found in the .NET Core runtime that 6.1.6 depends on, you would not receive a fix unless you upgrade. Always prefer the latest stable release for any production use.
Additionally, be cautious when running scripts from untrusted sources, regardless of the PowerShell version. Use execution policies and code signing to protect your system.
Frequently Asked Questions
Is PowerShell Core 6.1.6 the same as PowerShell 6.1.5?
No, 6.1.6 includes specific bug fixes over 6.1.5, such as the WSMan memory leak and a crash in Start-Job on Linux. The version number difference indicates those fixes are present.
Can I run Windows PowerShell modules in PowerShell Core 6.1.6?
Some modules work, but many that depend on the full .NET Framework do not. You can try the WindowsCompatibility module, but it is not guaranteed to work for all modules.
Why would anyone still use 6.1.6 instead of 7.x?
Usually because they have a legacy script that breaks in 7.x, or they are stuck on an operating system that only supports .NET Core 2.1. But these cases are rare, and upgrading is recommended.
How do I uninstall PowerShell Core 6.1.6?
On Windows, use the Control Panel or Settings to uninstall the MSI. On macOS, delete the app bundle. On Linux, use your package manager (e.g., apt remove powershell).
Is PowerShell Core 6.1.6 still supported by Microsoft?
No, support ended in September 2019. Only the latest PowerShell 7.x releases receive support.
What is the difference between PowerShell Core and PowerShell 7?
PowerShell 7 is the successor to PowerShell Core 6.x. It is built on .NET Core 3.1 (7.0) and later .NET 8 (7.4), and it adds many features, including better compatibility with Windows PowerShell modules.
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
- Reliable Subaru vs New Honda Civic Cost
- Pokemon Bookmark Corner Designs & Pokemon GO DIY
- Forgotten Games That Created Your Favorite Genres
- Lexus vs Genesis Luxurious Compact SUV0.075 hp/lb
- Uber VW Robotaxi LA Launch Date
- Notebook vs Tablet: Which Saves You More Money?