Good evening

Since years(!), it's well known that if we map SMB Shares using the New-SmbMapping command,
then the Windows Explorer does not recognize the new Drives: we have to kill and restart explorer.exe.
Well, we can be happy that we do not have to reboot...

We can not believe that this bug was never fixed and that we have to raise our user voice to solicitation so that such annoying bugs get finally fixed.

Of course, we could use the New-PSDrive command.
Unfortunately, this command is even worse: it does not validate if the credentials are valid nor if the SMB UNC Path is valid. This will lead to 'mapped' Drive letters which are not accessible at all. Therefore, Users have to deconnect the invalid drive - and to reconnect it again. Manually.
You probably remember: 20 years ago, Windows detected such problems during the onconnect event and asked the user for the missing / wrong information. Automatically.

Of course, we could use "net use". Of course, we could us batch files, too.
But for sure, it would be much more useful if powershell commands just works as expected.
The 1st time right.

I'm pretty sure it's not presumptuous if Microsoft starts spending some of the billions profit to write again software which accomplish the basics as expected.

Maybe you could start anf fixing this uservoice-form so that this textbox will display more than 4x100 characters. You know: some useful thing.

Kind regards,
Thomas

Setting $ErrorActionPreference to Stop is ignored by New-SmbShare (and possibly other CIM wrapped functions) in specific use cases:

• Run within Windows ISE: No problem


• Invoked using powershell.exe -File argument: No problem


• Called with explicit -ErrorAction Stop: No problem


• Run within PowerShell Prompt (dot-sourced): $ErrorActionPreference is ignored


• Invoked using powershell.exe -Command argument: $ErrorActionPreference is ignored

This can be tested with the following script (test.ps1):

$ErrorActionPreference = "Stop"
New-SmbShare -Name "Test" -Path "C:\NonExistingPath"
Write-Host "Should not be reached"

The following call shows the error "The system cannot find the file specified", but also shows "Should never be reached", which is incorrect:
powershell.exe -Command .\test.ps1

The following call just throws the "The system cannot find the file specified", which is correct:
powershell.exe -File .\test.ps1

Requirements:
- PowerShell 4 or higher
- Windows Server 2012 R2, Windows 8.1 or higher