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

WSL 2 kernel file is not found - Installing: Windows Subsystem for Linux - Catastrophic failure #11727

Closed
1 of 2 tasks
jbyrnescu opened this issue Jun 25, 2024 · 2 comments
Closed
1 of 2 tasks

Comments

@jbyrnescu
Copy link

Windows Version

Microsoft Windows [Version 10.0.19045.4529]

WSL Version

2.0.0.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

not running a kernel

Distro Version

No distro - wsl not running

Other Software

This problem started with installing podman.

Repro Steps

GAINWELL+jbyrne@GWT-94QB9K3 MINGW64 ~/git
$ podman machine inspect
[]
Error: podman-machine-default: VM does not exist

GAINWELL+jbyrne@GWT-94QB9K3 MINGW64 ~/git
$ podman machine init
Error: vm "podman-machine-default" already exists on hypervisor

GAINWELL+jbyrne@GWT-94QB9K3 MINGW64 ~/git
$ wsl --list --running
There are no running distributions.

GAINWELL+jbyrne@GWT-94QB9K3 MINGW64 ~/git
$ wsl --status
Default Distribution: podman-machine-default
Default Version: 2

WSL automatic updates are on.

The WSL 2 kernel file is not found. To update or restore the kernel please run 'wsl --update'.

GAINWELL+jbyrne@GWT-94QB9K3 MINGW64 ~/git
$ wsl --update
Installing: Windows Subsystem for Linux
Catastrophic failure

Expected Behavior

wsl --update should install wsl because it's having problems. I've turned on and off the software in the control panel and rebooted with these settings however this has not seemed to help.

Actual Behavior

See error output of commands above.

Diagnostic Logs

No response

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 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 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.

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

1 participant