firebase.ps1 cannot be loaded because running scripts is disabled on this system

avatar

Borislav Hadzhiev

Last updated: Nov 22, 2022

banner

Photo from Unsplash

firebase.ps1 cannot be loaded because running scripts is disabled on this system #

The error "firebase.ps1 cannot be loaded because running scripts is disabled on this system" occurs when the execution policy does not allow running the specific script on Windows. Use the Set-ExecutionPolicy -ExecutionPolicy RemoteSigned command to solve the error.

PowerShell
firebase : File C:\Users\bobbyhadz\AppData\Roaming\npm\firebase.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.

Open your PowerShell as an administrator and set its execution policy with the Set-ExecutionPolicy command.

To run PowerShell as an administrator:

  1. Click on the Search bar and type "PowerShell".
  2. Right-click on the "PowerShell" application and click "Run as administrator".

run powershell as administrator

  1. Run the following command.
shell
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

The Set-ExecutionPolicy command sets the PowerShell execution policy for the Windows computer.

The RemoteSigned execution policy is the default execution policy for Windows server computers. It requires that all scripts and configuration files that were downloaded from the internet are signed by a trusted publisher.

This effectively removes the execution policy of Restricted, which doesn't allow us to load configuration files or run scripts. The Restricted execution policy is the default for Windows client computers.

Make sure to open your PowerShell as an administrator before you run the Set-ExecutionPolicy command.

If you aren't able to run the command as an administrator, try running it with the CurrentUser parameter.

shell
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

set executionpolicy remotesigned scope currentuser

The RemoteSigned policy still prevents us from running unsigned scripts.

Now, run the Get-ExecutionPolicy command:

shell
Get-ExecutionPolicy

run get execution policy command

The Get-ExecutionPolicy command should display the effective execution policy for the current PowerShell session (RemoteSigned).

If you get RemoteSigned back, then you have successfully updated your permissions and are able to run the firebase command.

You can also run the command with the -List parameter to display the execution policies for each scope in the order of precedence.

shell
Get-ExecutionPolicy -List

get execution policy list command

When run with the -List parameter, the command returns a list of all execution policy values for the session listed in precedence order.

The command should show that the RemoteSigned policy is set for the default scope (LocalMachine).

Alternatively, you can try to delete the C:\Users\Your_User_Name\AppData\Roaming\npm\firebase.ps1 file and restart your terminal.

Make sure to replace the Your_User_Name placeholder with your actual username.

After restarting your terminal, try running the command again.

If that doesn't help, clear your npm cache and re-run the command.

shell
# 👇️ clean npm cache npm cache clean --force

clean npm cache

If nothing else works, you can try to set the execution policy to Unrestricted, which means that the system would allow unsigned PowerShell scripts to run.

To run PowerShell as an administrator:

  1. Click on the Search bar and type "PowerShell".
  2. Right-click on the "PowerShell" application and click "Run as administrator".

run powershell as administrator

  1. Run the following command.
shell
Set-ExecutionPolicy -ExecutionPolicy Unrestricted

Starting with PowerShell 6.0, Unrestricted is the default execution policy for non-Windows computers and can't be changed.

Alternatively, you can run the command scoped only to the current user.

PowerShell
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted

If I run the Get-ExecutionPolicy -List command, I can see that the execution policy for the LocalMachine scope is now set to Unrestricted.

PowerShell
Get-ExecutionPolicy -List

execution policy of local machine set to unrestricted

The policy loads all configuration files and runs all scripts. If you run an unsigned script that was downloaded from the internet, you would still get prompted for permission before it runs.

Alternatively, you can set your ExecutionPolicy to Bypass.

When using the Bypass policy, nothing is blocked and there are no warnings or prompts. Bypass is more permissive than Unrestricted.

Make sure to open PowerShell as an administrator before issuing the command.

PowerShell
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Bypass -Force

set executionpolicy to bypass

You can also bypass the policy for a specific script (.ps1) file.

PowerShell
powershell -ExecutionPolicy Bypass -File "C:\path\to\script.ps1"

bypass policy for specific script

The possible execution policy values are the following.

NameDescription
AllSignedRequires that all scripts and configuration files are signed by a trusted publisher.
BypassNothing is blocked and there are no warnings or prompts.
DefaultSets the default execution policy (Restricted for Windows clients).
RemoteSignedRequires that all scripts and configuration files downloaded from the internet are signed by a trusted publisher.
UndefinedNo execution policy is set for the scope.
UnrestrictedThe default policy since PowerShell 6.0 for non-Windows computers. The policy loads all configuration files and runs all scripts. If you run an unsigned script, you're prompted before the script runs.

You can read more about the Set-ExecutionPolicy command and its possible values and parameters in this section of the official docs.

Conclusion #

The error "firebase.ps1 cannot be loaded because running scripts is disabled on this system" occurs when the execution policy does not allow running the specific script on Windows. Use the Set-ExecutionPolicy -ExecutionPolicy RemoteSigned command to solve the error.

I wrote a book in which I share everything I know about how to become a better, more efficient programmer.
book cover
You can use the search field on my Home Page to filter through all of my articles.