How to Fix Running Scripts is Disabled on This System in PowerShell

If you’re trying to run PowerShell scripts on Windows 10 and encounter the error message “Running scripts is disabled on this system,” you’re not alone. This restriction is a security feature designed to prevent malicious scripts from executing without your knowledge. However, there are legitimate reasons to enable script execution, such as automating tasks, running custom scripts, or managing your system more effectively. This guide will walk you through the steps to safely enable PowerShell script execution on your Windows 10 machine, ensuring you can run your scripts without compromising security.

What You’ll Need

• Administrative access to your Windows 10 computer
• PowerShell installed (default on Windows 10)
• Basic familiarity with command-line interfaces

Step-by-Step

1. Open PowerShell with Administrator privileges:
   • Click on the Start menu, type “PowerShell” in the search bar.
   • Right-click on “Windows PowerShell” and select “Run as administrator.”
2. Check the current execution policy:

   Get-ExecutionPolicy

   This command displays the current setting, which is likely set to “Restricted” if scripts are disabled.

3. Change the execution policy to allow scripts:

   Set-ExecutionPolicy RemoteSigned

   – This setting allows scripts downloaded from the internet to run if they are signed by a trusted publisher.
   – Alternatively, you can use “Unrestricted” to allow all scripts, but this is less secure.
   – When prompted, type “Y” and press Enter to confirm.

4. Verify the change:

   Get-ExecutionPolicy

   Confirm that the new policy is set to your chosen level.

5. Test running a script:
   • Create a simple script file, e.g., “test.ps1” with the content:

     Write-Output "Hello, PowerShell!"

   • Run the script by typing:

     .	est.ps1

6. If you want to revert the setting back for security reasons, run:

   Set-ExecutionPolicy Restricted

   and confirm when prompted.

Common Mistakes

• Trying to run scripts without opening PowerShell as an administrator—this can prevent changing execution policies.
• Setting an overly permissive execution policy like “Unrestricted” without understanding the security implications.
• Not confirming the change when prompted, which leaves the policy unchanged.
• Editing the execution policy in the wrong scope (e.g., User vs. Machine). Always specify the scope if needed.
• Attempting to run scripts from a location blocked by Windows security policies, such as network shares or downloaded files.

Tips

• Always run PowerShell as an administrator when changing execution policies to ensure you have the necessary permissions.
• Use the “RemoteSigned” policy for a balance between security and functionality.
• Be cautious when setting the execution policy to “Unrestricted” or “Bypass,” as this can expose your system to malicious scripts.
• Only run scripts from trusted sources to avoid security risks.
• After completing your tasks, consider reverting to the default “Restricted” setting for safety.

Troubleshooting

If the script still doesn’t run after following the steps above, try the following:

• Ensure you’re running PowerShell with administrator privileges. Without admin rights, changes to execution policy may not apply.
• Check for Group Policy restrictions:
  • Press Win + R, type gpedit.msc, and press Enter.
  • Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell.
  • Look for the setting Turn on Script Execution. If it’s enabled and set to “Disallowed,” you’ll need to change it or contact your system administrator.
• Verify that your script isn’t blocked by Windows Defender or other security software. Temporarily disable security tools if necessary, but only if you trust the script source.
• Check the script for errors or syntax issues that might prevent execution.
• Restart your computer after making changes to ensure policies are applied correctly.

If these steps still don’t resolve the issue, seek assistance from your system administrator or consult official Microsoft support resources.

Frequently Asked Questions

1. Is it safe to change the PowerShell execution policy?

It depends on the policy you choose. “RemoteSigned” is generally safe for most users, but setting it to “Unrestricted” can expose your system to malicious scripts. Always understand the implications and only run scripts from trusted sources.

2. Can I set different policies for different users?

Yes. PowerShell allows setting execution policies at the user level or for specific scopes using the -Scope parameter, such as Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned.

3. What do I do if I get a policy error even after changing the setting?

Check for Group Policy restrictions, as enterprise or organizational computers may enforce policies that override local settings. In such cases, contact your system administrator.

4. How do I run scripts that are digitally signed?

If your scripts are signed by a trusted publisher, setting the execution policy to “AllSigned” will require all scripts to be signed before running.

5. Can I run scripts without changing the execution policy?

Yes, you can run individual scripts bypassing the policy by executing PowerShell with the -ExecutionPolicy Bypass parameter, e.g.,

powershell -ExecutionPolicy Bypass -File .	est.ps1

.

6. How do I confirm the current execution policy?

Run

Get-ExecutionPolicy

in PowerShell. To see policies at different scopes, use

Get-ExecutionPolicy -List

.

}

Related

• How to Fix Mouse Going to Second Monitor While in Game
• How to Fix Mouse Cursor Not Showing on Windows 11
• How to Fix Mouse Cursor Not Moving to Second Monitor in Windows 11