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
wsl --unmount
cannot unmount paths with whitespaces
#11451
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! Closed similar issues:
|
wsl --unmount
wsl --unmount
cannot unmount paths with whitespaces
/emailed-logs |
Diagnostic information
|
What's noticeable is that mount works, no complain because of space in the path:
|
Windows Version
Microsoft Windows [Version 10.0.22621.3155]
WSL Version
2.1.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-2
Distro Version
No response
Other Software
No response
Repro Steps
Invoke
wsl --unmount <PATH>
where PATH is the path to a vhdx file with one or more spaces.It does not mattter if: a) the path exists or not b) the vhdx file is mounted or not in wsl
Expected Behavior
Let's focus on the simplest case - the case where the vhdx file does not even exist.
Expected:
Actual Behavior
(On Powershell 7.4.1)
Actual:
Note that I am focusing on the case of a disk that does not exist because it is the simplest to reproduce.
The real impact of this bug is that disks that have a space in their path or name cannot be unmounted. On the contrary,
wsl --mount --vhd
works as expected on paths with spaces.Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: