-
Notifications
You must be signed in to change notification settings - Fork 847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to add mount for Development Drive attached as Junction #11706
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done. Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
|
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue. Thank you! |
Windows Version
Microsoft Windows [Version 10.0.22631.3737]
WSL Version
2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-2
Distro Version
Ubuntu-24.04
Other Software
No response
Repro Steps
A lot of existing tooling expects source to be in a certain folder. To benefit from the Dev Drive feature, I create an additional mount in the old, expected folder in
c:\
p:
)c:\projects
cd
into a directory inc:\projects
wsl
Expected Behavior
WSL starts in folder
/mnt/c/projects/
folderActual Behavior
<3>WSL (9499) ERROR: CreateProcessEntryCommon:496: chdir(/mnt/c/Projects) failed 5
and I'm
~
Note: when under
p:\
WSL correctly starts in/mnt/p/...
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: