Resolving the “Script Execution Disabled” Error in PowerShell

 



If you’ve encountered the error message:

File C:\Program Files\nodejs\node_modules\npm\bin\npm.ps1 cannot be loaded because running scripts is disabled on this system.

This guide will help you resolve the issue step-by-step

Why Does This Error Occur?

By default, PowerShell restricts the execution of scripts for security reasons. This restriction is controlled by the Execution Policy, which determines which scripts can run on your system.

To enable script execution, we need to adjust this policy.

Step-by-Step Solution

1. Open PowerShell as Administrator

  • Right-click on the Start Menu or press Win + X.
  • Select Windows PowerShell (Admin).

This is necessary to make changes to your system’s settings.

2. Check the Current Execution Policy

Run the following command to see the current policy for the current user:

Get-ExecutionPolicy -Scope CurrentUser

You will likely see Restricted, which is the default policy.

3. Change the Execution Policy

To allow scripts to run, update the execution policy to RemoteSigned:

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

Here’s what this policy means:

  • Local Scripts: Scripts created on your computer can run without any restrictions.
  • Remote Scripts: Scripts downloaded from the internet must be signed by a trusted publisher.

4. Verify the New Policy

To confirm the policy has been updated, run:

Get-ExecutionPolicy -Scope CurrentUser

It should now display RemoteSigned.

5. Retry Your Command

Close and reopen your terminal, then try running your npm command again:

npm init

The error should no longer appear, and you’ll be able to proceed with your project setup.

Important Notes

  • Security Considerations: Only change the execution policy for the current user (CurrentUser scope). This avoids system-wide changes and minimizes risks.
  • Reverting Changes: If needed, you can revert the policy back to Restricted later using:
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Restricted

Conclusion

By following this guide, you’ve enabled PowerShell to run scripts safely, allowing tools like npm to function without issues. Let me know in the comments if you encounter any other roadblocks or have questions!

Comments

Popular posts from this blog

Stop Storing JWTs in LocalStorage: A 2026 Guide to MERN Auth

Changing Workspace in Eclipse IDE: A Friendly Guide