Salesforce CLI Setup Guide

Before You Begin
Release Notes
Move from sfdx (v7) to sf (v2)
Install Salesforce CLI
Update Salesforce CLI
Salesforce CLI Configuration and Tips
Uninstall Salesforce CLI or Plugins
Run Salesforce CLI Using a Docker Image
Salesforce CLI Plugins
Troubleshoot Salesforce CLI
Use the Doctor to Troubleshoot Problems
Error: Bad CPU Type
Where is Salesforce CLI Installed?
Error: Command Failed with ENOENT
Error After Installing Salesforce CLI on PowerShell Using npm
CLI Deprecation Policy
Next Steps
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Error After Installing Salesforce CLI on PowerShell Using npm

After installing Salesforce CLI on Windows PowerShell using npm, you get a security policy error whenever you try to execute any CLI command. Installing with the Windows-specific installer works correctly.

The error looks something like this:

1sf : File C:\Users\<username>\AppData\Roaming\npm\sf.ps1 cannot be loaded because running scripts is disabled on this system

The problem is that you have a PowerShell execution policy configured for your computer that’s blocking Salesforce CLI from working correctly.

To fix the error, work with your administrator to manage the policy settings on your computer to disable the one that's blocking Salesforce CLI. For more information, see about_Execution_Policies in the Microsoft PowerShell documentation.