PowerShell says "execution of scripts is disabled on this system."

Also running this command before the script also solves the issue:

Set-ExecutionPolicy Unrestricted

If you are in an environment where you are not an administrator, you can set the Execution Policy just for you (CurrentUser), and it will not require administrator.

You can set it to RemoteSigned:

Set-ExecutionPolicy -Scope "CurrentUser" -ExecutionPolicy "RemoteSigned"

or Unrestricted:

Set-ExecutionPolicy -Scope "CurrentUser" -ExecutionPolicy "Unrestricted"

You can read all about Getting and Setting Execution policy in the help entries:

Help Get-ExecutionPolicy -Full
Help Set-ExecutionPolicy -Full

Open a Windows PowerShell command window and run the below query to change ExecutionPolicy:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

If it asks for confirming changes, press Y and hit Enter.

You should run this command:

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted

Win + R and type copy paste command and press OK:

powershell Set-ExecutionPolicy -Scope "CurrentUser" -ExecutionPolicy "RemoteSigned"

And execute your script.

Then revert changes like:

powershell Set-ExecutionPolicy -Scope "CurrentUser" -ExecutionPolicy "AllSigned"

Open the command prompt in Windows. If the problem is only with PowerShell, use the following command:

powershell Set-ExecutionPolicy -Scope "CurrentUser" -ExecutionPolicy "RemoteSigned"

you may try this and select "All" Option

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned

1. Open Run Command/Console ( Win + R ) Type: gpedit. msc (Group Policy Editor)
2. Browse to Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Windows Powershell.
3. Enable "Turn on Script Execution" Set the policy as needed. I set mine to "Allow all scripts".

Now run the run command what ever you are using.. Trust this the app will runs.. Enjoy :)

I have also faced a similar issue. Try this.

As I'm using Windows, I followed the steps as given below. Open a command prompt as an administrator and then go to this path:

C:\Users\%username%\AppData\Roaming\npm\

Look for the file ng.ps1 in this folder (directory) and then delete it (del ng.ps1).

You can also clear npm cache after this though it should work without this step as well.

First, you need to open the PowerShell window and run this command.

set-ExecutionPolicy RemoteSigned -Scope CurrentUser

Then it will ask you to confirm. Type Y and press Enter.

When you run this command, you can see that your system has set all policies for the current user as remotely. It will take a few seconds to complete this process.

The image will be shown like below:

To check if the execution policy has set. Type:

Get-ExecutionPolicy

If it was set, the output would be like this:

Set-ExecutionPolicy RemoteSigned

Executing this command in administrator mode in PowerShell will solve the problem.

In Window 10:

If you are not administrator, you can use this:

powershell Set-ExecutionPolicy -Scope CurrentUser

cmdlet Set-ExecutionPolicy at command pipeline position 1
Supply values for the following parameters:
ExecutionPolicy: `RemoteSigned`

It solved my problem like a charm!

If you have Git installed, just use Git Bash.

For Windows 11...

It is indeed very easy. Just open the settings application. Navigate to Privacy and Security:

Click on For Developers and scroll to the bottom and find the PowerShell option under which check the checkbox stating "Change the execution policy ... remote scripts".

In Windows 10, enable the option under the name: 'Install apps from any source, including loose files.'

It fixed the issue for me.

Open PowerShell as a administrator. Run the following command

Set-ExecutionPolicy RemoteSigned

Type Y when asked!

I get another warning when I tryit to run Set-ExecutionPolicy RemoteSigned

I solved with this commands

Set-ExecutionPolicy "RemoteSigned" -Scope Process -Confirm:$false

Set-ExecutionPolicy "RemoteSigned" -Scope CurrentUser -Confirm:$false

Go to the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell and set ExecutionPolicy to RemoteSigned.

I had the same problem today. 64-bit execution policy was unrestricted, while 32-bit was restricted.

Here's how to change just the 32-bit policy remotely:

Invoke-Command -ComputerName $servername -ConfigurationName Microsoft.PowerShell32 -scriptblock {Set-ExecutionPolicy unrestricted}

Open the Powershell console as an administrator, and then set the execution policy

Set-ExecutionPolicy -ExecutionPolicy Remotesigned 

There's great information in the existing answers, but let me attempt a systematic overview:

Context

PowerShell's effective execution policy applies:

• to script files (.ps1) only, not also to calls to cmdlets (e.g., Get-ChildItem), for instance.
• on Windows only (that is, on Unix-like platforms (Linux, macOS) execution policies do not apply)

On workstation editions of Windows, script-file execution is disabled by default (policy Restricted), requiring either a persistent modification of the policy to enable it, or a current-process-only modification such as via the -ExecutionPolicy parameter when calling the PowerShell CLI, powershell.exe (Windows PowerShell edition) / pwsh.exe (PowerShell (Core) edition).

Execution policies are maintained separately:

• for the two PowerShell editions:

  • the legacy, Windows-only, ships-with-Windows Windows PowerShell edition (whose latest and last version is v5.1.x)
  • the modern, cross-platform, install-on-demand PowerShell (Core) edition (v6+).

• for the 32-bit and 64-bit versions of Windows PowerShell (both of which are preinstalled)

  • Note: If you were to install 32-bit and 64-bit versions of PowerShell (Core) side by side (which would be unusual), only the LocalMachine scope would be bitness-specific.

For a given edition / bitness combination of PowerShell, the execution policies can be set in multiple scopes, but there's only ever one effective policy, based on precedence rules - see below.

Details

• In PowerShell on Windows, script-file execution is disabled by default in workstation editions of Windows (on Unix, execution policies do not apply); that is, the default execution policy in workstation editions of Windows is Restricted, whereas in server editions, it is RemoteSigned; see the conceptual about_Execution_Policies help topic for a description of all available policies.

• To set a (local) policy that permits script execution, use Set-ExecutionPolicy. There are three scopes that Set-ExecutionPolicy can target, using the -Scope parameter (see below); changing the LocalMachine scope requires elevation (running as admin).

  • To unset a previously set policy in a given scope, use Undefined

• A frequently used policy that provides a balance between security and convenience is RemoteSigned, which allows local scripts - including from network shares - to execute without containing a signature, while requiring scripts downloaded from the internet to be signed (assuming that the downloading mechanism marks such as scripts as internet-originated, which web browsers do by default). For instance, to set the current user's execution policy to RemoteSigned, run the following:

  Set-ExecutionPolicy -Scope CurrentUser RemoteSigned -Force
  

• The PowerShell CLI (powershell.exe for Windows PowerShell, pwsh.exe for PowerShell (Core), v6+) accepts a process-specific -ExecutionPolicy <policy> argument too, which is often used for ad-hoc policy overrides (only for the process being created, the equivalent of Set-ExecutionPolicy -Scope Process ..); e.g.:

  pwsh.exe -ExecutionPolicy RemoteSigned -File someScript.ps1
  

• Important:

  • Execution policies can also be set via Group Policy Objects (GPOs), in which case they can not be changed or overridden with Set-ExecutionPolicy or via the CLI.

  • Execution policies can be set in various scopes, and which one is in effect is determined by their precedence (run Get-ExecutionPolicy -List to see all scopes and their respective policies), in descending order:

    • MachinePolicy (via GPO; cannot be overridden locally)
    • UserPolicy (via GPO; cannot be overridden locally)
    • Process (current process only; typically set ad-hoc via the CLI)
    • CurrentUser (as set by Set-ExecutionPolicy)
    • LocalMachine (as set by Set-ExecutionPolicy, with admin rights)

You can use a special way to bypass it:

Get-Content "PS1scriptfullpath.ps1" | Powershell -NoProfile -

It pipes the content of PowerShell script to powershell.exe and executes it bypassing the execution policy.

Delete the ng.ps1 file in C:\Users[your user]\AppData\Roaming\npm.

And delete the npm cache file in C:\Users\USER\AppData\Roaming.

To fix this issue, we have to set the execution policy, so that the PowerShell script runs on the particular machine. Here is how:

Open PowerShell Console by selecting “Run as Administrator” and set the execution Policy with the command: Set-ExecutionPolicy RemoteSigned Type “Y” when prompted to proceed

credits: https://www.sharepointdiary.com/2014/03/fix-for-powershell-script-cannot-be-loaded-because-running-scripts-is-disabled-on-this-system.html

It happened to me as well. For me, the solution was simple. I didn't realize that the path in the command prompt to run Nodemon was different to where I installed the package.

So it gave me the same error that you've mentioned.

Changing my path resolved it.

For a downloaded file, right-click → Properties

Then click Unblock and click OK. Then run the PowerShell script and it will no longer complain about not being able to run.

Open cmd instead of powershell. This helped for me...

Run Set-ExecutionPolicy RemoteSigned command

Run cmd or powershell as "Run as administrator"