PowerShell Core 6.1 Arriving This Month but Compatibility Will Lag

PowerShell Core 6.1 is expected to hit the "general availability" (GA) commercial release milestone at the end of this month, but compatibility with some Windows PowerShell modules will lag, according to an announcement by Microsoft this week.

In the announcement, Steve Lee, a principal software engineering manager for the PowerShell team, described the many obstacles the team has encountered in trying to assure the compatibility of PowerShell Core 6.1 with older Windows PowerShell modules. The PowerShell team typically has needed to set up individual projects with other technical groups at Microsoft to make the Windows PowerShell module compatibility happen.

The back story behind this effort is that Microsoft is deprecating Windows PowerShell in favor of the cross-platform PowerShell Core, which works across various Linux platforms, in addition to Windows. Windows PowerShell development essentially ended with version 5.1 and Windows PowerShell 6.0 never got out of the beta test level. Instead, Microsoft proceeded with plans to favor PowerShell Core. Microsoft subsequently slapped the "PowerShell Core 6.0" label onto this new effort and then released it as a commercial product in January.

In moving ahead with PowerShell Core, the PowerShell team wanted to assure that existing Windows PowerShell scripts would continue to work with the new platform. It's been a bumpy road.

In the announcement, Lee outlined Microsoft's new goals in achieving Windows PowerShell module compatibility:

Our target is to get >65% of the Windows PowerShell in-box modules compatible with PowerShell Core 6.1 within the next Windows 10 release. We'll continue to work with Windows partner teams to get the number of compatible modules closer to 100%.

Some of the Windows PowerShell module compatibility will show up for testers of Windows 10 build 17711, which was released to Windows Insider Program participants last month, Lee indicated. However, when PowerShell Core 6.1 reaches the commercial release stage later this month, some of the module compatibility won't be there, he warned.

"It is important to understand that the Windows PowerShell module porting work won't be complete by the time PowerShell Core 6.1 GA nor when the next version of Windows 10 is released, and we expect to continue this work as needed to eventually get complete coverage," he explained.

PowerShell Core 6.0 is considered to be a success already, with an estimated 3 million startups. It's mostly been a success with Linux users, though, as "approximately 80% of the usage is on Linux," Lee indicated.

About the Author

Kurt Mackie is senior news producer for the 1105 Enterprise Computing Group.


  • Azure Active Directory Connect Preview Adds Support for Disconnected AD Forests

    Microsoft on Thursday announced a preview of a new "Cloud Provisioning" feature for the Azure Active Directory Connect service that promises to bring together scattered Active Directory "forests."

  • Microsoft Defender ATP Gets macOS Investigation Support

    The endpoint and detection response (EDR) feature in Microsoft Defender Advanced Threat Protection (ATP) has reached the "general availability" stage for macOS devices.

  • How To Block Self-Service Purchasing in Microsoft's Power Platform

    Microsoft threw Office 365 admins a bone when it gave them the ability to block users from purchasing Power Platform tools without IT approval. Here's how to prevent total anarchy.

  • Azure DevOps Services Losing Support for Alternate Credentials

    Microsoft gave notice last week that it's going to drop Alternate Credentials support for authenticating users of its Azure DevOps Services.

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.