How to fix error- nodemon.ps1 cannot be loaded because running scripts is disabled on this system

#node #nodemon #discuss #webdev

A solution for running nodemon on local machine error on Windows :

nodemon.ps1 cannot be loaded because running scripts is disabled on this system. For more 
information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.

So if you ever get this error, simply you can follow these steps to solve the issue-

Step 1:

Open Windows PowerShell with Run As Administrator.

Step 2:

As you see the error is about_Execution_Policies, first to see what's there in the present execution policy. Use this command on Windows PowerShell to get it

Get-ExecutionPolicy

Here you'll see 'Restricted'. So, this is the main reason- running scripts on this system is 'Restricted'.

Step 3:

Now we need to change this policy to allow the operation. Use this command to make it Unrestricted -

Set-ExecutionPolicy Unrestricted

Here you'll get a prompt message. Press Y to change it

That's it. To ensure, you may check the execution policy status by this command again

Get-ExecutionPolicy

You'll get the output 'Unrestricted'

The problem is solved. Now you can use nodemon on your machine.

Top comments (44)

Mohit Saud • Oct 26 '20

"Doesn't work"
PS C:\Windows\system32> Get-ExecutionPolicy
Restricted
PS C:\Windows\system32> Get-ExecutionPolicy Unrestricted
Get-ExecutionPolicy : Cannot bind parameter 'Scope'. Cannot convert value "Unrestricted" to type
"Microsoft.PowerShell.ExecutionPolicyScope". Error: "Unable to match the identifier name Unrestricted to a valid
enumerator name. Specify one of the following enumerator names and try again:
Process, CurrentUser, LocalMachine, UserPolicy, MachinePolicy"
At line:1 char:21

Get-ExecutionPolicy Unrestricted
~~~~~~~~~~~~
- CategoryInfo : InvalidArgument: (:) [Get-ExecutionPolicy], ParameterBindingException
- FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.GetExecutionPolicyCommand

Salem Aljebaly • Oct 28 '20

use Set-ExecutionPolicy Unrestricted
not Get-ExecutionPolicy Unrestricted

Rishi-choudhary • Mar 17 '21

There is set-execution policy

Luiz Antonio Carlin • Apr 14

I´m getting the error bellow when I try to change the policies

Set-ExecutionPolicy Process Unrestricted
Set-ExecutionPolicy: Cannot bind parameter 'Scope'. Cannot convert value "Unrestricted" to type "Microsoft.PowerShell.ExecutionPolicyScope". Error: "Unable to match the identifier name Unrestricted to a valid enumerator name. Specify one of the following enumerator names and try again:
Process, CurrentUser, LocalMachine, UserPolicy, MachinePolicy"

Please, what I´m doing wrong ? can You help-me ?
I'm running PowerShell with administrative rights

Immam • Sep 19 '20

Thanks very much for your smart help where I was continuously watching the youtube video but failed.This article is just spot on.Thanks again

Era Codex • Sep 29 '20

Glad to know that it helps you. You're welcome!

Immam • Nov 19 '20

Hi , can you please make an cross platform app that consists with calendar and messaging service to the google review page .
Please get back to me as soon as you can .