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

WSL cannot start from anywhere besides ~ #23502

New Issue
Open
opened 2026-01-31 08:44:06 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:44:06 +00:00
Owner
Copy Link

Originally created by @JamesRickards-Canada on GitHub (Aug 6, 2025).

Windows Terminal version

1.22.12111.0

Windows build number

10.0.26100.4652

Other Software

WSL 1

Steps to reproduce

In Windows terminal, go to settings, change the Ubuntu starting directory to be anywhere besides ~ (e.g. "C:\Users"), save.
Open a new Ubuntu tab (or, set the default profile to Ubuntu, go to C:\Users in Windows Terminal, right click, open in Terminal)

Expected Behavior

You open WSL in "C:\Users", i.e. /mnt/c/Users

Actual Behavior

You open WSL in ~

Under settings, I noticed that "Command line" was set to:
"C:\Windows\system32\wsl.exe --distribution-id {fc5a03e5-b632-4340-8975-048f8e6f47ee} --cd ~"

This was the default setting when it was installed. Deleting the "--cd ~" fixed my issue. I don't know why the "--cd ~" was the default behaviour, as it makes the starting directory choice useless. In an older version of WSL on a different laptop the "cd ~" was not included in the command line.

Originally created by @JamesRickards-Canada on GitHub (Aug 6, 2025). ### Windows Terminal version 1.22.12111.0 ### Windows build number 10.0.26100.4652 ### Other Software WSL 1 ### Steps to reproduce In Windows terminal, go to settings, change the Ubuntu starting directory to be anywhere besides ~ (e.g. "C:\Users"), save. Open a new Ubuntu tab (or, set the default profile to Ubuntu, go to C:\Users in Windows Terminal, right click, open in Terminal) ### Expected Behavior You open WSL in "C:\Users", i.e. /mnt/c/Users ### Actual Behavior You open WSL in ~ Under settings, I noticed that "Command line" was set to: "C:\Windows\system32\wsl.exe --distribution-id {fc5a03e5-b632-4340-8975-048f8e6f47ee} --cd ~" This was the default setting when it was installed. Deleting the "--cd ~" fixed my issue. I don't know why the "--cd ~" was the default behaviour, as it makes the starting directory choice useless. In an older version of WSL on a different laptop the "cd ~" was not included in the command line.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:44:06 +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 Issue-Bug 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#23502
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?