If you use angular, Node, JAVA, python, Javascript or any other programming language on windows computer then you may have come across this issue, or perhaps you trying to run a command inside your project terminal in VS code or powershell and then get this error “ng.ps1 cannot be loaded because running scripts is disabled on this system”. Dont worry you are not alone. This tutorial will assist you in fixing this error irrespective of your scenario.
Below is a video tutorial on how to fix it but if you are more of a reader then continue reading
According to angular documentation “//angular.io/guide/setup-local” power script is disabled by default
To fix this, navigate to your project directory e.g C:/users/demouser/projectdirectory/ and run the following command
Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSignedNow when you try to run your Angular command or the command you were trying to execute before it should work perfectly now.
If you are not getting it right or having difficulties on your side, please watch the video tutorial.
YouTube video tutorial
If you’ve installed angular before and you’re having “ng command not found” issues I have written a detailed step to fix it here. Also if you want to completely uninstall angular globally from your mac computer, I have written a step-by-step guide to uninstall mac completely from your mac and also made a video that will guide you.
Don’t forget to leave us a comment in the comment section below, like our videos, if you don’t like them please hit the dislike button I’m sure you won’t do that lol, it helps us grow.
If you enjoyed this post, we’ll be very grateful if you’d help spread it by sharing it with your friends using the share button. you can also get our latest updates by following us on Facebook, Twitter, Linkedin, and Instagram. Don’t forget to subscribe to our Youtube channel for more Tech Tutorials, Tech reviews, and Tech reviews.
KB ID 0001417 If you’ve arrived here, you are trying to run a script, and you cant;Problem
PS C:\Users\{User-name}> .\{script-name}.ps1 .\{script-name} : File C:\Users\{User-name}\{script-name} cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at //go.microsoft.com/fwlink/?LinkID=135170. At line:1 char:1 + .\{script-name} + ~~~~~~~~~~~~~~~~~~ + CategoryInfo : SecurityError: (:) [], PSSecurityException + FullyQualifiedErrorId : UnauthorizedAccess PS C:\Users\\{User-name}>
Solution
Execute the following command;
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
Then run your script.
THIS WILL ONLY WORK: While that PowerShell window is open, so don’t close it if you are running a lot of scripts.
I Want to Always be Able to Run Scripts?
OK you can either change the ‘Scope’ of that last command, from ‘Process’ to to ‘CurrentUser’, or ‘CurrentMachine’.
- Process: The execution policy affects only the current Windows PowerShell process.
- CurrentUser: The execution policy affects only the current user.
- LocalMachine: The execution policy affects all users of the computer.
Or you can simply change the policy ‘Globally’;
Set-ExecutionPolicy {Value}
Possible values are;
- Restricted: Does not load configuration files or run scripts. Restricted is the default execution policy.
- AllSigned: Requires that all scripts and configuration files be signed by a trusted publisher, including scripts that you write on the local computer.
- RemoteSigned: Requires that all scripts and configuration files downloaded from the Internet be signed by a trusted publisher.
- Unrestricted: Loads all configuration files and runs all scripts. If you run an unsigned script that was downloaded from the Internet, you are prompted for permission before it runs.
- Bypass: Nothing is blocked and there are no warnings or prompts.
- Undefined: Removes the currently assigned execution policy from the current scope. This parameter will not remove an execution policy that is set in a Group Policy scope.
Related Articles, References, Credits, or External Links
NA