-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The terminal process command 'C:\WINDOWS\System32\cmd.exe' failed to launch (exit code: 2) #62953
Comments
(Experimental duplicate detection) |
Are you on a locked down machine? You should also try the user installer instead of the system installer https://code.visualstudio.com/Download |
I has installed VSCode with user installer,but terminal not works too. Message: |
is this a personal machine or managed by your organization? |
Yes,it is my personal machine. |
Does it work when you switch to powershell? https://code.visualstudio.com/docs/editor/integrated-terminal#_windows |
The terminal process command 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' failed to launch (exit code: 2) |
I'm a bit stumped on this one, hopefully it will be fixed by changing the way we create the process which will likely land in 1.31 #45693 |
Thanks. |
Just remove deleted files from your work space in vs code it works for me |
I also had this issue, because I renamed one of the folders leading to a workspace. Check to see in the Workspace explorer if there's a "!" symbol next to any of the workspaces' names. If so, just remove the Workspace and add it again. Hope this helps. Anyway, this shouldn't prevent the Terminal from being launched, unless you're trying to open the terminal in the directory of the workspace with the error (and even then, it should give a proper error, not "Exit Code 2")
|
VSCode Version:
Version: 1.28.2 (system setup)
Commit: 7f3ce96
Date: 2018-10-17T00:23:51.859Z
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
OS Version:10.0.17134.345
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: