PowerShell Core is a cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework that works well with your existing tools and is optimized for dealing with structured data (e.g. JSON, CSV, XML, etc.), REST APIs, and object models. It includes a command-line shell, an associated scripting language and a framework for processing cmdlets.
What’s the difference between Windows PowerShell and PowerShell Core?
There are now two editions of PowerShell:
Windows PowerShell is the edition of PowerShell built on top of .NET Framework
(sometimes referred to as “FullCLR”):
- This is the PowerShell that has been in widespread use for the last ~10 years.
- Because of it’s dependency on the .NET Framework, Windows PowerShell is only available on Windows (hence the name).
- The released versions of Windows PowerShell include 1.0, 2.0, 3.0, 4.0, 5.0, and 5.1.
- Windows PowerShell is available as a built-in component in Windows client and Windows Server.
- Windows PowerShell is launched as powershell.exe.
- On Windows PowerShell 5.0/5.1, $PSVersionTable.PSEdition is set to Desktop.
- Any usage of .NET-based functionality (e.g. C# cmdlets, Add-Type, and the invocation of static .NET Methods), relies on the .NET Framework runtime. This means Windows PowerShell’s .NET usage is limited to the functionality exposed by the .NET Framework and .NET Standard.
- Continues to be supported via critical bug fixes in the newest releases of Windows and Windows Server
PowerShell Core is the edition of PowerShell built on top of .NET Core
(sometimes simplified to “CoreCLR”).
- PowerShell Core is cross-platform, available on Windows, macOS, and Linux, thanks to the cross-platform nature of .NET Core.
- PowerShell Core is launched as pwsh.exe on Windows and pwsh on macOS and Linux
- On PowerShell Core, $PSVersionTable.PSEdition is set to Core.
Note: while PowerShell Core 6.0 is cross-platform, there is also a PowerShell Core 5.0/5.1 released exclusively as part of Microsoft Nano Server.
- Any usage of .NET-based functionality (e.g. C# cmdlets, Add-Type, and the invocation of static .NET Methods), relies on the .NET Core runtime. This means PowerShell Core is limited to the functionality exposed by .NET Core and .NET Standard.
PowerShell Core is officially supported on the following platforms:
- Windows 7, 8.1, and 10
- Windows Server 2008 R2, 2012 R2, 2016
- Windows Server Semi-Annual Channel
- Ubuntu 14.04, 16.04, and 17.04
- Debian 8.7+, and 9
- CentOS 7
- Red Hat Enterprise Linux 7
- OpenSUSE 42.2
- Fedora 25, 26
- macOS 10.12+
Our community has also contributed packages for the following platforms,
but they are not officially supported:
- Arch Linux
- Kali Linux
- AppImage (works on multiple Linux platforms)
Engine Updates and Fixes
- Revert the PRs that made
General Cmdlet Updates and Fixes
- Fix an operator preference order issue in binder code (#12075) (Thanks @DamirAinullin!)
NullReferenceExceptionwhen binding common parameters of type
- Fix default formatting for deserialized
MatchInfo(#11728) (Thanks @iSazonov!)
- Use asynchronous streams in
Invoke-RestMethod(#11095) (Thanks @iSazonov!)
- Address UTF-8 Detection In
Get-Content -Tail(#11899) (Thanks @NoMoreFood!)
- Handle the
Get-FileHash(#11944) (Thanks @iSazonov!)
- Change ‘PowerShell Core’ to ‘PowerShell’ in a resource string (#11928) (Thanks @alexandair!)
- Bring back
PSHostProcessInfo(#11885) (Thanks @iSazonov!)
- Miscellaneous minor updates to Windows Compatibility (#11980)
- Remove network hop restriction for interactive sessions (#11920)
RestoreStoppingPipeline()(#11870) (Thanks @iSazonov!)
- Generate GUID for
InstanceIdif not provided (#11896)
ConciseViewwhere error message is wider than window width and doesn’t have whitespace (#11880)
- Allow cross-platform
CAPI-compatibleremote key exchange (#11185) (Thanks @silijon!)