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

Autodetected WSL profiles do not appear if Terminal opened too soon after login #12586

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

Originally created by @cerebrate on GitHub (Feb 15, 2021).

Environment

Windows build number: 10.0.21313.0
Windows Terminal version (if applicable): 1.6.10412.0 or earlier

Any other software?

WSL, any distribution(s) installed

Steps to reproduce

  1. Log on to Windows.
  2. Immediately open Windows Terminal.
  3. Observe that the WSL distributions are not listed on the '+' drop-down menu.
  4. Close Terminal and wait for a short time.
  5. Reopen Terminal.
  6. Observe that the WSL distributions are now properly listed.

It may be necessary for the machine to be heavily loaded on logon to trigger the issue.

Expected behavior

The WSL distributions installed on the machine/listed in the profile to be displayed always.

Actual behavior

WSL distributions installed on the machine, even those whose profile has been customized in the Terminal settings, do not appear in the '+' drop-down menu until the machine has passed a certain stage of the logon process. While this can be worked around by opening Settings and making a null edit, or by closing and reopening Terminal, it does effectively render the "Launch on machine startup" setting useless for its intended purpose.

Originally created by @cerebrate on GitHub (Feb 15, 2021). # Environment ```none Windows build number: 10.0.21313.0 Windows Terminal version (if applicable): 1.6.10412.0 or earlier Any other software? WSL, any distribution(s) installed ``` # Steps to reproduce 1. Log on to Windows. 2. _Immediately_ open Windows Terminal. 3. Observe that the WSL distributions are not listed on the '+' drop-down menu. 4. Close Terminal and wait for a short time. 5. Reopen Terminal. 6. Observe that the WSL distributions are now properly listed. It may be necessary for the machine to be heavily loaded on logon to trigger the issue. # Expected behavior The WSL distributions installed on the machine/listed in the profile to be displayed always. # Actual behavior WSL distributions installed on the machine, even those whose profile has been customized in the Terminal settings, do not appear in the '+' drop-down menu until the machine has passed a certain stage of the logon process. While this can be worked around by opening Settings and making a null edit, or by closing and reopening Terminal, it does effectively render the "Launch on machine startup" setting useless for its intended purpose.
claunia added the Resolution-Duplicate label 2026-01-31 03:19:34 +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 Resolution-Duplicate
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#12586
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?