powershell-2.0

Solution was to run PowerShell as an administrator. Stop-Service worked ok after doing that.

In fact, if you call a .ps1 file, by default any functions and variables declared within it are scoped privately within the script (this is referred to as “script scope”). Since you’re seeing both functions defined globally, I infer that you’re dot-sourcing SvcTest.ps1, i.e. invoking it like this PS> . <path>\SvcTest.ps1 rather than calling it … Read more

I like Keith Hill’s answer except it has a bug that prevents it from recursing past two levels. These commands manifest the bug: New-Item level1/level2/level3/level4/foobar.txt -Force -ItemType file cd level1 GetFiles . xyz | % { $_.fullname } With Hill’s original code you get this: …\level1\level2 …\level1\level2\level3 Here is a corrected, and slightly refactored, version: … Read more

AllowEncrypted is defined on the client end, via the WSMAN: drive. You must be running powershell.exe (or powershell_ise.exe) as an elevated process. ps> cd WSMan:\localhost\Client ps> dir Name Value —- —– NetworkDelayms 5000 URLPrefix wsman AllowUnencrypted false Auth DefaultPorts TrustedHosts You would change it like so (after changing to the directory above): Set-Item .\allowunencrypted $true … Read more

Casting the character array to System.String actually seems to join the array elements with spaces, meaning that [string][System.IO.Path]::GetInvalidFileNameChars() does the same as [System.IO.Path]::GetInvalidFileNameChars() -join ‘ ‘ when you actually want [System.IO.Path]::GetInvalidFileNameChars() -join ” As @mjolinor mentioned (+1), this is caused by the output field separator ($OFS). Evidence: PS C:\> [RegEx]::Escape([string][IO.Path]::GetInvalidFileNameChars()) “\ \ \|\ \ ☺\ … Read more

ls variable:* should work, or Get-Variable. If these are resulting in bad output, it’s due to a poorly-implemented host, not with powershell itself. If you open the standard console host (run powershell.exe), you will see that these work fine. If you need to work around a bad host, you might have better luck dumping everything … Read more

Using throw will change the job object’s State property to “Failed”. The key is to use the job object returned from Start-Job or Get-Job and check the State property. You can then access the exception message from the job object itself. Per your request I updated the example to also include concurrency. $createZip = { … Read more

In PowerShell 5.0+, you would use: “TestTest” | Out-File -encoding ascii test.txt -NoNewline But in earlier versions you simply can’t with that cmdlet. Try this: [System.IO.File]::WriteAllText($FilePath,”TestTest”,[System.Text.Encoding]::ASCII)