There is no official release called “V6 2 0” of PowerShell Core. The version you are thinking of is PowerShell Core 6.2, which was released on March 28, 2019, as the second minor update in the 6.x series. This article explains what PowerShell Core is, the specifics of the 6.2 release, how it differs from Windows PowerShell, and how to choose between them.
Background: What Is PowerShell Core?
PowerShell Core is the cross-platform, open-source edition of PowerShell, built on the .NET Core runtime. It was introduced with version 6.0 in January 2018, after Microsoft announced that PowerShell would be available on Linux and macOS in addition to Windows. The “Core” in the name refers to the underlying .NET Core framework, which allows it to run on multiple operating systems. PowerShell Core 6.2 is the last minor release before the major version 7.0, which was released in March 2020 and later renamed simply “PowerShell” (with the 7.x series).
The 6.2 Release: What Was New?
PowerShell Core 6.2 was a minor release, meaning it focused on bug fixes, performance improvements, and some new features rather than major architectural changes. Key additions included:
- Improved error handling for native commands, making it easier to catch and handle errors from external executables.
- New operators such as
-Notand!for boolean negation, and-Joinand-Splitenhancements. - Better support for Windows with the introduction of the
WindowsPScompatibility layer, which allowed using Windows PowerShell modules from PowerShell Core. - Performance improvements in areas like pipeline execution and string handling.
- Updated help system that works offline, using updatable help files.
This release was supported on Windows 7 and later, macOS 10.12 and later, and several Linux distributions including Ubuntu, Debian, CentOS, and Fedora.
How to Get PowerShell Core 6.2
You can download PowerShell Core 6.2 from the official GitHub releases page (microsoft/PowerShell). It was distributed as MSI packages for Windows, PKG for macOS, and various package formats (DEB, RPM, tar.gz) for Linux. Alternatively, you could install it via package managers like choco install powershell-core on Windows, brew tap microsoft/powershell && brew install powershell on macOS, or snap install powershell --classic on Linux. After installation, you run it by typing pwsh in your terminal, which is the executable name for PowerShell Core.
PowerShell Core vs. Windows PowerShell
Windows PowerShell (versions 5.1 and earlier) is the classic edition that runs only on Windows and is built on the full .NET Framework. PowerShell Core (6.x) is cross-platform and built on .NET Core. The main differences include:
- Compatibility: Windows PowerShell can use all Windows-specific modules (e.g., ActiveDirectory, NetAdapter) without extra steps, while PowerShell Core requires the WindowsPS compatibility layer to run many of them.
- Performance: PowerShell Core generally starts faster and uses less memory because .NET Core is more efficient.
- Language features: PowerShell Core introduced new operators and improved error handling, but also removed some features that relied on the full .NET Framework (like certain COM and WMI cmdlets).
- Future: Microsoft announced that Windows PowerShell 5.1 is the last version of Windows PowerShell, and all future development is in PowerShell (7.x), which is based on .NET Core (now .NET 5+).
How to Choose: Which Should You Use?
If you are starting a new automation project and do not rely on Windows-only modules, PowerShell Core (or the newer PowerShell 7) is the recommended choice because it is actively maintained and cross-platform. If you manage Windows servers with legacy modules that do not yet support .NET Core, you may need to stick with Windows PowerShell 5.1 or use the compatibility layer. For most users today, the best option is to install PowerShell 7.x, which is the successor to Core and includes all its benefits plus additional Windows compatibility. PowerShell Core 6.2 is now out of support, so for production use, upgrade to a supported version.
Common Problems and Misconceptions
One common misconception is that PowerShell Core cannot run on Windows at all, which is false. It runs on Windows, but it is a separate installation from Windows PowerShell. Another issue is that some modules written for Windows PowerShell fail to load in Core because they reference .NET Framework assemblies. The workaround is to use the WindowsPS compatibility layer, but not all modules are compatible. Also, users often confuse the version number: there is no “V6 2 0”; the correct version format is major.minor.patch, so 6.2.0 is the full version, and the release is referred to as 6.2.
Frequently Asked Questions
Is PowerShell Core 6.2 still supported?
No. PowerShell Core 6.2 reached its end of support on September 4, 2020, when the 6.x series was retired. Microsoft recommends upgrading to PowerShell 7.0 or later, which is the current supported version.
Can I run both Windows PowerShell and PowerShell Core on the same machine?
Yes. They are separate applications and can coexist. Windows PowerShell is installed as powershell.exe, and PowerShell Core is installed as pwsh.exe. You can choose which one to run from the Start menu or terminal.
How do I update from PowerShell Core 6.2 to a newer version?
You can download the latest MSI or package from the official GitHub releases and install it over the existing version. The installer will replace the old files. Alternatively, you can use package managers like winget on Windows or brew upgrade on macOS.
Why is the executable called pwsh?
The name pwsh was chosen to avoid conflicts with the existing powershell.exe and to be short enough for cross-platform use. It is the standard command to launch PowerShell Core on all operating systems.
Does PowerShell Core support all cmdlets from Windows PowerShell?
No. Some cmdlets that depend on the full .NET Framework or Windows-specific components are not available. However, the WindowsPS compatibility layer allows many of them to run, but with potential performance or functionality limitations.
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
- Skip Ryobi and Milwaukee? Harbor Freight Tools to Buy
- Funny Subreddits That Make You Laugh
- Why Retro Gaming Is Still Worth Playing Today
- Neptune Facts That Will Blow Your Mind
- Survival Crafting Game Fatigue: Why & How to Fix It
- Sell Your EV Now Before Prices Plummet?