Windows 10: Powershell 7.1 preview 2 is released

Brink · May 11, 2020

Powershwll version 7.1 preview 2 has been released.

Changes from preview 1.

Breaking Changes

On Windows, Start-Process creates a process environment with
all the environment variables from current session,
using -UseNewEnvironment creates a new default process environment (#10830) (Thanks @iSazonov!)

Do not wrap return result to PSObject when converting ScriptBlock to delegate (#10619)

Engine Updates and Fixes

Allow case insensitive paths for determining PSModulePath (#12192)

Add PowerShell version 7.0 to compatible version list (#12184)

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

General Cmdlet Updates and Fixes

Fix WinCompat module loading to treat PowerShell 7 modules with higher priority (#12269)

Implement ForEach-Object -Parallel runspace reuse (#12122)

Fix Get-Service to not modify collection while enumerating it (#11851) (Thanks @NextTurn!)

Clean up the IPC named pipe on PowerShell exit (#12187)

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

Allow shorter signed hex literals with appropriate type suffixes (#11844) (Thanks @vexx32!)

Update UseNewEnvironment parameter behavior of Start-Process cmdlet on Windows (#10830) (Thanks @iSazonov!)

Add -Shuffle switch to Get-Random command (#11093) (Thanks @eugenesmlv!)

Make GetWindowsPowerShellModulePath compatible with multiple PS installations (#12280)

Fix Start-Job to work on systems that don't have Windows PowerShell registered as default shell (#12296)

Specifying an alias and -Syntax to Get-Command returns the aliased commands syntax (#10784) (Thanks @ChrisLGardner!)

Make CSV cmdlets work when using -AsNeeded and there is an incomplete row (#12281) (Thanks @iSazonov!)

In local invocations, do not require -PowerShellVersion 5.1 for Get-FormatData in order to see all format data. (#11270) (Thanks @mklement0!)

Added Support For Big Endian UTF-32 (#11947) (Thanks @NoMoreFood!)

Fix possible race that leaks PowerShell object dispose in ForEach-Object -Parallel (#12227)

Add -FromUnixTime to Get-Date to allow Unix time input (#12179) (Thanks @jackdcasey!)

Change default progress foreground and background colors to provide improved contrast (#11455) (Thanks @rkeithhill!)

Fix foreach -parallel when current drive is not available (#12197)

Do not wrap return result to PSObject when converting ScriptBlock to delegate (#10619)

Don't write DNS resolution errors on Test-Connection -Quiet (#12204) (Thanks @vexx32!)

Use dedicated threads to read the redirected output and error streams from the child process for out-of-proc jobs (#11713)

Code Cleanup
Click to expand...

Available from https://github.com/PowerShell/PowerS....1.0-preview.2

:)

Brink · May 11, 2020

Microsoft releases Secret Management Preview 2 module for PowerShell

We are excited to release a second preview of the Secret Management Module. Thanks to the tremendous feedback we received from the first preview release of this module, you will notice a number of breaking changes to the module. This release is still a preview release meaning that it is not feature complete, future releases will face breaking changes, and we are still iterating based on your feedback. It is important to also note that this version of the module is still Windows only as we are currently implementing Linux support which we hope to make available in the next preview release (and MacOS support after). Please note that because of the breaking changes this release requires a complete replacement of the Secret Management module and any extension modules. Additionally, any existing built in local vault secret can no longer be retrieved and must be re-saved.

How to Install Secret Management Preview 2

If you did not install our first preview release, open any PowerShell console and run:

Install-Module Microsoft.PowerShell.SecretManagement -AllowPrerelease

If you installed our first preview release you will want to first remove any secrets from the LocalDefaultVault. Based on feedback we changed the naming convention for secrets stored in CredMan, therefore previous secrets stored in the local vault will no longer be visible after the new version of the module is installed. (Although the user can still view/remove the old secrets via CredMan UI.) Next you will want to run Uninstall-Module Microsoft.PowerShell.SecretsManagement, this extra step is a result of the change we made to the name of the module. Finally you can run the above command Install-Module Microsoft.PowerShell.SecretManagement -AllowPrerelease to install the latest preview release of the module.

Changes in Secret Management Preview 2

New Module Name

We have removed the plurality in the module name to Mirosoft.PowerShell.SecretManagement in order to be consistent with the cmdlet name and to align with PowerShell naming conventions.

New Cmdlet Names

In addition to renaming the module, we have also removed plurality in the cmdlets. The available cmdlets in the module are now:

Code:

# Registering extension vaults
Register-SecretVault
Get-SecretVault
Unregister-SecretVault
Test-Vault # new cmdlet in this release

# Accessing secrets
Set-Secret # this cmdlet replaces Add-Secret
Get-Secret
Get-SecretInfo
Remove-Secret
Click to expand...

You will notice we renamed the Add-Secret cmdlet to be Set-Secret. This change was based on user feedback that this name better conveyed the intention of the cmldet.

You will also notice that we have added a Test-Vault cmdlet, this change allows vault extension owners to check that the vault is properly configured at registration time.

Other Changes

Set-Secret now has a default parameter set that takes SecureString secret input type. This way Set-Secret will always prompt safely for a SecureString. String secret types can still be passed via parameter or pipeline, but default will be SecureString.

Code:

PS> Set-Secret -Name MyStringToken
cmdlet Set-Secret at command pipeline position 1 Supply values for the following parameters:
SecureStringSecret: **********

# Set string secret directly
Set-Secret -Name MyStringToken -Secret $token
Set-Secret -Name MyStringToken -Secret 'MyToken'
# Set string secret via pipeline
$token | Set-Secret -Name MyStringToken -NoClobber
Click to expand...

Added SecretInformation class used to return information from Get-SecretInfo in a uniform way.

Changed CredMan naming prefix to ps:SecretName.

Added vaultName to all vault extension functions.

Fixed additionalParameters parameter in SecretManagementExtension abstract classes.

Fixed return byte[] bug in example test script extension.

In coordination with these changes we have also updated our tests and example scripts.

Next Steps

As we move towards a GA release later this year, we are using a GitHub Milestone to track issues we plan to fix. The two major work items that we are currently working toward are:

Linux Support (via keyring)

MacOS Support (via keychain)

Support and Feedback

For support on the module, feedback, or reporting a bug, please open an issue in the PowerShell/modules repo with “(Secrets Management)” specified in the issue title.
Sydney Smith, PowerShell Team
Click to expand...

Source: https://devblogs.microsoft.com/power...iew-2-release/

Brink · May 11, 2020

PowerShell 7 Preview 6 now available

Today we shipped PowerShell 7 Preview.6! This release contains a number of new features and many bug fixes from both the community as well as the PowerShell team. See the Release Notes for all the details of what is included in this release.

This will be the last preview release as we head towards a Release Candidate in December. For the Release Candidate, there will be no more new features although small changes to cmdlets may still be accepted depending on risk of the change. Bug fixes will still be accepted but also accessed for their risk of causing a regression. Finally, we expect General Availability of PowerShell 7 in January as our first Long Term Servicing release.

New Features in Preview 6

This release has a number of new features from both the community as well as the PowerShell team. Remember that preview releases of PowerShell are installed side-by-side with stable versions so you can use both and provide us feedback on previews for bugs and also on experimental features.

You can read about new features in previous preview releases:

PowerShell 7 Preview 5

PowerShell 7 Preview 4

PowerShell 7 Preview 3

There were new features in Preview 1 and Preview 2, but I didn’t blog about them… sorry!

Skip Error Check for Web Cmdlets

Great addition by community member Vincent Damewood to allow skipping the internal HTTP response error check within the web cmdlets. This means that you can now handle the web error yourself including getting the response object as well as the HTTP response headers whereas previously you would have to get it from the resulting error object.

Null Conditional Member Property and Method Access

This is a new language feature that allows you to skip checking if a variable is $null before indexing into the variable, calling a method, or accessing a property. For properties, PowerShell will already allow accesing properties of $null, but this new syntax makes it more clear the intent in the script. Note that because PowerShell allows variable names to end with a question mark, you must use braces around the variable name

Extended Unix Filesystem Information

For users of PowerShell on Linux and macOS, they may miss some of the additional information of the filesystem provided by ls -l (long form of a directory listing). This new feature makes that information available using Get-ChildItem so you are no longer missing any useful information.

Windows PowerShell Compatibility in Preview 6

This release also improves the compatibility of PowerShell 7 with Windows PowerShell 5.1. We’ve brought back many existing cmdlets from Windows PowerShell 5.1 thanks to .NET Core 3! In addition, we have a new feature included with PowerShell 7 that encapsulates the Windows Compatibility Module (more on that below!).

Clipboard Cmdlets

Get-Clipboard and Set-Clipboard are back! Not only are they available again, but they are cross platform compatible which means you can use them on Linux (requires xclip to be installed) and macOS. Note that only text is supported at this time even on Windows.

Performance Counter Cmdlets

Get-Counter is back allowing you to get Windows performance counter information. Note that Import-Counter and Export-Counter cmdlets are not supported in PowerShell 7.

Graphical Tools Cmdlets

With .NET Core 3.0 bringing back WPF support on Windows, we’ve been able to bring back some popular graphical tools. Out-GridView gives a dynamic table view of results in a pipeline with sorting and filtering capabilities and when used with -PassThru can be used interactively within a pipeline to select objects to send back to the pipeline. Show-Command gives a graphical view of a command including parameter sets, parameters, switches, etc… Finally, Get-Help -ShowWindow works again to give a graphical view of PowerShell help content.

Update-List, Out-Printer, and Clear-RecycleBin cmdlets

Update-List allows adding/removing items from a property value that contains a collection of objects within a pipeline. This cmdlet is cross-platform compatible.

Out-Printer sends a PowerShell object to the printer. This cmdlet is only supported on Windows currently.

Clear-RecycleBin empties the recycle bin and is currently only supported on Windows.

Test-Connection Improvements

The original implementation of Test-Connection in Windows PowerShell relied on WMI which made it not cross-platform compatible.

Community member and PowerShell repo maintainer Ilya Sazonov ported the cmdlet to work against .NET Core APIs in PowerShell Core 6 making it work cross-platform. However, this also changed the user experience.

For PowerShell 7, Joel Sallow, another community member made improvements to this cmdlet and also getting back to similar experience as the original cmdlet in Windows PowerShell.

Import Windows PowerShell Modules in PS7

For PowerShell Core 6, we introduced the Windows Compatibility Module to allow importing Windows PowerShell modules that were not compatible with PowerShell Core 6 leveraging WinRM and implicit remoting.

In PowerShell 7, we have included this functionality into Import-Module directly without relying on WinRM, but does rely on Windows PowerShell 5.1 (it won’t work if Windows PowerShell 5.1 is not available).

Basically, for modules in the System32 folder, if the module manifest doesn’t indicate that module is compatible with Core then that module will be loaded in a Windows PowerShell process and using implicit remoting reflected into your PowerShell 7 session.

More details of this feature along with other information regarding Windows PowerShell compatibility in general coming in a separate blog post.

Closing

These are the last of the big changes coming in PowerShell 7 as we heads toward a Release Candidate next month. Please try out this preview and report issues in our GitHub repo as we still have opportunity to fix existing bugs as well as new bugs introduced by these features.

Thanks!
Steve Lee
PowerShell Team
Click to expand...

Source: https://devblogs.microsoft.com/power...l-7-preview-6/

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Brink · May 11, 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

Windows 10: Powershell 7.1 preview 2 is released

Powershell 7.1 preview 2 is released

Powershell 7.1 preview 2 is released

Powershell 7.1 preview 2 is released

Powershell 7.1 preview 2 is released - Similar Threads - Powershell preview released

PowerShell 7.2.0 preview 2 released

PowerShell 7.2.0 preview 1 released

PowerShell 7.1.0 preview 7 released

PowerShell 7.1.0 preview 6 released

PowerShell 7.1.0 preview 5 is released

Powershell 7.1 preview 5 is released

Powershell 7.1 preview 4 is released

Microsoft releases Secret Management Preview 2 module for PowerShell

The Next Release of PowerShell - PowerShell 7