[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

Error "Element not found" for wsl update #12085

Closed
1 of 2 tasks
Ornella452 opened this issue Sep 26, 2024 · 3 comments
Closed
1 of 2 tasks

Error "Element not found" for wsl update #12085

Ornella452 opened this issue Sep 26, 2024 · 3 comments
Labels
emailed-logs Logs have been emailed

Comments

@Ornella452
Copy link
Ornella452 commented Sep 26, 2024 •
edited
Loading

Windows Version

Microsoft Windows [version 10.0.22631.4249

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.10.102.1

Distro Version

Ubuntu

Other Software

Docker version 27.2.0

Repro Steps

Expected Behavior

I would like it to work with the message "WSL has been updated successfully."

Actual Behavior

When I run wsl --update with the cmder here is the error: Element not found.=======90.0%======================
image

I just installed docker, same error :

image

  • I tried to install "Windows Subsystem for Linux" but error Code : 0x80070490
    image

Diagnostic Logs

send by mail : wsl-gh-logs@microsoft.com
@github-actions GitHub Actions
Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How 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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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 wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Open similar issues:

Closed similar issues:

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

@Ornella452
Copy link
Author

/emailed-logs

@github-actions GitHub Actions
Copy link
Diagnostic information 
Found '/emailed-logs', adding tag 'emailed-logs'

@github-actions github-actions bot added the emailed-logs Logs have been emailed label Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
emailed-logs Logs have been emailed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Ornella452