VSCode won't launch terminal / run program - visual-studio-code

When trying to open the terminal in VSCode, I've been getting the error "The terminal process failed to launch: Starting directory (cwd) "C:\Windows\Sysnative\cmd.exe" does not exist".
Error message
The command line directory is still C:\Windows\System32\cmd.exe, not sure what to do from here, has anyone else had this problem?
Thanks

Related

How to remove the following error in VScode: zsh:1: command not found: msbuild

I have recently started writing my LaTeX documents in VScode on my Mac running Big Sur.
I am able to build my .tex files without issue using the built in "Build LaTeX project" option (the green arrow -- short cut OPT+CMD+B). When I try to build the .tex file with CMD+SHIFT+B, however, the terminal pops up with the following text:
Executing task: msbuild /property:GenerateFullPaths=true /t:build /consoleloggerparameters:NoSummary
zsh:1: command not found: msbuild
The terminal process "/bin/zsh '-c', 'msbuild /property:GenerateFullPaths=true /t:build /consoleloggerparameters:NoSummary'" failed to launch (exit code: 127).
Terminal will be reused by tasks, press any key to close it.
Despite this, the .tex file is still built as normal. My question is: why is this happening and how do I fix it?
Thanks!

Why I can't launch VS Code? I get launch-failed error

I have a issue.
If I try to launch Visual Studio Code i get error: "The window has crashed.(reason: 'launch-failed' code '0')"
and if I try to launch it by cmd i get this error: "spawn EPERM"
No matter if I reinstall, I get always the same error.

EACCES error in VSCode if it's started from the command line of Far Manager

I love to use FarManager as a file explorer in Windows. But I face the same problem each time I try to run the Visual Studio Code from the FarManager's command line:
Error from the extension host: spawn C:\Users\xxx\AppData\Local\Programs\Microsoft VS Code\Code.exe EACCES
The VS Code is started using the following command in the FarManager's command line:
code .

Eclipse (2018-09) CDT project with Cygwin, can't debug the binary

It seems that everything cygwin-related configured and works fine in my Eclipse project, for example Eclipse is able to invoke 'make' or 'gcc', and can even run the compiled binary and show the output in the Eclipse console window.
However, when I try to debug my binary within Eclipse, I get the following error:
Error in final launch sequence:
Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program exited with code 0xc0000135.
Failed to execute MI command:
-exec-run
Error message from debugger back end:
During startup program exited with code 0xc0000135.
During startup program exited with code 0xc0000135.
I do able to launch gdb from my Cygwin console, so it is installed correctly (I assume). But why it fails when I try to use it from Eclipse?
For my case, as you say, it turns out that adding the Cygwin bin folder to the PATH variable solves this problem.
I use Eclipse 2020-06 and Cygwin 64bit on Win7 64bit. And installing Cygwin doesn't change the PATH variable currently.
But it is also confused to me that "build" and "run" work fine in Eclipse whithout the Cygwin bin in PATH.

Unity3D failed at launching on Mac

While trying to launch Unity3d (4.6.1) on Mac(10.10) it gives a popup with this message: Opening file /tmp/licenseloader.html failed because the file or directory doesn't exist.
Please Help.
found the solution finally. have to run Unity as sudo:
sudo /Applications/Unity/Unity.app/Contents/MacOS/Unity