Starting with version 1.1, we can now configure the external shell.
Prior to version 1.6.1, there was only one setting.
"externalTerminal.windowsExec": "powershell"
Starting with version 1.6.1, there is an external and internal configuration of the terminal. Using the value "% COMSPEC%", you can change their COMSPEC environment variable instead.
// The path of the shell that the terminal uses on Windows. When using shells shipped with Windows (cmd, PowerShell or Bash on Ubuntu), prefer C:\Windows\sysnative over C:\Windows\System32 to use the 64-bit versions. "terminal.external.windowsExec": "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe", // The path of the shell that the terminal uses on Windows. When using shells shipped with Windows (cmd, PowerShell or Bash on Ubuntu), prefer C:\Windows\sysnative over C:\Windows\System32 to use the 64-bit versions. "terminal.integrated.shell.windows": "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
I found that it was opening the 32-bit Powershell.exe file. For me, I did not have an established execution policy. So I installed it using the following ...
I elevated my rights (sudo Powershell version):
Start-Process Powershell -Verb Runas
Then in a new enlarged Powershell window:
Set-ExecutionPolicy RemoteSigned
Nathan hartley
source share