starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal screen redraw issues when ssh-ing from WSL2 console after recent Windows updates #12982

New Issue
Open
opened 2026-01-31 03:30:39 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 03:30:39 +00:00
Owner
Copy Link

Originally created by @bpkroth on GitHub (Mar 12, 2021).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable): 1.6.10571.0

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19042.0 Microsoft Windows NT 10.0.19042.0

Any other software?
WSL2

Steps to reproduce

My windows machine updated the other night and now I'm having weird terminal issues when I ssh to a remote host from a local WSL2 terminal.
Plain old shell generally seems to work on the remote end, but the moment it needs to go to some form of full screen redraw interface (e.g. less, top, vim, etc.) the screen can't refresh anymore. In some cases, long output (e.g. ps -AH u) will cause it to stall output as well.
Seems to work okay for local sessions though.
The remote machines also work okay from a different Windows laptop's WSL that I have (for the moment since I haven't rebooted to apply the update yet), so it doesn't appear to be the remote end point that's the problem.
It also works okay if I ssh from a Putty terminal emulator on my problematic workstation, so it appears to really be a problem with the terminal emulator on this machine. I have tried starting bash from

  • the various Windows Console programs terminal emulator (Win-R -> bash, pwsh, cmd)
  • the powershell terminal
  • the new "Windows Terminal"
    These all exhibit the same behavior.

When the problem occurs I can enter the magic ~.~. sequence to kill the ssh session and return to the host terminal session. At this point the cursor itself is gone (no longer a white block, underscore, etc.), though I can type again. Running reset in the local bash session recovers the local behavior without needing to restart the console window, but I still get the same issue once I try to ssh to a remote host again.

Expected behavior

Free flowing characters over ssh :)

Actual behavior

Characters stop flowing :(

Links

Feedback hub report: https://aka.ms/AAbi4mw

Originally created by @bpkroth on GitHub (Mar 12, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): 1.6.10571.0 Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.19042.0 Microsoft Windows NT 10.0.19042.0 Any other software? WSL2 ``` # Steps to reproduce My windows machine updated the other night and now I'm having weird terminal issues when I ssh to a remote host from a local WSL2 terminal. Plain old shell generally seems to work on the remote end, but the moment it needs to go to some form of full screen redraw interface (e.g. `less`, `top`, `vim`, etc.) the screen can't refresh anymore. In some cases, long output (e.g. `ps -AH u`) will cause it to stall output as well. Seems to work okay for local sessions though. The remote machines also work okay from a different Windows laptop's WSL that I have (for the moment since I haven't rebooted to apply the update yet), so it doesn't appear to be the remote end point that's the problem. It also works okay if I `ssh` from a Putty terminal emulator on my problematic workstation, so it appears to really be a problem with the terminal emulator on this machine. I have tried starting `bash` from - the various Windows Console programs terminal emulator (Win-R -> `bash`, `pwsh`, `cmd`) - the `powershell` terminal - the new "Windows Terminal" These all exhibit the same behavior. When the problem occurs I can enter the magic `~.~.` sequence to kill the ssh session and return to the host terminal session. At this point the cursor itself is gone (no longer a white block, underscore, etc.), though I can type again. Running `reset` in the local `bash` session recovers the local behavior without needing to restart the console window, but I still get the same issue once I try to ssh to a remote host again. # Expected behavior Free flowing characters over ssh :) # Actual behavior Characters stop flowing :( # Links Feedback hub report: https://aka.ms/AAbi4mw
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:30:39 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Attention Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#12982
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?