Terminal on Windows 7 does not show any text

[Bendjen]

• VSCode Version: 1.20.0
• OS Version: win7 SP1 X64

Steps to Reproduce:

1.When I use ctrl+~ open the terminal, can't input anything in the terminal
2.And I also find when I right-click a folder， the option [open in the terminal ] is instead of [open in the cmd], but my "terminal.integrated.shell.window has been config to powershell.exe
3.It happened after I updated to the latest version.
4.It cannot be solved after restarting the system or vscode.
5.The powershell outside is working normally.

Does this issue occur when all extensions are disabled?: Yes

[Shiroyan]

i also have this problem

[Tyriar]

Does it show when you toggle the terminal (ctrl+`, ctrl+`) or zoom in and out (ctrl++, ctrl+-)?

[Tyriar]

Also are there any errors in the devtools console (Help > Toggler Developer Tools)

[preinoch]

@Tyriar I can use these shortcuts to toggle the terminal or zoom in and out. Devtools have no error, there are a warning:

Ctrl+Alt+ keybindings should not be used by default under Windows.

[Shiroyan]

I tried to specify powershell and git-bash, reinstall vscode, restart computer, ban all extensions. terminal still no response.

[physihan]

mark！

[Lenic]

mark

[physihan]

revert to last version，reinstall 1.19.2
the terminal will show again

版本 1.19.2
提交 490ef76
日期 2018-01-10T15:55:03.538Z
Shell 1.7.9
渲染器 58.0.3029.110
Node 7.9.0
架构 x64

[Bendjen]

@Tyriar

1. 'Does it show when you toggle the terminal (ctrl+, ctrl+) or zoom in and out (ctrl++, ctrl+-)?'
   A: It shows with a block where I can input nothing.
2. 'Also are there any errors in the devtools console (Help > Toggler Developer Tools)'
   A: Yes,but i seems has no relation with terminal.
   

After disabling these extensions.

3.The problem disapperred for one day(I did nothing) . But it(the problem) appear again today(I did nothing),
and I have no idea about that.

版本 1.20.0
提交 c63189d
日期 2018-02-07T17:09:39.780Z
Shell 1.7.9
渲染器 58.0.3029.110
Node 7.9.0
架构 x64

[woshiguabi]

Seems like a System Permissions issue.
Find Code.exe in the installation path, check run as administrator and back to normal.

[Technoblazed]

@woshiguabi not the case for me. Even running as admin still doesn't fix it. (On insiders anyway)

Okay so, disabling compatibility mode seems to fix it, regardless of if run is administrator is enabled or not.

[Tyriar]

Okay so, disabling compatibility mode seems to fix it, regardless of if run is administrator is enabled or not.

@bitcrazed FYI, this might be another Windows regression

[NARUTOne]

@woshiguabi good, thank you

[davec21]

Been noticing this as well. It's weird though because the terminal will work fine for a bit and I can run node commands, ionic commands, etc. I'll minimize code or drag to a new window and terminal disappears. I can get it back by clicking the garbage can and re-opening the terminal with Ctrl+J

[bitcrazed]

This is really difficult to track down without a repro. If anyone has specific repro steps, please share.

Thanks.

[flarpblart]

Add this to your settings.json

"terminal.integrated.shellArgs.windows": ["-NoLogo"]

[dougal83]

Wonder if this is related to to the issue. I recently started experiencing an empty terminal on win 10, while pressing enter reveals the prompt. I've noticed that there is a vertical scroll bar. If I make the terminal window large/tall enough(half my screen) then a new terminal shows the prompts as expected without a scroll bar. Not a show stopper, wondering if the experience is similar/repeatable for anyone here.

[Tyriar]

@dougal83 it's a Windows 10 bug: #57803, press enter once or twice to see your prompt

[vadim-96]

I have the same problem. My VS Code: 1.30.2 (user setup).

Please stop commenting here if you're on Windows 10, you're seeing a bug in Windows that is fixed in the next version #57803.

How long to wait this next version?

[Jexn]

Please stop commenting here if you're on Windows 10, you're seeing a bug in Windows that is fixed in the next version #57803.

版本: 1.31.0 (system setup)
提交: 7c66f58
日期: 2019-02-05T22:35:56.624Z
Electron: 3.1.2
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

this version not fix

[yw662]

I am on windows 1809 17763.316 The bug is still here.

Will preview versions solve this ?

[leslieeilsel]

I think I found a temporary solution!
Step1: Open CMD terminal, edit properties, check this option

Step2: Restart the system

Before：

After：

System Info

Windows 10 1809

VSCode Info

Version: 1.33.1 (user setup)
Commit: 51b0b28
Date: 2019-04-11T08:27:14.102Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

[devsetgo]

@yw662 I am on v 1809 17763.437 and I have the problem. Both on CMD and Bash (ubuntu 18.04 WSL).

@leslieeilsel - I tried your suggestion and it cause the cmd prompt to crash (Bash is my default).

[leslieeilsel]

@devsetgo It seems that this is not a universal solution, let us wait for the official fix.

[tyrfing666]

Also check the terminal.integrated.cwd setting.

I moved computers (from Windows 7 to Windows 10, drives C: and D: to only C:) and terminal stopped working. At first it would exit with code 2, then when I updated today, it would start and freeze with just a white square.

It turns out that my terminal.integrated.cwd setting was set to a folder on D drive, which no longer existed. Changing to to a folder that does exist fixed Terminal.

[hugomaia]

I think I found a temporary solution!
Step1: Open CMD terminal, edit properties, check this option

Step2: Restart the system

Before：

After：

System Info

Windows 10 1809

VSCode Info

Version: 1.33.1 (user setup)
Commit: 51b0b28
Date: 2019-04-11T08:27:14.102Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

Thanks! This really works!
Below the same window in portuguese:

[cikent]

@woshiguabi not the case for me. Even running as admin still doesn't fix it. (On insiders anyway)

Okay so, disabling compatibility mode seems to fix it, regardless of if run is administrator is enabled or not.

@Technoblazed This worked for me, thank you!

@Tyriar, thank you for marking my ticket as duplicate so I could find this thread and devise a Workaround until this is fixed.

[MaybeMeet]

ok, I see you are all in windows system. And I have the same question in ubuntu16.04. And when I meet the problem, it can be recovered after reboot the vscode. But it will appear some times later. It is so terrible. Anyone know how to solve it, please tell me. thanks a lot.

[cikent]

ok, I see you are all in windows system. And I have the same question in ubuntu16.04. And when I meet the problem, it can be recovered after reboot the vscode. But it will appear some times later. It is so terrible. Anyone know how to solve it, please tell me. thanks a lot.

^ see if you can access the Properties for Visual Studio Code -> then search through those settings looking for Compatibility options -> Ensure that Visual Studio Code can run as an Administrator, but everything else should be toggled/turn-ed Off.

See if that helps.

[Tyriar]

There are no plans to invest further in Windows 7 support and the backend that we use for it (winpty), looking forward from Windows 10 1903 we use conpty which is a terminal backend provided by the same team that builds Windows Terminal so we can action such requests much easier.

If you're on WIndows 10 and having issues you're probably seeing #73790 and should uncheck use legacy console in conhost's properties.

[vscodebot]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!