Should I set the execution policy to Unrestricted or Bypass?

Not to fix this error. Unrestricted lets unsigned scripts run, with a risk of running malicious scripts. Bypass blocks nothing and shows no warnings; it is designed for scripts built into a larger application with its own security model.

Is the execution policy a security boundary?

No. Microsoft calls it defense in depth, because users can bypass it by typing the script contents at the command line. It sets basic rules so you don't break them by accident.

Why didn't my change take effect?

A scope with higher precedence can override it: Process beats CurrentUser, which beats LocalMachine. A Group Policy setting beats all of them. Run Get-ExecutionPolicy -List to see every scope.

Do I need to restart PowerShell after changing the policy?

No. The change is effective immediately. A policy set for the Process scope is lost when you close that session.

Fix "running scripts is disabled on this system" in PowerShell

File C:\Desktop\myscript.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.

PowerShell shows "running scripts is disabled on this system" when the execution policy is Restricted⁵. Restricted allows single commands but no scripts¹. Run Get-ExecutionPolicy -List to see the policy in each scope³. Then set RemoteSigned for the current session or for your own account with Set-ExecutionPolicy¹. Unblock a downloaded script with Unblock-File only after you check it is safe⁴.

What the error means

PowerShell's execution policy controls when it loads configuration files and runs scripts¹. Under the Restricted policy, PowerShell runs single commands but no script files. That includes .ps1 profiles and .psm1 module files¹.

Microsoft ties this message to the Restricted policy⁵. In Windows PowerShell 5.1, Restricted is the default on Windows client computers¹. The policy is not a security boundary. It is a safety feature that stops you from running scripts by accident¹.

Before you start

The fixes below change only the Process and CurrentUser scopes. Only the LocalMachine scope needs PowerShell started with Run as administrator².
On a work PC, Group Policy may set the policy. That setting overrides all scopes, and Set-ExecutionPolicy can't change it^1,2.
Windows PowerShell 5.1 (powershell.exe) and PowerShell 6 or later (pwsh.exe) keep separate settings. Run the fix in the shell that shows the error².
Execution policies apply only on Windows. On Linux and macOS, the policy is Unrestricted and can't be changed².

Fixes

Check the current policy. Open PowerShell and run this command. It lists the policy for each scope in order of precedence³.
PowerShell
```
Get-ExecutionPolicy -List
```
The MachinePolicy and UserPolicy rows come from Group Policy¹. If either one shows a value other than Undefined, the fixes below can't override it².
Allow scripts for this session only. Set RemoteSigned for the Process scope. It affects only the current PowerShell session, and the setting is deleted when you close it².
PowerShell
```
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process
```
Run your script in the same window. The policy lasts until that window and its child processes close¹.
Allow local scripts for your account. Set RemoteSigned for the CurrentUser scope. This is the command Microsoft's docs use¹.
PowerShell
```
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
```
RemoteSigned runs scripts written on your computer. Scripts downloaded from the internet, including email and instant messaging, still need a signature from a trusted publisher¹. The change is saved and takes effect at once, with no restart¹.
Unblock a downloaded script you trust. Under RemoteSigned, an unsigned script from the internet still fails. The error then says the file "is not digitally signed. The script will not execute on the system."² Read the script's code and check its source first⁴. Then unblock it, using your own file path:
PowerShell
```
Unblock-File -Path .\Start-ActivityTracker.ps1
```
Unblock-File removes the Zone.Identifier stream that marks the file as downloaded⁴. It doesn't change the execution policy².

If nothing works

If MachinePolicy or UserPolicy is set, the policy comes from the Turn on Script Execution Group Policy setting¹. It overrides PowerShell's own settings in all scopes¹. Ask your Group Policy administrator to change it².

Don't switch to Unrestricted or Bypass to make the error go away. Unrestricted lets unsigned scripts run, with a risk of running malicious scripts¹. Bypass blocks nothing and gives no warnings or prompts¹.

To undo the change for your account later, set the scope back to Undefined¹:

PowerShell

Set-ExecutionPolicy -ExecutionPolicy Undefined -Scope CurrentUser

Questions

Should I set the execution policy to Unrestricted or Bypass?: Not to fix this error. Unrestricted lets unsigned scripts run, with a risk of running malicious scripts¹. Bypass blocks nothing and shows no warnings; it is designed for scripts built into a larger application with its own security model¹.
Is the execution policy a security boundary?: No. Microsoft calls it defense in depth, because users can bypass it by typing the script contents at the command line¹. It sets basic rules so you don't break them by accident¹.
Why didn't my change take effect?: A scope with higher precedence can override it: Process beats CurrentUser, which beats LocalMachine¹. A Group Policy setting beats all of them¹. Run Get-ExecutionPolicy -List to see every scope³.
Do I need to restart PowerShell after changing the policy?: No. The change is effective immediately¹. A policy set for the Process scope is lost when you close that session¹.

4 Oct 2026: Published.