-
Notifications
You must be signed in to change notification settings - Fork 822
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 No Longer Boots #12113
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 View similar issuesPlease 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:
|
/emailed-logs |
Diagnostic information
|
@Mythra do you have Run |
Hi, I thought I had uninstalled it since I saw it cropping up issues, it appears I hadn't actually. I've now uninstalled it, and confirmed it did get uninstalled with the command you gave:
And alas the error does still remain:
|
Thank you @Mythra. The logs show that the Virtual Machine Platform component it not enabled on your machine. You can try to run: |
Hello @OneBlue , Unfortunately it seems no dice, same error, I ran:
Rebooted, and ran:
Seems like it's still the same error :( |
Oh I see. This is probably because we aren't correctly detecting that VMP is missing. Can you try to enable the "Virtual Machine Platform" optional component ? |
Looks like that solved it, thanks! Weird that it just happened randomly, but hey I'm glad it's fixed. Appreciate your help! |
Windows Version
Microsoft Windows [Version 10.0.22631.4169]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
Ubuntu 24.04
Other Software
No response
Repro Steps
Attempt to run
wsl
, or launch a wsl instance through WSL terminal.Expected Behavior
I should be able to access the WSL instances I was able to access before a reboot.
Actual Behavior
or
Diagnostic Logs
(Will email to forward as is mentioned in docs)
The text was updated successfully, but these errors were encountered: