Skip to content
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

Allow installation of WSL distros, via Microsoft Store, to other (non-system) drives. #6597

Closed
mingp opened this issue Mar 1, 2021 · 2 comments

Comments

@mingp
Copy link

mingp commented Mar 1, 2021

Is your feature request related to a problem? Please describe.

My desktop contains a smaller SSD, mounted as "C:", and a larger HDD, mounted as "D:". Windows 10 is installed on "C:", and "C:" is my system drive. I generally prefer to install most things to "D:", in order to conserve space on "C:", because "C:" is a very small SSD, and was already over half full from the factory after installation of the OS and OEM bundled applications (another issue entirely).

I tried to install WSL Ubuntu 20.02 to "D:". I got a notification that it must be installed to a system drive, and it only allowed me to select "C:". Attempting to move the application to "D:", I got a similar notification that it cannot be moved. Despite my "Change where new content is saved" setting set to "D:", this particular application seems not to follow it.

Describe the solution you'd like

Allow for the WSL distros, via the official Microsoft Store installation route, to be installed to non-system drives.

I found an issue report to a different and unrelated project, where they claim that this is a configuration on the application in the Microsoft Store. If so, could this be reconfigured, please?

Describe alternatives you've considered

It looks like there exist unofficial manual installation instructions that would allow moving the application to another drive. I haven't tested these yet and cannot confirm if they work or not. If they do work, though, that seems like it should be officially supported, rather than requiring a workaround.

Additional context

N/A.

@mingp mingp added the feature label Mar 1, 2021
@therealkenc
Copy link
Collaborator

/dupe #449

@ghost
Copy link

ghost commented Mar 2, 2021

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

@ghost ghost closed this as completed Mar 2, 2021
@ghost ghost added the duplicate label Mar 2, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants