The Set-ExecutionPolicy cmdlet changes the user preference for the Windows PowerShell execution policy. The execution policy is part of the security strategy of Windows PowerShell. It determines whether you can load configuration files (including your Windows PowerShell profile) and run scripts, and it determines which scripts, if any, must be digitally signed before they will run. For more information, see about_Execution_Policies (http://go.microsoft.com/fwlink/?LinkID=135170).
To change the execution policy for the default (LocalMachine) scope, start Windows PowerShell with the “Run as administrator” option.
-Confirm [<SwitchParameter>]
- Default value is FalseAccepts pipeline input False
Prompts you for confirmation before running the cmdlet.
-ExecutionPolicy <ExecutionPolicy>
- This value is required
- Default value is None
Accepts pipeline input ByValue
Specifies the new execution policy. The acceptable values for this parameter are:
– Restricted. Does not load configuration files or run scripts. Restricted is the default execution policy. – AllSigned. Requires that all scripts and configuration files be signed by a trusted publisher, including scripts that you write on the local computer. – RemoteSigned. Requires that all scripts and configuration files downloaded from the Internet be signed by a trusted publisher. – Unrestricted. Loads all configuration files and runs all scripts. If you run an unsigned script that was downloaded from the Internet, you are prompted for permission before it runs. – Bypass. Nothing is blocked and there are no warnings or prompts. – Undefined. Removes the currently assigned execution policy from the current scope. This parameter will not remove an execution policy that is set in a Group Policy scope.
-Force [<SwitchParameter>]
- Default value is False
- Accepts pipeline input False
Suppresses all prompts. By default, Set-ExecutionPolicy displays a warning whenever you change the execution policy.
-Scope <ExecutionPolicyScope>
- Default value is None
- Accepts pipeline input ByPropertyName
Specifies the scope of the execution policy. The default is LocalMachine. The acceptable values for this parameter are:
– Process: The execution policy affects only the current Windows PowerShell process.
– CurrentUser: The execution policy affects only the current user.
– LocalMachine: The execution policy affects all users of the computer.
To remove an execution policy from a particular scope, set the execution policy for that scope to Undefined.When the value of the Scope parameter is Process, the execution policy is saved in the PSExecutionPolicyPreference environment variable ($env:PSExecutionPolicyPreference), instead of the registry, and the variable is deleted when the process is closed. You cannot change the execution policy of the process by editing the variable.
-WhatIf [<SwitchParameter>]
- Default value is False
- Accepts pipeline input False
Shows what would happen if the cmdlet runs. The cmdlet is not run.
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,ErrorAction, ErrorVariable, WarningAction, WarningVariable,OutBuffer, PipelineVariable, and OutVariable.
Inputs
Microsoft.PowerShell.ExecutionPolicy, System.String
Outputs
None
Examples
Set the shell execution policy:
This command sets the user preference for the shell execution policy to RemoteSigned.
- Set a shell execution policy that conflicts with the group policy:
This command attempts to set the execution policy for the shell to Restricted. The Restricted setting is written to the registry, but because it conflicts with a group policy, it is not effective, even though it is more restrictive than the group policy.
- Apply the execution policy from a remote computer to the local computer:
This command gets the execution policy from a remote computer and applies that execution policy to the local computer.
The command uses the Invoke-Command cmdlet to send the command to the remote computer. Because you can pipe an ExecutionPolicy (Microsoft.PowerShell.ExecutionPolicy) object to Set-ExecutionPolicy , the Set-ExecutionPolicy command does not require an ExecutionPolicy parameter.
The command uses the Force parameter to suppress the user prompt.
- Set the scope for an execution policy:
The second command uses the *List* parameter of the Get-ExecutionPolicy cmdlet to get the execution policies set in each scope. The results show that the execution policy that is set for the current user differs from the execution policy set for all users of the computer.This example shows how to set an execution policy for a particular scope.
The first command uses the Set-ExecutionPolicy cmdlet to set an execution policy of AllSigned for the current user. It uses the Force parameter to suppress the user prompt.
- Remove the execution policy for the current user:
This command uses an execution policy value of Undefined to effectively remove the execution policy that is set for the current user scope. As a result, the execution policy that is set in Group Policy or in the LocalMachine (all users) scope is effective.
If you set the execution policy in all scopes to Undefined and the Group Policy is not set, the default execution policy, Restricted, is effective for all users of the computer.
- Set the execution policy for the current session:
This command sets an execution policy of AllSigned for only the current Windows PowerShell session. This execution policy is saved in the PSExecutionPolicyPreference environment variable ($env:PSExecutionPolicyPreference), so it does not affect the value in the registry. The variable and its value are deleted when the current session is closed.
- Unblock a script to run it without changing the execution policy:
i.The first command uses the **Set-ExecutionPolicy** cmdlet to change the execution policy to RemoteSigned.
The first command uses the **Set-ExecutionPolicy** cmdlet to change the execution policy to RemoteSigned.
ii.The second command uses the Get-ExecutionPolicy cmdlet to get the effective execution policy in the session:
The output shows that it is RemoteSigned.
iii.The third command shows what happens when you run a blocked script in a Windows PowerShell session in which the execution policy is RemoteSigned:
The RemoteSigned policy prevents you from running scripts that are downloaded from the Internet unless they are digitally signed.
iv.The fourth command uses the Unblock-File cmdlet to unblock the script so it can run in the session.Before running an **Unblock-File** command, read the script contents and verify that it is safe:
v.The fifth and sixth commands show the effect of the **Unblock-File** command:
The **Unblock-File** command does not change the execution policy. However, it unblocks the script so it will run in Windows PowerShell.This example shows the effect of the RemoteSigned execution policy, which prevents you from running unsigned scripts that were downloaded from the Internet. It also shows how to use the Unblock-File cmdlet to unblock scripts, so that you can run them without changing the execution policy.
Expert Instructors
Practical Training
Industry-Relevant Curriculum
Cutting-Edge Tools
Collaborative Learning
Portfolio Development
Limited seats available! Visit JeeviAcademy or call +91 9994051212 to enroll. Start your journey towards a successful career in UI & UX design now!
