specifying a directory on a mounted drive or a symbolic link to a directory on a mounted drive as the starting directory does not work #11219

Open
opened 2026-01-31 02:41:48 +00:00 by claunia · 0 comments
Owner

Originally created by @gkamendje on GitHub (Oct 30, 2020).

Environment

Windows build number:  19041.572
Windows Terminal version (if applicable): 1.2.2381.0

Any other software?

In the Windows Terminal Json file, specifying a directory on a mounted drive or a symbolic link to a directory on a mounted drive as the starting directory does not work at all.

Steps to reproduce

For example for me, the following works well.
"startingDirectory" : "//wsl$/Ubuntu/home/<User>/"
This works also
"startingDirectory" : "//wsl$/Ubuntu/home/<User>/a_sub_dir_of_my_home"

However, setting a directory on a mounted drive as the starting directory does not work.
"startingDirectory" : "//wsl$/Ubuntu/mnt/e/mydir_on_drive_e"
This does not work either
"startingDirectory" : "//wsl$/Ubuntu/home/<User>/<Symbolic_link_to_a_directory_located_on_one_of_the_mounted_drives>"

Expected behavior

WSL should open in the specified directory

Actual behavior

WSL opens into the default directory

Originally created by @gkamendje on GitHub (Oct 30, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: 19041.572 Windows Terminal version (if applicable): 1.2.2381.0 Any other software? ``` In the Windows Terminal Json file, specifying a directory on a mounted drive or a symbolic link to a directory on a mounted drive as the starting directory does not work at all. # Steps to reproduce For example for me, the following works well. `"startingDirectory" : "//wsl$/Ubuntu/home/<User>/"` This works also `"startingDirectory" : "//wsl$/Ubuntu/home/<User>/a_sub_dir_of_my_home"` However, setting a directory on a mounted drive as the starting directory does not work. `"startingDirectory" : "//wsl$/Ubuntu/mnt/e/mydir_on_drive_e"` This does not work either `"startingDirectory" : "//wsl$/Ubuntu/home/<User>/<Symbolic_link_to_a_directory_located_on_one_of_the_mounted_drives>"` # Expected behavior WSL should open in the specified directory # Actual behavior WSL opens into the default directory
claunia added the Resolution-Duplicate label 2026-01-31 02:41:48 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11219