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

WSL tmux screen scrambled by launching powershell.exe #227

New Issue
Closed
opened 2026-01-30 21:46:15 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 21:46:15 +00:00
Owner
Copy Link

Originally created by @agowa on GitHub (Apr 14, 2018).

Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.16299.371]

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

  • Open Cmd
  • bash
  • apt-get update
  • apt-get install tmux
  • tmux
  • [CTRL] + [B]
  • [Shift] + [5]
  • powershell.exe
  • Clear-Host
    Now the screen separation is gone, but if you press [STRG] + [B]; [Arrow Left] it still switches to the console on the left, but the screen is garbage. But if you only use linux applications (those inside wsl) it works fine.

The thing actually gets worse if the hosting shell is powershell, e. g. you used powershell.exe to run the bash command. Then also normal linux applications inside wsl destroy the screen separation.

What's wrong / what should be happening instead:

The screen layout should not get destroyed when launching applications.
Also cmd.exe and powershell should have the same behavior after executing the bash command e. g. switching into wsl.

Originally created by @agowa on GitHub (Apr 14, 2018). ### Your Windows build number: (Type `ver` at a Windows Command Prompt) Microsoft Windows [Version 10.0.16299.371] ### What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) * Open Cmd * `bash` * `apt-get update` * `apt-get install tmux` * `tmux` * [CTRL] + [B] * [Shift] + [5] * `powershell.exe` * `Clear-Host` Now the screen separation is gone, but if you press [STRG] + [B]; [Arrow Left] it still switches to the console on the left, but the screen is garbage. But if you only use linux applications (those inside wsl) it works fine. The thing actually gets worse if the hosting shell is powershell, e. g. you used powershell.exe to run the bash command. Then also normal linux applications inside wsl destroy the screen separation. ### What's wrong / what should be happening instead: The screen layout should not get destroyed when launching applications. Also cmd.exe and powershell should have the same behavior after executing the bash command e. g. switching into wsl.
claunia added the Resolution-Fix-AvailableProduct-WSL labels 2026-01-30 21:46:15 +00:00
claunia commented 2026-01-30 21:46:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 16, 2018):

Running Windows executables in WSL is really buggy before 17617. Everything you described was due to how interop was first implemented, however, on newer Insider's builds this should already be fixed!
image

@zadjii-msft commented on GitHub (Apr 16, 2018): Running Windows executables in WSL is really buggy before 17617. Everything you described was due to how interop was first implemented, however, on newer Insider's builds this should already be fixed! ![image](https://user-images.githubusercontent.com/18356694/38822573-b6d1a968-4158-11e8-9b60-9a9b2ede970c.png)
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 Product-WSL Resolution-Fix-Available
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#227
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?