Integrated Terminal stopped working, opens externally

[lvcz]

/bug

Since Yesterday i try to Open Terminal in VSCode and it open Externally, using ctrl+j or ctrl+'. My settings are set to open integrated,

[mjbvz]

/needsMoreInfo

[vscodebot]

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.

Happy Coding!

[efroim102]

This just started happening for me too, when opening the first terminal in a new VSCode instance, it opens a cmd line process as an external process instead of inline, with the integrated terminal having a blank cursor.

When closing the external process, I get the error The terminal process terminated with exit code: 3221225786.

When setting wsl as the default shell, it opens an external cmd line process with the error Unsupported console settings. In order to use this feature, the legacy console must be disabled..

VSCode Info
Version: 1.36.1 (user setup)
Commit: 2213894
Date: 2019-07-08T22:59:35.033Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362

P.S. I actually have another instance of VSCode open from a couple of days ago that has 2 integrated terminals open that work fine, but when attempting to add a new terminal tab the same as above happens.

[efroim102]

I just noticed that Windows Terminal crashes right after launch, not sure if this is related.

[efroim102]

@lvcz I was just able to resolve this based on the error mentioned above (Unsupported console settings. In order to use this feature, the legacy console must be disabled.).

By right clicking on a cmd prompt instance, going to properties -> options and disabling the option Use legacy console.

Now everything works as expected, even Windows Terminal, I have no idea who or how legacy console got enabled in the first place.

Note you will need to restart any open terminal instances.

If this resolves the issue for you too, consider closing it as I'm sure the team has plenty issues on their hands...

[lvcz]

as @efroim102 gave more details about my problem, basically the same here, but the terminal worked fine but externally.
This was basically turno off the legacy mode in powershell or cmd , and everything workd fine.

@efroim102 thanks for the help.

[lvcz]

I thinks this is an external change, does not affect the VScode scope.

[Tyriar]

/duplicate #73790