How to fix npm ERR! running scripts is disabled on this system. Run Set-ExecutionPolicy to change in npm

Launch PowerShell with elevated privileges, which is required to change the execution policy:

1. Click the Windows Start menu
2. Type "PowerShell"
3. Right-click "Windows PowerShell" (not Windows PowerShell ISE)
4. Select "Run as administrator"
5. Confirm the User Account Control prompt if it appears

Verify you're running as administrator by checking for [Admin] in the window title.

Run this command to see what policy is currently preventing script execution:

Get-ExecutionPolicy -List

This will display the execution policy at each scope (MachinePolicy, UserPolicy, Process, CurrentUser, LocalMachine). The "CurrentUser" or "LocalMachine" scope showing "Restricted" is what prevents npm from running.

Run this command to enable locally created scripts while maintaining security for downloaded scripts:

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

You'll see a prompt asking to confirm the change. Type Y and press Enter.

The RemoteSigned policy allows scripts written locally (like npm) to run without signatures, while requiring scripts downloaded from the internet to be signed by a trusted publisher.

Confirm the policy was updated and test that npm now works:

Get-ExecutionPolicy
# Should return: RemoteSigned

npm --version
# Should display npm version without the execution policy error

npm install
# Or whatever npm command was failing before

If you prefer not to change PowerShell's execution policy, you can simply use the traditional Command Prompt (cmd.exe) instead, which does not have execution policy restrictions:

# Open Command Prompt and run npm commands
npm install
npm start

Command Prompt does not use PowerShell scripts and will work without any policy changes.