Monthly Archives: March 2019

PowerShell v6.2 contains a number of experimental features including PSCommandNotFoundSuggestion The idea of experimental features is to make the use of new features – especially those that may cause breaking changes optional.  Feedback can be obtainied and the experimental features … Continue reading →

I’ve mentioned the PowerShell v6.2 experimental features before. This blog post from the PowerShell team https://devblogs.microsoft.com/powershell/general-availability-of-powershell-core-6-2/ gives a good overview of the available experimental features. I’ve already covered the use of the temp drive. The command not found suggestions and … Continue reading →

The Powershell v6.2 release has just been made available on github – https://github.com/PowerShell/PowerShell/releases The full release notes aren’t available on the Microsoft documentation yet – they should appear in the What’s New section of https://docs.microsoft.com/en-us/powershell/scripting/overview?view=powershell-6 The release notes on github … Continue reading →

The issue Scope issue with Install-Module that I discussed in recent posts is annoying because I know that I’ll forget about it and end up installing in the wrong place and have to uninstall and reinstall. Then I remembered PowerShell … Continue reading →

Further to my last post it appears that Install-Module in PowerShell v6.2 RC1 DOESN’T follow the rules. In an elevated session if the scope parameter ISN’T used it will install to $home\Documents\PowerShell\Modules The default appears to be CurrentUser regardless. You … Continue reading →

Be aware of the Scope parameter when using Install-Module. The following rules apply: Allusers scope installs to $env:ProgramFiles\PowerShell\Modules CurrentUser scope installs to $home\Documents\PowerShell\Modules NoScope defined: – – For an elevated PowerShell session, Scope defaults to AllUsers – –  For non-elevated … Continue reading →