Visual Studio Pro 2019 bash.exe terminal blank and unresponsive

Question

Visual Studio Pro 2019 bash.exe terminal blank and unresponsive

amp4045 opened this issue 5 years ago · 16 comments

When attempting to use any terminal (though my preference is using git bash's bash.exe - I use the same configuration in Visual Studio Code)

I get a completely blank, unresponsive, terminal. I've tried turning the "Change to current solution" to false, but that also has not solved my problem. This problem occurs with Powershell, CMD, WSL Bash, and the "OTHER" option (pointed to git bash's bash.exe)

Any thoughts?

Answer 1 · 2019-06-24T16:20:05.000Z

If it occurs with all settings its possible that the backend isn't working properly. If you open up task manager when the terminal is supposed to be running do you see winpty-agent running?

Answer 2 · 2019-06-26T02:03:09.000Z

Sorry for a slow response - but thanks for getting back to me!

Tried this again tonight, same issues. Opening Task manager I see...

Under VScode 2019 32bit (expanded).. about 18 "Console Window Host"

I don't see winpty-agent running. Perhaps I'm missing a pre-req?

Answer 3 · 2019-06-26T15:23:37.000Z

There shouldn't be any pre-reqs you need installed. Do you happen to have the NODE_OPTIONS environment variable set?

Answer 4 · 2019-07-01T16:29:55.000Z

An additional diagnostic step would be to set the SERVICEHUBTRACELEVEL environment variable to all and then provide the logs at %temp%\serviceHub

Answer 5 · 2019-07-11T18:07:19.000Z

Currently away from my PC for a while, so once I get home I'll play with this! Thanks for the help

Answer 6 · 2019-07-20T23:12:01.000Z

It still won't work, btw. I'm attempting to use it in VS Community 2019. In my case, I just downloaded it from Marketplace, so I'm guessing PowerShell should be running...

Answer 7 · 2019-07-23T14:16:09.000Z

@RenanKummer I experience the exact look/feel with my terminal.

Answer 8 · 2019-07-23T14:23:14.000Z

@dgriffen The only thing I received in my serviceHub log was

07/23/2019 10:21:12 : Error : Reached end of stream.
07/23/2019 10:22:24 : Error : Reached end of stream.
07/23/2019 10:22:26 : Error : Reached end of stream.
My terminal looks as RenanKummer's

Answer 9 · 2019-07-23T14:25:47.000Z

I turned back on the switch to current solution flag, and I see text, but cannot type or anything. My servicehub log looks the same as before (Reached end of stream). Perhaps you can repeat it with better insight if you DL the VS 2019 community addition?

Thanks for the help!!

Answer 10 · 2019-07-23T16:01:36.000Z

It looks like something is going wrong with service hub. Did you check to see if the environment variable I mentioned is set? I can't reproduce this on my own machine.

Answer 11 · 2019-07-26T19:11:43.000Z

How do I check the environment variables you mentioned?

Answer 12 · 2019-08-23T08:04:06.000Z

hello
i think it is:
08/23/2019 08:48:36 : Verbose : CreateTerminalAsync read: {"jsonrpc":"2.0","id":2,"error":{"code":-32603,"message":"Request initTerm failed with message: Error launching WinPTY agent: ConnectNamedPipe failed: Windows error 232"}}

here some more logs:

hubHostNode-6724-ieJFLc-1.log
CreateTerminalAsync-hubControllerLookup-15452-ab0kvhtx-1.log
VsixServiceDiscovery-19884-qzmmwgrx-1.log
VsixServiceDiscovery-wwt.pty-18544-i5ssaxki-1.log
CreateTerminalAsync-15452-mrpvljsl-1.log

Answer 13 · 2019-08-23T18:47:46.000Z

According to this bug filed on node-pty, there is something on your system preventing winpty from properly connecting its named pipe. Windows 1903+ shouldn't have this issue since they use the newer conpty infrastructure.

Answer 14 · 2019-08-24T12:07:29.000Z

this is problem with McAfee:
rprichard/winpty#142
Disabling McAfee resolves the issue
I will try W1903+ later ;)

Answer 15 · 2020-02-04T04:23:09.000Z

I'm having this issue as well. It started about 2 weeks ago. I'm not running antivirus, and I've disabled Windows Defender. I've uninstalled and reinstalled WWT. This worked fine for years. One day it just stopped. It still works on another machine where I've updated to the same verions of VS, dotnet core, etc etc.

I generated logs as you asked above, there are lots of them. The environment variable you mentioned is not set. I'm attaching the generated logfiles that have reference to wwt. I don't see anything obvious. Let me know if you need more logs than these.

7D5AEE63-CreateTerminalAsync-4060-hca3s0sh-1.log
7D5AEE63-hubController-5592-wmobzx14-1.log
7D5AEE63-VsixServiceDiscovery-696-xwxrglot-1.log
7D5AEE63-VsixServiceDiscovery-wwt.pty-5592-fb42fnq4-1.log

Windows 10 Pro, 1903, 18362.592

Answer 16 · 2020-12-07T05:14:18.000Z

This is pretty terrible... same issue, trying to run docker-compose in a terminal in VS... I might not be following... but why cant we just do "cnt + c"?