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

> > > > _Tested on Windows 10 Pro._ #11300

Closed
Vinayak097 opened this issue Mar 14, 2024 · 4 comments
Closed

> > > > _Tested on Windows 10 Pro._ #11300

Vinayak097 opened this issue Mar 14, 2024 · 4 comments

Comments

@Vinayak097
Copy link

Uploading ws.PNG…
Uploading ws.PNG…

          > > > > _Tested on Windows 10 Pro._

@thehairy, ok, now try this:

  1. In a Command Prompt (%windir%\system32\cmd.exe) running as admin, run:
    netsh winsock reset
  2. Reboot the computer.
  3. Then, in a Command Prompt (%windir%\system32\cmd.exe) not running as admin, run the following. It will have some pop-up windows requiring your admin username and password during the install, but the Cmd Prompt should not be in admin mode:
    # Update your WSL system
    wsl --update
    
    # Install the latest version of Ubuntu
    wsl --install

This is the shorter and clearer version of what's already in my comment you quoted.
Does this work for you?

This worked for me, thanks a lot was stuck on this for a whole day

Thanks for your instruction. But I didn't get a pop-up windows requiring my local admin username and password during step 3 and still have the "Catastophic failure". Any ideas?

Is it possible you are already a local admin 🤔?

I am in the same situation as the person asking the question. I'm logged in to Windows with my work email that doesn't have Admin rights, but I have a local admin account which I can run admin tasks with. I am sure I am using my work email user account.

Originally posted by @guoran23 in #9420 (comment)

@Vinayak097
Copy link
Author

ws
solve this please

@benhillis
Copy link
Member

/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