Well, I definitely got my hands wet with running Windows PowerShell scripts today. I ran into a number of issues in the process, so I better make note of the solutions for next time around.
First off, PowerShell is Windows’ task automation framework. Good for running scripts on windows machines. As far as I can tell, you can run PowerShell in the command prompt with the command call PowerShell.exe:
C:\Scripts>PowerShell.exe. Or, you can open the Start Menu and start typing PowerShell and open Windows PowerShell.
Now, you have a script and want to run it right? Pretty easy right? Not for me. I had to jump through some serious hoops here… so I tried typing Suspend.ps1. No dice. I’d get an error saying the command isn’t recognized. Through some bing magic I found that you need to include the complete file path:
Or, if you are currently in the specified folder you can use the .\ notation:
It’s better to use the full notation, to prevent it from finding a file of the same name in your current Windows path (it looks through the entire path, not just your current directory). FYI – you can see your current path with this command:
$a = $env:path; $a.Split(";")
Anyways, once I figured out how to actually make the call from the command prompt, I kept getting this weird signing error:
File C:\Scripts\Suspend.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-
help about_signing" for more details.
At line:1 char:19
+ C:\Scripts\Suspend.ps1 <<<<
This is where it got tricky. I searched around for a bit and found that by default, windows machines are set to restrict you from running scripts. To see your execution policy try using the command
Get-ExecutionPolicy. If you’ve never messed with this before, it’ll probably say Restricted, like mine did. Now, the simple fix to change this is to use the following command call:
Set-ExecutionPolicy RemoteSigned. If this works for you, congratulations! You’re good to good. For me… it didn’t. I got some weird error that looked like the following:
Set-ExecutionPolicy : Access to the registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell’ is denied.
At line:1 char:20
+ Set-ExecutionPolicy <<<< RemoteSigned
Is this familiar to you? Hopefully not, but it if is. There’s a solution.
To fix this and add the RemoteSigned execution policy by hand you’ll need to work a little Windows registry magic.
Now, you should be all set. Go back to the command prompt or PowerShell window and run your command. This time when I ran
C:\Scripts\Suspend.ps1 it was beautiful.
If you have any other issues send me an email or leave a comment, I may have struggled with it too.
Useful pages for troubleshooting: