Answered by : amit-bhagat
add following in vscode > settings.json
"terminal.integrated.profiles.windows": { "PowerShell": { "source": "PowerShell", "icon": "terminal-powershell", "args": ["-ExecutionPolicy", "Bypass"] }
},
"terminal.integrated.defaultProfile.windows": "PowerShell"Source : https://stackoverflow.com/questions/56199111/visual-studio-code-cmd-error-cannot-be-loaded-because-running-scripts-is-disabl/67420296#67420296 | Last Update : Wed, 22 Dec 21
Answered by : muhammad-mabrouk
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"
"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)Source : https://stackoverflow.com/a/56199112/6663458 | Last Update : Sat, 12 Sep 20
Answered by : selfish-swiftlet-p3mczx931udh
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachineSource : https://www.roelpeters.be/solved-running-scripts-is-disabled-on-this-system-in-powershell/ | Last Update : Mon, 09 Nov 20
Answered by : confused-crayfish-sey14ldp6st5
"terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"]Source : https://stackoverflow.com/questions/56199111/visual-studio-code-cmd-error-cannot-be-loaded-because-running-scripts-is-disabl | Last Update : Tue, 07 Jul 20
Answered by : anxious-alpaca-rfv7ojuyiqaa
"terminal.integrated.shellArgs.windows": ["-ExecutionPolicy", "Bypass"]Source : https://stackoverflow.com/questions/56199111/visual-studio-code-cmd-error-cannot-be-loaded-because-running-scripts-is-disabl | Last Update : Wed, 06 Jan 21