Changing the Windows PowerShell Script Execution Policy
Error – install.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see “get-help about_signing” for more details.
When you download a script off the internet and try to run it, if you have not previously configured PowerShell, it will throw a nasty error in red font. This is enough to scare most users off, but there is an easy fix.
PowerShell has a number of execution modes that define what type of code it is permitted to run, this is governed by a registry key that lives in the HKLM hive. There are 4 different execution modes, they are:
The Set-ExecutionPolicy cmdlet enables you to determine which Windows PowerShell scripts (if any) will be allowed to run on your computer. Windows PowerShell has four different execution policies:
-
Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.
-
AllSigned – Only scripts signed by a trusted publisher can be run.
-
RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.
-
Unrestricted – No restrictions; all Windows PowerShell scripts can be run.
To assign a particular policy simply call Set-ExecutionPolicy followed by the appropriate policy name. For example, this command sets the execution policy to RemoteSigned:
Set-ExecutionPolicy RemoteSigned
(Visited 2 times, 1 visits today)
