-
Notifications
You must be signed in to change notification settings - Fork 816
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
WslRegisterDistribution failed with error: 0x80070424 #10772
Comments
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:
You can give me feedback by thumbs upping or thumbs downing this comment. |
Try this #10764 (comment) |
I'm getting this error AFTER applying the fix from the comment above. |
/logs |
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:
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 Thank you! |
I have the same error running this version of WSL. Everything worked and suddenly, probably after updating wsl in the background, WSL does not start anymore and it appears the WSL distribution is gone. |
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-open it. Thank you! |
Windows Version
10.0.22631.2715
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Ubuntu 22.04.0 LTS
Other Software
No response
Repro Steps
Expected Behavior
ubuntu start success
Actual Behavior
ubuntu system start failed error:0x80070424
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: