Support launching wsl.exe with a mapped network drive as the current directory.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Windows Version
Microsoft Windows [Version 10.0.22621.2134]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
- WSL 2
- WSL 1
Kernel Version
5.15.90.1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
- map a network drive to Windows Explorer
- ensure to mount the drive automatically on startup
- Reboot system
- Open any folder on your network drive
- right click on empty space
- open the terminal from the options
- Type
wsland hit enter.
Expected Behavior
wsl will launch, and the current directory will be the folder in the network drive.
Actual Behavior
wsl lanches
Error is shown:
<3>WSL (358) ERROR: CreateProcessParseCommon:789: Failed to translate _\path in network drive\_
the current working directory is the default home folder ~
Diagnostic Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior with wsl.exe from a folder on a mapped network drive, using the listed Windows, WSL, kernel, and Ubuntu versions as context. Trace the path associated with the CreateProcessParseCommon error and compare it with launching from a local drive. Done means wsl.exe starts without the translation error and preserves the network-drive folder as the current directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100