wsl2 won't start anymore using Windows Terminal #13704

Closed
opened 2026-01-31 03:49:51 +00:00 by claunia · 3 comments
Owner

Originally created by @snowgato on GitHub (May 2, 2021).

Windows Terminal version (or Windows build number)

1.7.1033.0

Other Software

No response

Steps to reproduce

Click on Ubuntu-20.04 when launching Windows Terminal

Expected Behavior

Be able to interact bash.exe and use linux commands

Actual Behavior

when Ubuntu 20.04 is selected, a cursor appears at the top-left corner of the Terminal window and nothing more happens.
On the same time, Windows Terminal works fine using Powershell or Cmd.exe and I use wsl2 without issue with Windows Console Host ( the terminal used by default after wsl2 Ubuntu 20.04 install )
Thanks for your help !

Originally created by @snowgato on GitHub (May 2, 2021). ### Windows Terminal version (or Windows build number) 1.7.1033.0 ### Other Software _No response_ ### Steps to reproduce Click on Ubuntu-20.04 when launching Windows Terminal ### Expected Behavior Be able to interact bash.exe and use linux commands ### Actual Behavior when Ubuntu 20.04 is selected, a cursor appears at the top-left corner of the Terminal window and nothing more happens. On the same time, Windows Terminal works fine using Powershell or Cmd.exe and I use wsl2 without issue with Windows Console Host ( the terminal used by default after wsl2 Ubuntu 20.04 install ) Thanks for your help !
Author
Owner

@zadjii-msft commented on GitHub (May 3, 2021):

Could you share your setting.json?

@zadjii-msft commented on GitHub (May 3, 2021): Could you share your `setting.json`?
Author
Owner

@red-socks294 commented on GitHub (May 3, 2021):

Using Ubuntu 20.04 on WSL2 in Windows Terminal works completly.

@red-socks294 commented on GitHub (May 3, 2021): Using Ubuntu 20.04 on WSL2 in Windows Terminal works completly.
Author
Owner

@snowgato commented on GitHub (May 5, 2021):

Hi,
actually the bug was probably a consequence of wsl2 overload, an intensive postgresql task was running on wsl2 and some usual commands also crashed on the regular bash terminal, like man or which.
Strangely, the cursor could blink and it was still possible to execute some simple commands with bash usual terminal.
I tried to uninstall and reinstall Windows Terminal that didn't solve the issue.
When I kill the postgress process that was exhausting the laptop and restarted the computer, Windows Terminal was working again.

@snowgato commented on GitHub (May 5, 2021): Hi, actually the bug was probably a consequence of wsl2 overload, an intensive postgresql task was running on wsl2 and some usual commands also crashed on the regular bash terminal, like man or which. Strangely, the cursor could blink and it was still possible to execute some simple commands with bash usual terminal. I tried to uninstall and reinstall Windows Terminal that didn't solve the issue. When I kill the postgress process that was exhausting the laptop and restarted the computer, Windows Terminal was working again.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13704