-
Notifications
You must be signed in to change notification settings - Fork 838
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
Cannot start WSL, error Wsl/0x8007041d #10910
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:
|
/logs |
Sorry, I should've done it before. |
Thank you @Dr-Pe. Looking at the logs it looks like something is going wrong during an upgrade. Can you try to run as administrator:
And share the content of the C:\wsl-upgrade.txt file ? |
The first one returns success, but when I run |
Interesting. Can you capture /logs when that happens ? This is not expected |
|
Interesting, it looks like the installer service is crashing but I'm not seeing any logs from it. Can you try to follow [11) Reporting a WSL process crash While you're collecting crash dumps, can you also try to run (elevated cmd.exe):
and see if that generates a crash ? |
Running |
Thank you ! Sadly our script isn't up to date and doesn't automatically dump wslinstaller.exe. Can you follow these instructions and share a dump of |
|
Thank you. In the dump I can see that wslinstaller.exe is behaving normally so something else must be causing this. We probably need COM logs. I'll get back to you on how to collect them. |
Actually having a deeper look, it looks like the service might be stuck exiting. Do you have any wsl.exe processes running that could be talking to wslinstaller ? |
Firstly, there wasn't any wsl.exe process running. Then I ran |
Does manually installing the MSI package solve the issue ? |
Now I get the same error I was getting at the beginning (Error code: Wsl/0x8007041d). |
Hmm this is very surprising. Let's try something else: What if you completely uninstall and then only install the above MSI package ? |
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
Microsoft Windows [Versión 10.0.19045.3803]
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
No response
Other Software
No response
Repro Steps
Try to execute any wsl command, such as
wsl -l
,wsl --install
, etc.I tried to reinstall everything so now I don't have any distribution installed either because
wsl --install
doesn't work.Expected Behavior
It depends on the command (i.e.: install default distribution when the input is
wsl --install
).Actual Behavior
The terminal prints "El servicio no respondió a tiempo a la solicitud de inicio o de control. Error code: Wsl/0x8007041d".
I think the english version would say "The service did not respond to the start or control request in a timely fashion" or something like that.
Diagnostic Logs
WslLogs-2023-12-14_15-27-27.zip
The text was updated successfully, but these errors were encountered: