Windows 10 Running Scripts Is Disabled on This System: Allowing PowerShell Scripts Safely
You try to run a PowerShell script, activate a Python virtual environment, or follow a setup guide, and PowerShell answers in red: “File cannot be loaded because running scripts is disabled on this system.” When Windows 10 running scripts is disabled on this system blocks your PAGODA127 RESMI command, PowerShell’s execution policy is stopping script files from running.
The execution policy is a safety setting that decides whether PowerShell can run .ps1 script files. On Windows 10 client PCs, the default is Restricted, which allows typed commands but blocks all script files. That protects beginners from running harmful scripts by accident.
Developers and power users often need scripts, such as the Activate.ps1 file in Python virtual environments or setup scripts for tools.
You can allow them for your own account without weakening security for the whole PC.
The error often appears when following programming tutorials, setting up Python virtual environments, or installing tools such as Node.js package scripts that rely on PowerShell.
Why This Happens
Scripts are blocked for these reasons:
- The execution policy is Restricted, the default on Windows 10.
- The script was downloaded and is marked as coming from the internet.
- A Group Policy enforces a strict execution policy.
- The script is not signed under an AllSigned policy.
Running a single command typed directly into PowerShell is not affected by the policy; only script files are.
Windows PowerShell and the newer PowerShell 7 keep separate policies on some systems, so a script may run in one and fail in the other. Check which one you are using in the window’s title bar.
Start With These Basic Checks
Check the current policy.
- Open PowerShell normally, not as administrator.
- Type Get-ExecutionPolicy -List and press Enter.
- Note the values for CurrentUser and LocalMachine.
- If MachinePolicy or UserPolicy shows a value, a Group Policy controls it.
- Decide whether you need scripts for your account only.
If you only need a virtual environment, you can also activate it from Command Prompt with activate.bat instead of Activate.ps1, which avoids the PowerShell policy completely.
Going a Step Further
Allow scripts for your account.
- In PowerShell, type Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned and press Enter.
- Type Y to confirm.
- Run your script again.
- If the script came from the internet and is still blocked, right-click it, choose Properties, and tick Unblock, after confirming it is trustworthy.
- For one-off use, run powershell -ExecutionPolicy Bypass -File script.ps1 instead of changing the policy.
RemoteSigned allows local scripts but requires downloaded scripts to be signed or unblocked, which is a sensible balance.
A Word of Caution
Never set the policy to Unrestricted or Bypass permanently for the whole machine. Read any downloaded script before running it, and on work PCs ask IT before changing policies.
Final Thoughts
This error appears because PowerShell’s execution policy blocks script files. Set RemoteSigned for your user account, unblock trusted downloaded scripts, and use Bypass only for single trusted runs.