How to Enable and Use Script Execution Policy in Windows Powershell

This practical guide explains how to enable and use script execution policy in windows powershell with clear steps and useful context. It also covers common requirements, potential problems, and the details that can help you get better results.

However, if this is your first time executing a script via PowerShell, you will get a "running script is disabled" error. By default, script execution on PowerShell is disabled as a security measure to prevent malicious scripts from running on the system. The following article will show you two ways to enable Script Execution Policy in Windows PowerShell.

How to Check the Current Enforcement Policy

You can use a PowerShell cmdlet to get your current execution policy. Knowing the current enforcement policy is necessary to know if you need to change the policy.

To get the policy to execute for the current user:

1. Open Windows PowerShell with admin rights.

2. Type the following command into the PowerShell console and press Enter :

get-executionpolicy

3. Since you encountered an error while executing the script, the returned result may show Restricted for your current execution policy.

4. If you need to see the enforcement policy for all supported scopes:

get-executionpolicy -list

You will need to change the execution policy to RemoteSigned to run the script locally without errors. You can change the execution policy from the Settings and PowerShell apps.

How to Enable Powershell Execution Policy Using the Settings App

You can change and set the PowerShell execution policy to RemoteSigned using the Settings app. All you have to do is adjust the PowerShell settings in the developer section to change the execution policy to enable PowerShell script execution.

To change the execution policy using Settings:

1. Press Win + I to open Settings.

2. Open the Privacy & Security tab in the left pane.

3. Next, click For developers .

4. Click to expand the PowerShell section.

5. Turn on the Change the execution policy to allow local PowerShell scripts to run without signing - Require signing for remote scripts switch .

6. Once done, open PowerShell, type get executionpolicy and press Enter. Execution Policy for the current user is set to RemoteSigned.

7. If you need to disable the enforcement policy, turn on the PowerShell switch and set it to Off .

How to Allow Scripts to Run in Powershell Using Powershell

You can use the PowerShell cmdlet to set the execution policy to RemoteSigned. The command-line interface makes it easy to change enforcement policies on the fly without using the Settings app.

Also, the Settings app can only enable or disable the RemoteSigned enforcement policy. While PowerShell also allows you to set other policies and scopes.

To change the execution policy using PowerShell:

1. Open PowerShell with admin rights.

2. In the PowerShell window, type the following command and press Enter :

Set-ExecutionPolicy RemoteSigned

3. If prompted, press A to confirm action. This will set the RemoteSigned enforcement policy for all users. If you only want to set the execution policy for Current User , use the Scope parameter followed by the username.

4. For example, to set the RemoteSigned execution policy for CurrentUser , use the following command:

Set-ExecutionPolicy RemoteSgined -Scope CurrentUser

5. Replace CurrentUser in the above command with another user (Scope) according to your requirements.

How to Delete Script Execution Policy with Powershell

If you want to disable script execution, set the execution policy to Undefined using the Set_ExecutionPolicy cmdlet. This is the default state and prevents PowerShell from executing any scripts.

To disable script execution using PowerShell:

1. Open PowerShell with admin rights.

2. Next, type the following command and press Enter to disable script execution for all users:

Set-ExecutionPolicy undefined

3. The above command will set the default execution policy (undefined) for all users. If you want to disable script execution for a specific range, use the following command:

Set-ExecutionPolicy undefined -Scope CurrentUser

4. The above command will disable script execution for CurrentUser .

Conclusion

Understanding Script Execution Policy makes it easier to compare options, avoid common mistakes, and apply the information in this guide more effectively. Review the relevant requirements before making changes or choosing a solution.