SOLVED – ng: File C:\Users\admin\AppData\Roaming\npm\ng.ps1 cannot be loaded

Resolving the Angular error message “ng: File C:\Users\admin\AppData\Roaming\npm\ng.ps1 cannot be loaded because running scripts is disabled on this system” typically involves adjusting the PowerShell execution policy on your Windows system. This error occurs because the default security settings in PowerShell restrict the execution of scripts to safeguard your system from unauthorized or harmful scripts.

Here’s a step-by-step guide to fixing this issue:

1. Open PowerShell as an Administrator:
   • Search for “PowerShell” in the Start menu.
   • Right-click on “Windows PowerShell.”
   • Select “Run as administrator.”
2. Check the Current Execution Policy:
   • In PowerShell, enter the command Get-ExecutionPolicy to view the current policy status.
3. Change Execution Policy (If Necessary):
   • If the policy is set to “Restricted,” you’ll need to change it to a less restrictive one for script execution. The recommended options are “RemoteSigned” or “Unrestricted,” with “RemoteSigned” being safer.
   • To set the policy to “RemoteSigned,” use the command Set-ExecutionPolicy RemoteSigned.
   • Alternatively, for “Unrestricted” (which is less secure), use Set-ExecutionPolicy Unrestricted.
   • Confirm the change when prompted by typing “Y” and pressing Enter.
4. Retry Running the Angular CLI Command:
   • After setting the execution policy, try executing the Angular CLI command again. The script error should now be resolved.
5. Revert Execution Policy After Use (Recommended):
   • For security reasons, it’s advisable to reset the execution policy to its original, more restrictive setting after you’re done.
   • To revert, run Set-ExecutionPolicy followed by the policy level you prefer (e.g., “Restricted”).

Remember, altering the execution policy can have security implications. Only change it when necessary, and always revert to a more secure setting after performing your required tasks.

For more information and detailed guidance, visit Microsoft’s official documentation on PowerShell execution policies.

Important Note:

While these steps are generally effective, always be cautious when changing system settings, especially on a work or shared computer. If you’re unsure or face persistent issues, consulting with an IT professional or system administrator is advisable.