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

KEEP HAVING TROUBLE GETTING Ubuntu WSL to work #11299

Closed
mk-g1 opened this issue Mar 13, 2024 · 4 comments
Closed

KEEP HAVING TROUBLE GETTING Ubuntu WSL to work #11299

mk-g1 opened this issue Mar 13, 2024 · 4 comments

Comments

@mk-g1
Copy link

mk-g1 commented Mar 13, 2024

Can someone help me with this, I have everything default to my windows drive C:/, I've tried multiple ways to install Ubuntu 22.04 or 20.04 LTS and it keeps giving me erros. From the Microsft Store it says "Unavailable" from CMD I am able to run "wsl --install -d Ubuntu-22.04" but then I get this error:
The system cannot find the file specified.
Please create a default UNIX user account. The username does not need to match your Windows username.
For more information visit: https://aka.ms/wslusers
Enter new UNIX username:

I enter any name it says:

"The system cannot find the file specified."

Also when I try "wsl --update" it says the following error

Installing: Windows Subsystem for Linux
The deployment operation was blocked due to a per-package-family policy restricting deployments on a non-system volume. Per policy, this app must be installed to the system drive, but that's not set as the default. In Storage Settings, make the system drive the default location to save new content, then retry the install.

Like I said my stem is set to everything on C:/ which is my default Windows Disk. Can you please help thanks

Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please 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. Thank you!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@OneBlue
Copy link
Collaborator

OneBlue commented Mar 13, 2024

/logs

Copy link
Contributor

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

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

If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue.

Thank you!

Copy link
Contributor

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!

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