Windows Terminal is stuck -- can not view the shell , can not be closed, can not be moved #4493

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

Originally created by @tlsalex on GitHub (Oct 16, 2019).

Environment

Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal (Preview)
Version: 0.5.2762.0

Steps to reproduce

enable openssh client in windows. Start Windows Terminal, it will start the default shell (powershell) , use ssh client connect to a remote ssh server, e.g ssh root@myhost .
wait for the ssh connection until it is timeout (let's say no keep alive package is sent by server or client)

Expected behavior

if the ssh connection is timeout , I can see what happen within the shell, e.g
[root@myhost ~]# Connection to myhost closed by remote host.
Connection to myhost closed.

Actual behavior

After the ssh connection is timeout. The whole windows terminal is stuck, you can not move windows terminal , you can not see what's happen within the shell , but you just can see the background of you desktop. I event can not close windows terminal. I have to click the + button to start a new shell, then I can get back the control fo windows terminal.

stuck

Originally created by @tlsalex on GitHub (Oct 16, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal (Preview) Version: 0.5.2762.0 ``` # Steps to reproduce enable openssh client in windows. Start Windows Terminal, it will start the default shell (powershell) , use ssh client connect to a remote ssh server, e.g ssh root@myhost . wait for the ssh connection until it is timeout (let's say no keep alive package is sent by server or client) # Expected behavior if the ssh connection is timeout , I can see what happen within the shell, e.g [root@myhost ~]# Connection to myhost closed by remote host. Connection to myhost closed. # Actual behavior After the ssh connection is timeout. The whole windows terminal is stuck, you can not move windows terminal , you can not see what's happen within the shell , but you just can see the background of you desktop. I event can not close windows terminal. I have to click the + button to start a new shell, then I can get back the control fo windows terminal. ![stuck](https://user-images.githubusercontent.com/36788337/66916799-93d78080-f04e-11e9-8267-d898ba8feb8f.PNG)
claunia added the Resolution-Duplicate label 2026-01-30 23:49:03 +00:00
Author
Owner

@skycommand commented on GitHub (Oct 20, 2019):

Same issue as #3261 and #3253. Should be merged, IMHO.

@skycommand commented on GitHub (Oct 20, 2019): Same issue as #3261 and #3253. Should be merged, IMHO.
Author
Owner

@DHowett-MSFT commented on GitHub (Oct 21, 2019):

Yeah, looks like a /dupe of #2733. Thanks for finding it!

@DHowett-MSFT commented on GitHub (Oct 21, 2019): Yeah, looks like a /dupe of #2733. Thanks for finding it!
Author
Owner

@ghost commented on GitHub (Oct 21, 2019):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Oct 21, 2019): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4493