Visual Studio Code - Terminal Blank Screen

I've been using Visual Studio Code since it was in beta and one of the features I like best about it is the integrated terminal for using the Angular CLI in app. I've had it working fine since I had the laptop, but I re-installed Windows 10 over the Xmas break and obviously as a result had to re-install Visual Studio Code.

Since then I've had issues with the Terminal, it's blank until you hit return, at which point you see the path, but not the usual copyright notice you should get from the Windows Command Line.

Before hitting return:

After hitting return:

And this is what I was expecting directly from the Windows 10 Command Line:

So far I've tried the following:

• The usual Windows shut down / restart
• Re-installing VS Code (even changed from regular to insiders)
• Changing the default Command Line Shell from CMD to Powershell and back again
• Adding a new Command Line Shell

Is there anything else I can try? Has anyone else encountered the same issue?

My solution for VSCode 1.39.2 with Ubuntu has been:

File -> Preferences -> Setting -> Features -> Terminal -> Inherit Env

I have the same problem with PowerShell even after installing the 1.32.1 update. I fixed it by going to PowerShell options and checked the "Use legacy console" option and now it works as it should and I thinks it should work with cmd too.

I had the same problem in visual studio code 1.41.1 in ubuntu 18.04,I solved it by editing the settings.json by going through settings and search for 'Inherit Env'and opening Edit in settings.json and changing

"terminal.integrated.inheritEnv": true

The screenshot is provided below

Here is the fix:

1. CLick bottom left setting wheel
2. go to setting > Features > terminal
3. Select Explorer kind: Intergrated
4. Change inheritEnv to true.

After some research I've found that this is a bug in VS Code with the application they use to integrate the shell. Looks like Android Studio has the same issue too. You can read about the more specific how / when / what etc. here:

https://github.com/Microsoft/vscode/issues/57803

This has been fixed on the insiders release that landed for me today (08/01/2019), not sure when this will be rolled out to the general release (if not January then I would imagine it might roll out in February barring no further issues).

So for anyone else still getting this issue, update to the latest version of VS Code. If you have done and you're still getting the same problem you can check and report issues here:

https://github.com/Microsoft/vscode/issues