V6 0 1 PowerShell Core Release: What It Is

V6 0 1 of PowerShell Core is the first patch release of PowerShell 6.0, the cross-platform, open-source edition of PowerShell built on .NET Core. It fixes bugs found in the initial 6.0.0 release while keeping the same feature set, and it is the version you should install if you need the stability of a patched 6.0 without moving to a newer minor version.

Background: Why PowerShell Core Exists

PowerShell has been a Windows-only automation tool since 2006, but by 2016 Microsoft began a project to make it run on Linux and macOS. The result was PowerShell Core, a separate edition from the classic Windows PowerShell 5.1. It uses .NET Core instead of the full .NET Framework, which allows the same code to run on multiple operating systems. The first stable release, 6.0.0, arrived in January 2018, and 6.0.1 followed in February 2018 as a servicing update.

The key difference between editions is the runtime and compatibility. Windows PowerShell 5.1 runs only on Windows and can load many Windows-specific modules. PowerShell Core 6.x runs on Windows, Linux, and macOS, but it cannot load modules that depend on the full .NET Framework. This is why some older scripts fail under Core even though they work in 5.1.

What Changed in 6.0.1

Version 6.0.1 was a patch release, meaning it did not add new features. Instead, it addressed a handful of bugs and regressions that were reported after 6.0.0 shipped. The release notes list fixes in areas such as the Start-Job cmdlet on non-Windows platforms, the Get-Help command when help files are missing, and the handling of certain pipeline input in ForEach-Object. It also included a fix for a crash that could occur when using the Import-Csv cmdlet with very large files.

For most users, upgrading from 6.0.0 to 6.0.1 is safe and recommended. The update is backward-compatible within the 6.0 series, so scripts that ran on 6.0.0 will run on 6.0.1 without modification. You can check your current version with $PSVersionTable.PSVersion.

How to Install or Update to 6.0.1

Installation depends on your operating system. Microsoft provided installers for Windows (MSI), macOS (PKG), and Linux (package managers like apt, yum, or dnf). For Windows, download the PowerShell-6.0.1-win-x64.msi file from the official GitHub releases page and run it. The installer will replace an existing 6.0.0 installation if present.

On Linux, the exact command varies by distribution. For Ubuntu, you would typically use sudo apt-get install powershell after adding the Microsoft repository. On macOS, the PKG installer works like any other. After installation, launch pwsh (the executable name for PowerShell Core) and verify the version:

pwsh -Command "$PSVersionTable.PSVersion"

If you see 6.0.1, the update succeeded. If you are using a package manager, you may need to update the package list first, for example sudo apt-get update on Debian-based systems.

Key Differences from Windows PowerShell 5.1

PowerShell Core 6.x is not a drop-in replacement for 5.1. The most significant differences include:

• Cross-platform support: 6.x runs on Linux and macOS, while 5.1 is Windows-only.
• .NET Core vs .NET Framework: Modules compiled for .NET Framework will not load in Core.
• Cmdlet availability: Some cmdlets are missing or changed. For example, the Computer cmdlets like Get-ComputerInfo are not available in 6.x.
• Default execution policy: On Windows, Core uses the same execution policy as 5.1, but on Linux and macOS, there is no execution policy enforcement.
• Remoting: PowerShell Remoting (WinRM) works on Windows, but on Linux and macOS, SSH remoting is the primary method.

If your scripts rely on Windows-specific features, they will likely break in Core. Microsoft provides a compatibility layer called WindowsCompatibility that can load some Windows modules, but it is not a complete solution.

Common Problems and How to Solve Them

One frequent issue after installing 6.0.1 is that the pwsh command is not found. This usually happens when the installation directory is not in the PATH. On Windows, the MSI adds it automatically; on Linux, you may need to add the symlink manually or reinstall using the package manager. Check the installation path, typically /opt/microsoft/powershell/6.0.1/pwsh on Linux.

Another problem is that modules from the PowerShell Gallery fail to install because they target .NET Framework. Use the -Scope CurrentUser parameter and ensure the module supports PowerShell Core. Many popular modules have been updated to work with Core, but not all.

If you see errors about missing dependencies on Linux, install the prerequisites listed in the official documentation, such as libunwind8 and libicu52 for older Ubuntu versions. These are required by .NET Core.

How to Choose Between 6.0.1 and Later Versions

PowerShell 6.0.1 is not the latest version today, but it is still relevant for legacy systems. If you need a stable, patched 6.0 release, 6.0.1 is the final patch for that series. However, if you want the latest features and security fixes, you should consider PowerShell 7.x, which is the current long-term servicing (LTS) version. PowerShell 7 is also cross-platform and built on .NET Core, but it includes many improvements and is the recommended choice for new projects.

When deciding, consider compatibility with your existing scripts. If you have a large base of scripts written for 5.1, test them on 6.0.1 first, but be prepared for breaking changes. If you are starting fresh, go with PowerShell 7. The 6.x series is no longer supported, so for production use, upgrade to a supported version.

Frequently Asked Questions

Is PowerShell Core 6.0.1 free to use?

Yes, PowerShell Core is open-source (MIT license) and free to download and use, including for commercial purposes. You can find the source code on GitHub.

Can I run PowerShell Core side-by-side with Windows PowerShell?

Yes. PowerShell Core installs as pwsh.exe on Windows, while Windows PowerShell remains as powershell.exe. They are separate executables and can coexist without conflict.

Will my Windows PowerShell modules work in 6.0.1?

Only if they are compatible with .NET Core. Modules that use .NET Framework APIs will fail to load. You can try the WindowsCompatibility module, but it is not guaranteed to work for all modules.

How do I uninstall PowerShell Core 6.0.1?

On Windows, use the standard “Add or Remove Programs” and select PowerShell 6.0.1. On Linux, use your package manager, e.g., sudo apt-get remove powershell. On macOS, delete the application from the Applications folder.

Is 6.0.1 still supported by Microsoft?

No. PowerShell 6.0 reached end-of-life in February 2019. Microsoft only provides support for the latest LTS version, currently PowerShell 7.2 and later. It is recommended to upgrade to a supported version for security updates.

Related

• Dusk Dawn Essential MK2: Who Should Buy It?
• Floor Plan Designers: How to Choose & Use Them
• How a Crude Oil Refinery Turns Crude Into Fuel