Set-ExecutionPolicy (Microsoft.PowerShell.Security) - PowerShell (2023)

Syntax

Set-ExecutionPolicy [-ExecutionPolicy] <ExecutionPolicy> [[-Scope] <ExecutionPolicyScope>] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]

Description

The Set-ExecutionPolicy cmdlet changes PowerShell execution policies for Windows computers. Formore information, see about_Execution_Policies.

Beginning in PowerShell 6.0 for non-Windows computers, the default execution policy isUnrestricted and can't be changed. The Set-ExecutionPolicy cmdlet is available, but PowerShelldisplays a console message that it's not supported.

An execution policy is part of the PowerShell security strategy. Execution policies determinewhether you can load configuration files, such as your PowerShell profile, or run scripts. And,whether scripts must be digitally signed before they are run.

The Set-ExecutionPolicy cmdlet's default scope is LocalMachine, which affects everyone whouses the computer. To change the execution policy for LocalMachine, start PowerShell with Runas Administrator.

To display the execution policies for each scope in the order of precedence, useGet-ExecutionPolicy -List. To see the effective execution policy for your PowerShell session useGet-ExecutionPolicy with no parameters.

Examples

Example 1: Set an execution policy

This example shows how to set the execution policy for the local computer.

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachineGet-ExecutionPolicy -ListScope ExecutionPolicy ----- ---------------MachinePolicy Undefined UserPolicy Undefined Process Undefined CurrentUser RemoteSigned LocalMachine RemoteSigned

The Set-ExecutionPolicy cmdlet uses the ExecutionPolicy parameter to specify theRemoteSigned policy. The Scope parameter specifies the default scope value,LocalMachine. To view the execution policy settings, use the Get-ExecutionPolicy cmdlet withthe List parameter.

Example 2: Set an execution policy that conflicts with a Group Policy

This command attempts to set the LocalMachine scope's execution policy to Restricted.LocalMachine is more restrictive, but isn't the effective policy because it conflicts with aGroup Policy. The Restricted policy is written to the registry hive HKEY_LOCAL_MACHINE.

PS> Set-ExecutionPolicy -ExecutionPolicy Restricted -Scope LocalMachineSet-ExecutionPolicy : PowerShell updated your local preference successfully, but the setting isoverridden by the Group Policy applied to your system. Due to the override, your shell will retainits current effective execution policy of "AllSigned". Contact your Group Policy administrator formore information. At line:1 char:20 + Set-ExecutionPolicy <<<< restrictedPS> Get-ChildItem -Path HKLM:\SOFTWARE\Microsoft\PowerShell\1\ShellIds Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIdsName Property---- --------Microsoft.PowerShell Path : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe ExecutionPolicy : RestrictedScriptedDiagnostics ExecutionPolicy : Unrestricted

The Set-ExecutionPolicy cmdlet uses the ExecutionPolicy parameter to specify theRestricted policy. The Scope parameter specifies the default scope value, LocalMachine.The Get-ChildItem cmdlet uses the Path parameter with the HKLM provider to specifyregistry location.

Example 3: Apply the execution policy from a remote computer to a local computer

This command gets the execution policy object from a remote computer and sets the policy on thelocal computer. Get-ExecutionPolicy sends a Microsoft.PowerShell.ExecutionPolicy object downthe pipeline. Set-ExecutionPolicy accepts pipeline input and doesn't require theExecutionPolicy parameter.

PS> Invoke-Command -ComputerName Server01 -ScriptBlock { Get-ExecutionPolicy } | Set-ExecutionPolicy

The Invoke-Command cmdlet is executed at the local computer and sends the ScriptBlock to theremote computer. The ComputerName parameter specifies the remote computer, Server01. TheScriptBlock parameter runs Get-ExecutionPolicy on the remote computer. TheGet-ExecutionPolicy object is sent down the pipeline to the Set-ExecutionPolicy.Set-ExecutionPolicy applies the execution policy to the local computer's default scope,LocalMachine.

Example 4: Set the scope for an execution policy

This example shows how to set an execution policy for a specified scope, CurrentUser. TheCurrentUser scope only affects the user who sets this scope.

Set-ExecutionPolicy -ExecutionPolicy AllSigned -Scope CurrentUserGet-ExecutionPolicy -ListScope ExecutionPolicy ----- ---------------MachinePolicy Undefined UserPolicy Undefined Process Undefined CurrentUser AllSigned LocalMachine RemoteSigned

Set-ExecutionPolicy uses the ExecutionPolicy parameter to specify the AllSigned policy.The Scope parameter specifies the CurrentUser. To view the execution policy settings, usethe Get-ExecutionPolicy cmdlet with the List parameter.

The effective execution policy for the user becomes AllSigned.

Example 5: Remove the execution policy for the current user

This example shows how use the Undefined execution policy to remove an execution policy for aspecified scope.

Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope CurrentUserGet-ExecutionPolicy -ListScope ExecutionPolicy ----- ---------------MachinePolicy Undefined UserPolicy Undefined Process Undefined CurrentUser Undefined LocalMachine RemoteSigned

Set-ExecutionPolicy uses the ExecutionPolicy parameter to specify the Undefined policy.The Scope parameter specifies the CurrentUser. To view the execution policy settings, usethe Get-ExecutionPolicy cmdlet with the List parameter.

Example 6: Set the execution policy for the current PowerShell session

The Process scope only affects the current PowerShell session. The execution policy is saved inthe environment variable $env:PSExecutionPolicyPreference and is deleted when the session isclosed.

Set-ExecutionPolicy -ExecutionPolicy AllSigned -Scope ProcessScope ExecutionPolicy ----- ---------------MachinePolicy Undefined UserPolicy Undefined Process AllSigned CurrentUser RemoteSigned LocalMachine RemoteSigned

The Set-ExecutionPolicy uses the ExecutionPolicy parameter to specify the AllSignedpolicy. The Scope parameter specifies the value Process. To view the execution policysettings, use the Get-ExecutionPolicy cmdlet with the List parameter.

Example 7: Unblock a script to run it without changing the execution policy

This example shows how the RemoteSigned execution policy prevents you from running unsignedscripts.

A best practice is to read the script's code and verify it's safe before using theUnblock-File cmdlet. The Unblock-File cmdlet unblocks scripts so they can run, but doesn'tchange the execution policy.

PS> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachinePS> Get-ExecutionPolicyRemoteSignedPS> .\Start-ActivityTracker.ps1.\Start-ActivityTracker.ps1 : File .\Start-ActivityTracker.ps1 cannot be loaded.The file .\Start-ActivityTracker.ps1 is not digitally signed.The script will not execute on the system.For more information, see about_Execution_Policies at https://go.microsoft.com/fwlink/?LinkID=135170.At line:1 char:1+ .\Start-ActivityTracker.ps1+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : NotSpecified: (:) [], PSSecurityException+ FullyQualifiedErrorId : UnauthorizedAccessPS> Unblock-File -Path .\Start-ActivityTracker.ps1PS> Get-ExecutionPolicyRemoteSignedPS> .\Start-ActivityTracker.ps1Task 1:

The Set-ExecutionPolicy uses the ExecutionPolicy parameter to specify the RemoteSignedpolicy. The policy is set for the default scope, LocalMachine.

The Get-ExecutionPolicy cmdlet shows that RemoteSigned is the effective execution policy forthe current PowerShell session.

The Start-ActivityTracker.ps1 script is executed from the current directory. The script isblocked by RemoteSigned because the script isn't digitally signed.

For this example, the script's code was reviewed and verified as safe to run. The Unblock-Filecmdlet uses the Path parameter to unblock the script.

To verify that Unblock-File didn't change the execution policy, Get-ExecutionPolicy displays theeffective execution policy, RemoteSigned.

The script, Start-ActivityTracker.ps1 is executed from the current directory. The script beginsto run because it was unblocked by the Unblock-File cmdlet.

Parameters

-Confirm

-ExecutionPolicy

-Force

-Scope

-WhatIf

Inputs

ExecutionPolicy

You can pipe an execution policy object to this cmdlet.

String

You can pipe a string that contains the name of an execution policy to this cmdlet.

Outputs

None

This cmdlet returns no output.

Notes

Set-ExecutionPolicy doesn't change the MachinePolicy and UserPolicy scopes because theyare set by Group Policies.

Set-ExecutionPolicy doesn't override a Group Policy, even if the user preference is morerestrictive than the policy.

If the Group Policy Turn on Script Execution is enabled for the computer or user, the userpreference is saved, but it is not effective. PowerShell displays a message that explains theconflict.

• about_Execution_Policies
• about_Group_Policy_Settings
• about_Providers
• Get-AuthenticodeSignature
• Get-ChildItem
• Get-ExecutionPolicy
• Invoke-Command
• Set-AuthenticodeSignature
• Unblock-File