Visual studio code cmd error: Cannot be loaded because running scripts is disabled on this system

Question

Inside of visual studio code, I'm trying to execute a script.bat from the command line, but I'm getting the following error:

File C:\Theses_Repo\train-cnn\environment\Scripts\activate.ps1 cannot be loaded because running scripts is disabled on this system.

After reading this I tried to run the visual studio code in administrator mode, thinking that the problem was a matter of privileges. But the error is throwing anyway.

1. Press the windows-button on your keyboard. 2. Type ‘PowerShell’ 3. Right-click Windows PowerShell 4. Click Run as Administrator 5. Run the following command and confirm with ‘Y’ Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine Referred to link https://www.roelpeters.be/solved-running-scripts-is-disabled-on-this-system-in-powershell/ — S Anil Kumar Dora, May 13 '21 at 10:35

Ricardo Rocha · Accepted Answer · 2021-08-31T17:28:45.707

313

I found out here that you can add to your visual studio code settings the following and the problem will vanish: For visual studio code settings, go to File -> Preferences -> Settings -> Extensions -> Scroll down and find "Edit in settings.json". Do not forget to restart the visual studio code

"terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"]

The reason is that, in build command line integrations like visual studio code, you need to set the command line policies by your self. By setting the above configurations, the visual studio code will do that for you.

(read this to understand better the command line policies)

Update August 2021

It seems that terminal.integrated.shellArgs is deprecated. This answer shows how to do it in new versions.

edited Aug 31 '21 at 17:28

answered May 18 '19 at 12:51

Ricardo Rocha

14,612
20
74
130

2

Thanks a million. This did the trick for me (after 1h of research) and saved me another headache. – Friedrich Siever Dec 08 '19 at 13:19
OK, my mistake. I also had to set Powershell as my default terminal. – Aros Mar 10 '20 at 17:28
3

Thank you sir! After you add this in settings.json , you should reload or reopen vscode, a notification will ask you if you want to grant access for execution policy. – Sorin Veștemean Mar 12 '20 at 06:35
3

Where in the VSCode settings do you add this? – Andy Jun 08 '20 at 09:20
1

@Andy You have in the link associated with the phrase "visual studio code settings " – Ricardo Rocha Jun 08 '20 at 09:29
1

@Andy, Go to File -> Preferences -> Settings -> Extensions -> Scroll down and find "Edit in settings.json" – CCC Aug 26 '20 at 21:08
thank you very much. Now i got more time to core developping. – ORCAs Oct 04 '20 at 12:58
For me I searched for `terminal.integrated.shellArgs` as @Barani mentioned. – Mohammed Noureldin Jan 04 '21 at 03:47
1

Go to the @null comment (three posts below) and you can see that you just have to change from Powershell to CMD as default command prompt. That's all! – Corina Roca Jan 10 '21 at 11:39
Or just hit ctrl + shift + p and type "Open settings.json". You will see the option. Just click it and it will open your settings.json – ajpieri Mar 28 '21 at 03:57
there are one million of "Edit in settings.json". Javed's answer worked for me. – Vincenzooo Apr 13 '21 at 21:36
1

the shellArgs is deprecated in the new versions as it answered below https://stackoverflow.com/a/67420296/2514158 @MoishyS – AbuDawood Aug 22 '21 at 10:41
Why suggest the "Bypass" policy by default? Wouldn't "RemoteSigned" be safer? – Marcos Pereira Jan 26 '23 at 18:10
Great. This answer helped me to get rid of this exact problem occurred to me. Just to describe the steps little more.. After you go to the **File -> Preferences -> Settings -> Extensions -> Scroll down and find "Edit in settings.json" path**, It will open up **settings.json file**. and there, I added this code like this `{ "terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"], "workbench.colorTheme": "Default Dark+", "json.schemas": [ ] }` – Ish Apr 27 '23 at 14:55
Related answer here https://stackoverflow.com/questions/47023796/visual-studio-code-unsigned-powershell-scripts – Nate Anderson May 01 '23 at 18:45

MoishyS · Answer 2 · 2022-01-19T16:53:28.233

217

the issue is that PowerShell by default restricts running scripts unless we change the execution policies.

we can change the execution policies by adding -ExecutionPolicy Bypass args. in vscode you will have to create a shell profile with these args by adding below in settings.json (ctrl + shift + p and type "settings.json")

"terminal.integrated.profiles.windows": {
  "PowerShell": {
    "source": "PowerShell",
    "icon": "terminal-powershell",
    "args": ["-ExecutionPolicy", "Bypass"]
  }
},
"terminal.integrated.defaultProfile.windows": "PowerShell",

Need to restart VS Code and the Terminal.

Note: terminal.integrated.shellArgs settings have been deprecated.

edited Jan 19 '22 at 16:53

answered May 06 '21 at 14:35

MoishyS

2,334
1
6
8

27

Note: defaultProfile is known not to work on the initial restored terminal [#123188](https://github.com/microsoft/vscode/issues/123188) - when you open the terminal from the + button it should work. hopefully will get fixed soon. – MoishyS May 10 '21 at 18:44
4

As of May 2021 this is the correct solution. The old method of setting terminal.integrated.shellArgs.windows no longer works. – Tigger May 10 '21 at 22:57
2

This worked perfectly. The previous answers are depreciated in VS Code. Thank you! – lov2code Aug 27 '21 at 19:18
5

Had to restart the powershell within vscode to make this work. Thanks. – PG_eon Nov 12 '21 at 18:10
This works, just needed to restart VS Code and the Terminal afterwards – user2552108 Jan 18 '22 at 01:58
4

VSCode might give you three options of settings.json: workspace settings, default settings, and just settings. It didn't work for me unless I chose the last option: Open Workspace Settings. – DoomGoober Jan 23 '22 at 04:15
2

works perfectly. I also had to start a new powershell inside VSCODe with + button. – Ani Mar 19 '22 at 22:49
thank you so much. I was very upset after installing typescript and got this error – Nam Lee May 11 '22 at 16:00
2

This solution kind of worked for me. I was unable to change the settings.json file as it was read-only when doing it this way. I had to combine with a "flavor" of Abdu's answer. I had to use File->Preferences->Settings and select "Edit in settings.json" in order to modify the file. I searched for "profiles" instead of "automation" though....not sure what the automation settings are, but they didn't work for me. – user1011627 Jun 22 '22 at 12:13
This solution works: I edited the "User" settings.json (not default, not workspace). Restarting VS Code only didn't pick up the changes. I did what @Ani said and deleted my PowerShell terminal window (use the "Kill terminal" trashcan icon on the right side of the terminal area) then "+" create a new instance. Then my settings were picked up and tsc command worked. – kenswdev Aug 19 '22 at 14:39

score 151 · Answer 3 · edited Dec 24 '22 at 21:42

151

The simplest way to deal with this problem from Visual Studio Code is to change from powerShell to cmd (assuming there's no reason for using powershell in your case). To do so, follow these few steps:

Terminal -> New Terminal
In right lower corner select "Select Default Shell" option

Select "Command prompt"

I have not found such solution among current answers.

edited Dec 24 '22 at 21:42

starball

20,030
7
43
238

answered Apr 18 '20 at 17:11

hpopiolkiewicz

3,281
4
24
36

2

This simple solution work great for me, I try the other solutions with no success. – Jozcar Jan 08 '23 at 22:00
Now this is updated as "Select default profile" – Nirmal Seneviratne Mar 03 '23 at 15:39

score 108 · Answer 4 · edited Jan 21 '21 at 13:27

108

For more simplicity, I want to add the vs code settings path in addition to Ricardo's answer. you can get it like this:

File -> Preferences -> Settings and in the search bar write "automation".

After that, by looking your operating system enter "edit in settings.json".

Finally, add the following b/n the braces:

"terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"]

edited Jan 21 '21 at 13:27

javed

406
3
10

answered Dec 09 '19 at 08:20

Abdulwehab

1,356
2
10
12

3

Might be a silly question but what's b/n here? – sskular Jun 01 '22 at 12:22
It is a short hand for between. – Abdulwehab Jun 18 '23 at 14:24

jayprakash chaurasia · Answer 5 · 2020-02-18T15:42:13.677

63

Face the same issue and this works for me. open PowerShell as Administrator and paste this.

    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

edited Feb 18 '20 at 15:42

answered Feb 18 '20 at 15:31

jayprakash chaurasia

639
5
3

More info here: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.3&viewFallbackFrom=powershell-6 – Marcos Pereira Jan 26 '23 at 18:07

pix data · Answer 6 · 2022-08-30T08:12:36.557

47

Press the windows-button on your keyboard
Type 'PowerShell'
Right-click Windows PowerShell
Click Run as Administrator
Run the following command and confirm with ‘Y’

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine

for more information: https://www.roelpeters.be/solved-running-scripts-is-disabled-on-this-system-in-powershell/

Hope this would resolve the issue

edited Aug 30 '22 at 08:12

answered Mar 18 '21 at 06:32

pix data

731
7
14

thanks a lot , I tried all solutions , but only this one help me – Navid Jul 05 '22 at 14:06

score 23 · Answer 7 · edited Sep 13 '21 at 09:27

Open VS code
File -> Prefrences -> settings
in the Search bar -> Search for "terminal.integrated.shellArgs"
Click on the "Edit in setting.json" for Terminal>integrated>ShellArgs > windows [whatever you OS, select the respective settings]
At the top of the json file add this :

terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"]

For example after adding your json might look like:

{
    "terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"],
    "git.autofetch": true,
    "peacock.favoriteColors": [
        {
            "name": "Angular Red",
            "value": "#b52e31"
        },
        {
            "name": "Auth0 Orange",
            "value": "#eb5424"
        },

restart the VS code and try the command again (in my case i was trying ng serve)

Note: terminal.integrated.shellArgs settings have been deprecated.

score 19 · Answer 8 · answered Feb 27 '21 at 09:40

19

Run the below command then the issue will be resolved.

set-ExecutionPolicy RemoteSigned -Scope CurrentUser ( I tried only in windows )

answered Feb 27 '21 at 09:40

Viplav Soni

1,489
13
18

Just some more additional information on [this](https://learn.microsoft.com/en-gb/powershell/module/microsoft.powershell.core/about/about_execution_policies?view=powershell-7.1) – veritaS May 22 '21 at 14:37

score 15 · Answer 9 · edited Feb 14 '20 at 11:13

15

I have faced the same problem due to security reasons on Windows 10. I managed to fix it by running the following command in PowerShell:

Set-ExecutionPolicy -ExecutionPolicy Unrestricted

edited Feb 14 '20 at 11:13

Ed The ''Pro''

875
10
22

answered Dec 28 '19 at 12:44

soumen saha

151
1
3

score 12 · Answer 10 · answered May 07 '21 at 11:12

Open VS code
Go to File -> Prefrences -> settings
in the Search bar -> Search for "terminal.integrated.defaultprofile.windows"
Click on the "Edit in setting.json" for Terminal > integrated > Default Profile: Windows [whatever you OS, select the respective settings].

At the top of the JSON file add this :

"terminal.integrated.defaultProfile.windows": "PowerShell",
"terminal.integrated.profiles.windows": {
    "PowerShell": {
        "source": "PowerShell",
        "args": [
            "-ExecutionPolicy",
            "Bypass"
        ]
    }
},

Note: The following settings line is deprecated:

"terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"]

Thank you. And it needs to restart the VS code. – Green Y. Jul 19 '21 at 09:55 — Green Y., Jul 19 '21 at 09:55

score 10 · Answer 11 · edited Feb 14 '20 at 12:33

10

I opened VS Code as Administrator and ran this command in the terminal:

Set-ExecutionPolicy Unrestricted

It allowed me to run the scripts without an errors.

edited Feb 14 '20 at 12:33

Ed The ''Pro''

875
10
22

answered Jan 30 '20 at 22:39

user1838609

111
1
6

This might work but sounds like bad practice from a security standpoint. – LondonAppDev Oct 20 '20 at 14:43

score 6 · Answer 12 · answered Oct 24 '20 at 12:35

6

For security reasons, in case you share the computer with other users, use: PowerShell:

Set-ExecutionPolicy -Scope CurrentUser Unrestricted

No need for Admin privileges.

answered Oct 24 '20 at 12:35

Daniel

61
1
1

After entering the above command it works – user2059013 Sep 07 '21 at 15:02

score 4 · Answer 13 · answered Jan 29 '21 at 10:32

Steps to resolve the issue,

Open PowerShell in your Computer (This will change the PowerShell execution policy on your Windows Computer)
Run ( To get-ExecutionPolicy for your Machine )

Get-ExecutionPolicy -List

Run

Set-ExecutionPolicy -Scope CurrentUser Unrestricted

bula · Answer 14 · 2020-02-14T10:34:04.067

3

If you don't need to explicitly run this on PowerShell, then you may want to try running it in the command prompt.

Just type cmd and press enter. Doing so will open the command prompt in the current terminal window. It will behave same as a normal command prompt.

edited Feb 14 '20 at 10:34

answered Feb 06 '20 at 09:01

bula

8,719
5
27
44

score 3 · Answer 15 · edited Aug 13 '21 at 07:19

For Win10 users

In Visual Studio Code: File -> Preferences -> Settings
Type in the search: terminal.integrated.defaultProfile.windows
Click on the Edit in setting.json
Add this:

"terminal.integrated.profiles.windows": {
  "PowerShell": {
    "path" : [
      "${env:windir}\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
    ],
    "source": "PowerShell",
    "icon": "terminal-powershell",
    "args": [
      "-NoLogo",
      "-ExecutionPolicy",
      "ByPass"]
  }
},
"terminal.integrated.defaultProfile.windows": "PowerShell",

Save and restart Visual Studio Code

score 3 · Answer 16 · answered Sep 29 '21 at 07:31

3

The location of tag is changed, Steps:

Do Ctrl+Shift+P and type 'settings' and then choose 'Preferences: Open settings (JSON)':
Then add "args": ["-ExecutionPolicy", "Bypass"] inside "terminal.integrated.profiles.windows"."PowerShell" in settings.json :
Restart VS code.

There can be different steps if anything changed with VS code updates in future.

answered Sep 29 '21 at 07:31

Priyank Kotiyal

241
2
13

why do we have shit tools like vscode , just use pycharm , its way better – dev Jan 19 '22 at 20:55
I think people working on windows finds it better, WebStorm is also good but its paid. – Priyank Kotiyal Jan 20 '22 at 06:24
i use windows , i generally use both of them (to keep me updated) , my GitHub desktop is connected to vscode for final reviews/comments but my development env. is pycharm , and pycharm is so much better. – dev Mar 13 '22 at 23:11

score 2 · Answer 17 · edited Aug 21 '21 at 12:40

2

Added this line in settings.json

"terminal.integrated.defaultProfile.windows": "PowerShell"

For me used following command in VS powershell and it starts working

Set-ExecutionPolicy -ExecutionPolicy Unrestricted

edited Aug 21 '21 at 12:40

lejlun

4,140
2
15
31

answered Aug 20 '21 at 22:32

shabnam

61
1
9

score 1 · Answer 18 · answered Dec 05 '19 at 12:58

1

Run VS-Code as ADMIN.

This fixed my issue on my home PC with running ng new my-App which had produced this error when I first opened VS-Code from the installation process.

answered Dec 05 '19 at 12:58

Jacob Fortuna

29
3

This fixed the issue for one run, but then it came back. The solution above worked for me. – Jacob Fortuna Dec 05 '19 at 13:11

Cyebukayire · Answer 19 · 2022-05-19T06:09:32.420

1

I had the same problem a few minutes ago: I did this and it worked for me

You need to edit your visual studio settings. Go to File -> Preferences -> Settings -> Extensions -> Scroll down and find "Edit in settings.json". Past these codes below, save, and restart the visual studio code.

   {
    "terminal.integrated.profiles.windows": {
        "PowerShell": {
            "source": "PowerShell",
            "icon": "terminal-powershell",
            "args": ["-ExecutionPolicy", "Bypass"]
        }
    },
    
    "terminal.integrated.defaultProfile.windows": "PowerShell",
    "files.associations": {
        "*.html": "html"
    },
}

edited May 19 '22 at 06:09

answered Feb 02 '22 at 07:34

Cyebukayire

795
7
14

2

where should you put this? – Jovane Mullings May 19 '22 at 03:14
Hi @JovaneMullings I've edited my answer with clear path of where you need to paste this. Thank you:) – Cyebukayire May 19 '22 at 06:10

PedroPK · Answer 20 · 2022-06-01T12:41:27.563

Adding this error message just to find this topic easily in the future:

    ng : File C:\Users\[USER_NAME]\AppData\Roaming\npm\ng.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.
    At line:1 char:1
    + ng help
    + ~~
        + CategoryInfo          : SecurityError: (:) [], PSSecurityException
        + FullyQualifiedErrorId : UnauthorizedAccess

score 1 · Answer 21 · answered Sep 07 '22 at 09:27

Unless you actually require the default terminal be windows Powershell, I would suggest simply changing the type of terminal. It's very easy to do: On the right top part of the shell click on the small down-facing arrow next to the plus sign. Then choose which terminal you would like to use (I like good old CMD) and you can even pick a default for the next time you open a new treminal.

score 0 · Answer 22 · answered May 19 '19 at 05:29

This is not a VSCode specific issue, it is a OS one. There are different levels for machine, user, process that allow PowerShell Scripts to run and it must be enabled.

If this is your machine just change the execution policy to RemoteSigned or unrestricted so that is applies to your entire system. If you just want to use it in VSCode, the change your settings file or change you shortcut to include the execution policy you want to use. The Recommendation is RemoteSigned. Meaning all local code will run, but any remote scripts must be signed.

If this is a corporate machine, that has the Execution set to Restricted, then no code will run until that setting is changed. You can still run code by selecting it all in the VSCode editor and hitting F8. Now, if they have enforced this policy, then you need to talk to the IT time to get them to change it for you.

All of this is detailed in the PowerShell Help files.

Get-Command -Name '*executionpolicy*' | ft -AutoSize

CommandType Name                Version Source                       
----------- ----                ------- ------                       
Cmdlet      Get-ExecutionPolicy 3.0.0.0 Microsoft.PowerShell.Security
Cmdlet      Set-ExecutionPolicy 3.0.0.0 Microsoft.PowerShell.Security


# get function / cmdlet details
(Get-Command -Name Get-ExecutionPolicy).Parameters
Get-help -Name Get-ExecutionPolicy -Full
Get-help -Name Get-ExecutionPolicy -Online
Get-help -Name Get-ExecutionPolicy -Examples

    Get-ExecutionPolicy
    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
    Get-ExecutionPolicy -List

(Get-Command -Name Set-ExecutionPolicy).Parameters
Set-help -Name Set-ExecutionPolicy -Full
Set-help -Name Set-ExecutionPolicy -Online
Set-help -Name Set-ExecutionPolicy -Examples

    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
    Set-ExecutionPolicy -ExecutionPolicy Restricted
    Invoke-Command -ComputerName "Server01" -ScriptBlock {Get-ExecutionPolicy} | Set-ExecutionPolicy -Force
    Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy AllSigned -Force
    Get-ExecutionPolicy -List
    Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Undefined
    Set-ExecutionPolicy -Scope Process -ExecutionPolicy AllSigned
    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

Note, if your org is controlling this, the again, talk to them before trying to bypass the policy, because if they did this, this also means they are monitoring it, and if you do this that will know. I have seen things like this engender RPE's. (Resume Producing Events)

score 0 · Answer 23 · edited Jan 23 '21 at 21:50

0

I Have this error in my visual studio 2019 (Version 16.8.4). Finally I found solution which is: EnableScripts (Make from PowerShell os windows (from Registry Editor of windows 10)

Brows the PowerShell as bellow and make 0 => 1 and that is it.

edited Jan 23 '21 at 21:50

Tomer Shetah

8,413
7
27
35

answered Jan 23 '21 at 20:41

kargarf

51
4

score 0 · Answer 24 · answered May 14 '21 at 23:10

After tearing my hair out this is what I ended up doing. Instead of using CMD or PowerShell I switched over to BASH. In the settings.json:

//"terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\cmd.exe",
// "terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",   
        "terminal.integrated.shell.windows": "C:\\Program Files\\Git\\bin\\bash.exe",

The CMD and Powershell here are commented out in case you want to go back to one of those. To get to settings.json:

> File -> Preferences -> Settings -> in search type : "settings.json" ->
> Under [JSON] click "Edit in settings.json"

score 0 · Answer 25 · answered Jul 07 '22 at 16:00

0

I faced a similar issue while trying to use pnpm. I just changed to GitBash instead of PowerShell for vs-code terminal, and it worked.

answered Jul 07 '22 at 16:00

Mayank Kumar Chaudhari

16,027
10
55
122

score 0 · Answer 26 · answered Oct 04 '22 at 05:54

I'm not clear where should I add it ("terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"]).

I have a code like this in the settings.json file

{
"python.defaultInterpreterPath": "C:\\Users\\Hansamal\\AppData\\Local\\Programs\\Python\\Python36\\python.exe",
"workbench.editorAssociations": {
    "*.ipynb": "jupyter-notebook"
},
"notebook.cellToolbarLocation": {
    "default": "right",
    "jupyter-notebook": "left"
},
"json.schemas": [

]

}

score 0 · Answer 27 · answered Nov 01 '22 at 14:48

Update Powershell Execution Policy.

Setting a global unrestricted execution policy will run any script. But also shows a warning from windows.

Set-ExecutionPolicy -ExecutionPolicy Unrestricted

Instead allow the script that is being run. You can find the full path of the script from the error.

powershell -ExecutionPolicy Bypass -File C:\Users\Me\AppData\Roaming\npm\webpack.ps1

Here I have provided access to webpack for running.

score -1 · Answer 28 · answered Jul 22 '22 at 00:44

-1

since we are in 2022, and vdcode has changed the way to fix this issue in setting.json just open the terminal and run

Set-ExecutionPolicy -Scope CurrentUser Unrestricted

answered Jul 22 '22 at 00:44

JERVI

37
5

Visual studio code cmd error: Cannot be loaded because running scripts is disabled on this system

28 Answers28

Update Powershell Execution Policy.

Linked