Reputation: 341
After installing VSCode, I started receiving this certain notification saying
The connection to the terminal's pty host process is unresponsive, the terminals may stop working.
The notification won't disappear until I click the restart button. But despite clicking this, no changes occurs and the notification pops up again after few seconds.
This problem caused my terminal to stop working and running node applications impossible.
Upvotes: 29
Views: 34633
Reputation: 3783
I had this happen when using the Remote SSH extension and VS Code 1.92.0. Restarting as suggested in other answers didn't fix it for me.
To fix it I SSHed into the machine from another terminal and deleted the local .vscode-server
directory.
ssh me@host
rm -rf .vscode-server
Then restarted VS Code and it reinstalled the server components and everything is working again as expected.
Upvotes: 4
Reputation: 1
I realized a silly mistake causing this error message for me.
If I do this:
code .
The integrated terminal doesn't work.
If I do this:
code . &
The integrated terminal works.
Upvotes: 0
Reputation: 25
Simply Kill the terminal and wait a minute. In my case it's working perfectly in MacOS :)
Upvotes: 0
Reputation: 551
I just encountered the same issue in 1.79.2 (windows 10) Just closed all the windows in VSC and could launch a new terminal
Upvotes: 0
Reputation: 470
This is how I solved the issue:
Ctrl + Shift + P
(or Cmd + Shift + P on macOS) to open the command palette.Developer: Reload Window
" option. This will reload the Visual Studio Code window.After this, my terminal started working normally.
Upvotes: 19
Reputation: 11
same problem with 1.79 - downgrading to former version makes wsl extension imcompatible, gradle java applications stopped working on wsl - not sure if this is related
Upvotes: 1
Reputation: 151
Look up the extension "Dev Container" -> uninstall it -> reload VS Code-> reinstall the extension.
Hope this fixes it for you as well.
Upvotes: 15
Reputation: 206
This is known issue https://github.com/microsoft/vscode-remote-release/issues/7964
The fix will be included in the next 1.76
stable release, that is expected to be released in the first week of March 2023.
In the meantime you could either switch to the insiders builds or revert to the 1.74.3
version.
Upvotes: 6