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

Windows terminal as default terminal application breaks WSL2 launch when WSL2 debugConsole is enabled #13916

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

Originally created by @reynoldskr on GitHub (May 26, 2021).

Originally assigned to: @miniksa on GitHub.

Windows Terminal version (or Windows build number)

1.9.1445.0

Other Software

  1. WSL2
  2. Windows 10 build 21387 or later, for the WSL2 debugConsole functionality

Steps to reproduce

  1. Install WSL2 + a distro and create the %USERPROFILE%\.wslconfig file with the following contents:
[wsl2]
debugConsole=true
  1. Make sure that Terminal v1.9.1445.0 is installed, and that it's a) set as the default terminal b) has a profile for your WSL2 distro
  2. Attempt to launch terminal in the WSL2 profile, either via the jump list or terminal's own profile menu

Expected Behavior

  1. WSL2 profile opens normally

Actual Behavior

  1. Windows terminal locks up and goes into a "not responding" state, with high system CPU usage from VM compute service
  2. After the windows terminal process is killed, a legacy console window spawns with the expected WSL2 VM debug output
  3. After the VM boots, another Windows terminal spawns without any tabs open, lacking any WSL profile, and doesn't respond to window close events
  4. When the terminal instance from 3 is killed, and another one is spawned, this one will work normally
Originally created by @reynoldskr on GitHub (May 26, 2021). Originally assigned to: @miniksa on GitHub. ### Windows Terminal version (or Windows build number) 1.9.1445.0 ### Other Software 1. WSL2 2. Windows 10 build 21387 or later, for the WSL2 `debugConsole` functionality ### Steps to reproduce 1. Install WSL2 + a distro and create the `%USERPROFILE%\.wslconfig` file with the following contents: ``` [wsl2] debugConsole=true ``` 2. Make sure that Terminal v1.9.1445.0 is installed, and that it's a) set as the default terminal b) has a profile for your WSL2 distro 3. Attempt to launch terminal in the WSL2 profile, either via the jump list or terminal's own profile menu ### Expected Behavior 1. WSL2 profile opens normally ### Actual Behavior 1. Windows terminal locks up and goes into a "not responding" state, with high system CPU usage from VM compute service 2. After the windows terminal process is killed, a legacy console window spawns with the expected WSL2 VM debug output 3. After the VM boots, another Windows terminal spawns without any tabs open, lacking any WSL profile, and doesn't respond to window close events 4. When the terminal instance from 3 is killed, and another one is spawned, this one will work normally
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 Area-DefApp Issue-Bug Priority-1 Product-Terminal Resolution-Fix-Committed
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#13916
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?