Windows 10: New PowerShell 7.0.1 version has been released - May 14

Brink · May 16, 2020

PowerShell 7.0.1 - 2020-05-14

Diff from 7.0.0

Engine Updates and Fixes

Discover assemblies loaded by Assembly.Load(byte[]) and Assembly.LoadFile (#12203)

Allow case insensitive paths for determining PSModulePath (#12192)

General Cmdlet Updates and Fixes

Add null check for Windows PowerShell install path (#12296)

Fix Null Reference error in CSV commands (#12281) (Thanks @iSazonov!)

Fix WinCompat module loading to treat Core edition modules higher priority (#12269)

Fix <img /> detection regex in web cmdlets (#12099) (Thanks @vexx32!)

Miscellaneous minor updates to WinCompat (#11980)

Fix ConciseView where error message is wider than window width and doesn't have whitespace (#11880, #11746)

Make Test-Connection always use the default synchronization context for sending ping requests (#11517)

Tests

Fix CIM tab complete test failure (#12636)

Build and Packaging Improvements

Move to .NET Core 3.1.202 SDK and update packages.

Use dotnet core 3.1.202 (Internal 11551)

Bump PowerShellGet from 2.2.3 to 2.2.4 (#12342)

Move to standard internal pool for building (#12119)

Bump NJsonSchema from 10.1.5 to 10.1.7 (#12050)

Documentation and Help Content

Remove the version number of PowerShell from LICENSE (#12019)

Click to expand...

Source: https://github.com/PowerShell/PowerShell/releases

See also: https://devblogs.microsoft.com/power...owerShell-7-0/

How to Install PowerShell 7.0.1 in Windows 7, Windows 8, and Windows 10

:)

Brink · May 16, 2020

New Powershell Core v7.0.0-rc.1 released

PowerShell version 7 RC1 has just been released.

v7.0.0-rc.1 - 12/16/2019

Breaking Changes

Make update notification support LTS and default channels (#11132)

Engine Updates and Fixes

Improvements in breakpoint APIs for remote scenarios (#11312)

Fix PowerShell class definition leaking into another Runspace (#11273)

Fix a regression in formatting caused by the FirstOrDefault primitive added in 7.0.0-Preview1 (#11258)

Additional Microsoft Modules to track in PS7 Telemetry (#10751)

Make approved features non-experimental (#11303)

Update ConciseView to use TargetObject if applicable (#11075)

Fix NullReferenceException in CompletionCompleters public methods (#11274)

Fix apartment thread state check on non-Windows platforms (#11301)

Update setting PSModulePath to concatenate the process and machine environment variables (#11276)

Bump .NET Core to 3.1.0 (#11260)

Fix detection of $PSHOME in front of $envATH (#11141)

Click to expand...

Release v7.0.0-rc.1 Release of PowerShell Core . PowerShell/PowerShell . GitHub

Brink · May 16, 2020

The Next Release of PowerShell - PowerShell 7

Recently, the PowerShell Team shipped the Generally Available (GA) release of PowerShell Core 6.2. Since that release, we’ve already begun work on the next iteration!

We’re calling the next release PowerShell 7, the reasons for which will be explained in this blog post.

Why 7 and not 6.3?

PowerShell Core usage has grown significantly in the last two years. In particular, the bulk of our growth has come from Linux usage, an encouraging statistic given our investment in making PowerShell viable cross-platform. This chart represents the number of times pwsh.exe (or just pwsh on Linux/macOS) was started (unless telemetry was disabled).

However, we also can clearly see that our Windows usage has not been growing as significantly, surprising given that PowerShell was popularized on the Windows platform. We believe that this could be occurring because existing Windows PowerShell users have existing automation that is incompatible with PowerShell Core because of unsupported modules, assemblies, and APIs. These folks are unable to take advantage of PowerShell Core’s new features, increased performance, and bug fixes. To address this, we are renewing our efforts towards a full replacement of Windows PowerShell 5.1 with our next release.

This means that Windows PowerShell and PowerShell Core users will be able to use the same version of PowerShell to automate across Windows, Linux, and macOS and on Windows, and PowerShell 7 users will have a very high level of compatibility with Windows PowerShell modules they rely on today.

We’re also going to take the opportunity to simplify our references to PowerShell in documentation and product pages, dropping the “Core” in “PowerShell 7”. The PSEdition will still reflect Core, but this will only be a technical distinction in APIs and documentation where appropriate.

Note that the major version does not imply that we will be making significant breaking changes. While we took the opportunity to make some breaking changes in 6.0, many of those were compromises to ensure our compatibility on non-Windows platforms. Prior to that, Windows PowerShell historically updated its major version based on new versions of Windows rather than Semantic Versioning

.NET Core 3.0

PowerShell Core 6.1 brought compatibility with many built-in Windows PowerShell modules, and our estimation is that PowerShell 7 can attain compatibility with 90+% of the inbox Windows PowerShell modules by leveraging changes in .NET Core 3.0 that bring back many APIs required by modules built on .NET Framework so that they work with .NET Core runtime. For example, we expect Out-GridViewto come back (for Windows only, though)!

A significant effort for PowerShell 7 is porting the PowerShell Core 6 code base to .NET Core 3.0 and also working with Windows partner teams to validate their modules against PowerShell 7.

Support Lifecycle Changes

Currently, PowerShell Core is under the Microsoft Modern Lifecycle Policy. This means that PowerShell Core 6 is fix-forward: we produce servicing releases for security fixes and critical bug fixes, and you must install the latest stable version within 6 months of a new minor version release.

In PowerShell 7, we will align more closely with the .NET Core support lifecycle, enabling PowerShell 7 to have both LTS (Long Term Servicing) and non-LTS releases.

We will still have monthly Preview releases to get feedback early.

When do I get PowerShell 7?

The first Preview release of PowerShell 7 will likely be in May. Be aware, however, that this depends on completing integration and validation of PowerShell with .NET Core 3.0.

Since PowerShell 7 is aligned with the .NET Core timeline, we expect the generally available (GA) release to be some time after the GA of .NET Core 3.0.

What about shipping in Windows?

We are planning on eventually shipping PowerShell 7 in Windows as a side-by-side feature with Windows PowerShell 5.1, but we still need to work out some of the details on how you will manage this inbox version of PowerShell 7.

And since the .NET Core timeline doesn’t align with the Windows timeline, we can’t say right now when it will show up in a future version of Windows 10 or Windows Server.

What other features will be in PowerShell 7?

We haven’t closed on our feature planning yet, but expect another blog post relatively soon with a roadmap of our current feature level plans for PowerShell 7.

Steve Lee
Steve Lee (@Steve_MSFT) | Twitter
Principal Engineering Manager
PowerShell Team
Click to expand...

Source: The Next Release of PowerShell - PowerShell 7 | PowerShell

Brink · May 16, 2020

The Next Release of PowerShell - PowerShell 7

Recently, the PowerShell Team shipped the Generally Available (GA) release of PowerShell Core 6.2. Since that release, we’ve already begun work on the next iteration!

We’re calling the next release PowerShell 7, the reasons for which will be explained in this blog post.

Why 7 and not 6.3?

PowerShell Core usage has grown significantly in the last two years. In particular, the bulk of our growth has come from Linux usage, an encouraging statistic given our investment in making PowerShell viable cross-platform. This chart represents the number of times pwsh.exe (or just pwsh on Linux/macOS) was started (unless telemetry was disabled).

However, we also can clearly see that our Windows usage has not been growing as significantly, surprising given that PowerShell was popularized on the Windows platform. We believe that this could be occurring because existing Windows PowerShell users have existing automation that is incompatible with PowerShell Core because of unsupported modules, assemblies, and APIs. These folks are unable to take advantage of PowerShell Core’s new features, increased performance, and bug fixes. To address this, we are renewing our efforts towards a full replacement of Windows PowerShell 5.1 with our next release.

This means that Windows PowerShell and PowerShell Core users will be able to use the same version of PowerShell to automate across Windows, Linux, and macOS and on Windows, and PowerShell 7 users will have a very high level of compatibility with Windows PowerShell modules they rely on today.

We’re also going to take the opportunity to simplify our references to PowerShell in documentation and product pages, dropping the “Core” in “PowerShell 7”. The PSEdition will still reflect Core, but this will only be a technical distinction in APIs and documentation where appropriate.

Note that the major version does not imply that we will be making significant breaking changes. While we took the opportunity to make some breaking changes in 6.0, many of those were compromises to ensure our compatibility on non-Windows platforms. Prior to that, Windows PowerShell historically updated its major version based on new versions of Windows rather than Semantic Versioning

.NET Core 3.0

PowerShell Core 6.1 brought compatibility with many built-in Windows PowerShell modules, and our estimation is that PowerShell 7 can attain compatibility with 90+% of the inbox Windows PowerShell modules by leveraging changes in .NET Core 3.0 that bring back many APIs required by modules built on .NET Framework so that they work with .NET Core runtime. For example, we expect Out-GridViewto come back (for Windows only, though)!

A significant effort for PowerShell 7 is porting the PowerShell Core 6 code base to .NET Core 3.0 and also working with Windows partner teams to validate their modules against PowerShell 7.

Support Lifecycle Changes

Currently, PowerShell Core is under the Microsoft Modern Lifecycle Policy. This means that PowerShell Core 6 is fix-forward: we produce servicing releases for security fixes and critical bug fixes, and you must install the latest stable version within 6 months of a new minor version release.

In PowerShell 7, we will align more closely with the .NET Core support lifecycle, enabling PowerShell 7 to have both LTS (Long Term Servicing) and non-LTS releases.

We will still have monthly Preview releases to get feedback early.

When do I get PowerShell 7?

The first Preview release of PowerShell 7 will likely be in May. Be aware, however, that this depends on completing integration and validation of PowerShell with .NET Core 3.0.

Since PowerShell 7 is aligned with the .NET Core timeline, we expect the generally available (GA) release to be some time after the GA of .NET Core 3.0.

What about shipping in Windows?

We are planning on eventually shipping PowerShell 7 in Windows as a side-by-side feature with Windows PowerShell 5.1, but we still need to work out some of the details on how you will manage this inbox version of PowerShell 7.

And since the .NET Core timeline doesn’t align with the Windows timeline, we can’t say right now when it will show up in a future version of Windows 10 or Windows Server.

What other features will be in PowerShell 7?

We haven’t closed on our feature planning yet, but expect another blog post relatively soon with a roadmap of our current feature level plans for PowerShell 7.

Steve Lee
Steve Lee (@Steve_MSFT) | Twitter
Principal Engineering Manager
PowerShell Team
Click to expand...

Source: The Next Release of PowerShell - PowerShell 7 | PowerShell

Windows 10: New PowerShell 7.0.1 version has been released - May 14

New PowerShell 7.0.1 version has been released - May 14

New PowerShell 7.0.1 version has been released - May 14

New PowerShell 7.0.1 version has been released - May 14

New PowerShell 7.0.1 version has been released - May 14 - Similar Threads - PowerShell version has

Windows 10 version 21H1 has been released

PowerShell 7.2.0 preview 5 released - April 14

Has there been a fix released for the driver issues with the new 20h2 version release ?...

PowerShell 7.2.0 preview 1 released

New PowerShell 7.0.3 version has been released - July 16

New PowerShell 7.0.2 version has been released - June 11

New Powershell Core v7.0.0-rc.1 released

Totally Confused -- Has the May Feature Update Been Released?!?

The Next Release of PowerShell - PowerShell 7

Users found this page by searching for:

powershell upgrade from 7.0.0 to 7.0.1