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)
Stop-Processcmdlet on Unix (#10098) (Thanks @iSazonov!)
- Support for starting PowerShell as a login shell (
pwsh -l) support (#10050)
Engine Updates and Fixes
- Additional Telemetry – implementation of
ForEach-Object -Parallelas an experimental feature (#10229)
Get-DscResourcework with class based resources (#10350)
pwsh7 to include
PSCompatibleVersions(#9943) (Thanks @bgelens!)
- Add dispose of
_runspaceDebugCompleteEventevent object. (#10323)
- Fix performance regression from disabling debugger in system lockdown mode (#10269)
- Special case the
Platform.IsWindowsDesktopinstead of checking both NanoServer and IoT (#10205)
General Cmdlet Updates and Fixes
- Enable Experimental Features by default on Preview builds (#10228)
-stais required for
- Make breakpoints display better over PowerShell remoting (#10339) (Thanks @KirkMunro!)
- Add support for
AppXreparse points (#10331)
- Make module name matching for
get-module -FullyQualifiedNamecase insensitive (#10329)
Select-Stringwhich allows returning only the string that was matched (#9901) (Thanks @Jawz84!)
- Reduce allocations in
MakePath()method (#10027) (Thanks @iSazonov!)
- Remove extra check that the system dll exists (#10244) (Thanks @iSazonov!)
- Avoid boxing when passing value type arguments to
PSTraceSource.WriteLine(#10052) (Thanks @iSazonov!)
- Reduce allocations in
Unescape()(#10041) (Thanks @iSazonov!)
- Add the license header to
switchstatements (#10328) (Thanks @KirkMunro!)
- Deprecate workflow debugging code (#10321) (Thanks @KirkMunro!)
- Fix style issues in
InternalCommands.cs(#10352) (Thanks @iSazonov!)
- Deprecate internal
HelpCategory.Workflowenumeration (#10319) (Thanks @KirkMunro!)
Microsoft.PowerShell.CoreCLR.Eventingto resolve conflict with
- Don’t collect process start time as it’s not being used on
- .NET Core 3.0 now aborts the thread for us. Remove the
ThreadAbortExceptioncode (#10230) (Thanks @iSazonov!)
PathInfo(#10200) (Thanks @iSazonov!)
- Fix Hungarian prefix
my(#9976) (Thanks @RDIL!)
- Fix spelling error in issue template (#10256)
- Quote arguments in
.vscode/tasks.jsonin case of spaces (#10204) (Thanks @msftrncs!)
markdownlinttests due to security issues (#10163)
- Add tests for
Unescape()(#10090) (Thanks @iSazonov!)
- Cleanup Docker release testing (#10310) (Thanks @RDIL!)
Build and Packaging Improvements
- Move to
.NET Core 3.0 preview.8(#10351) (#10227) (Thanks @bergmeister!)
Microsoft.PowerShell.CoreCLR.Eventing.dllto exception list for build fix (#10337)
- Revert the temporary AzDevOps artifact workaround (#10260)
- Fix macOS build break (#10207)
Documentation and Help Content
- Update docs for
7.0.0-preview.2release (#10160) (#10176)
PSSAalso includes formatting (#10172)
- Refactor security policy documentation so that they appear in the Security policy tab of GitHub (#9905) (Thanks @bergmeister!)
- Add tooling section to PR template (#10144)
metadata.jsonfor next releases (#10087)
- Update DotNet Support links (#10145)
- Update our language on our policy applying to security issues (#10304)
- Update dead links from
Distribution_Requestissue template (#10253)
- Fix: Removed dependency file with
Dependabot(#10212) (Thanks @RDIL!)