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

Cannot start WSL, error Wsl/0x8007041d #10910

Closed
1 of 2 tasks
Dr-Pe opened this issue Dec 13, 2023 · 18 comments
Closed
1 of 2 tasks

Cannot start WSL, error Wsl/0x8007041d #10910

Dr-Pe opened this issue Dec 13, 2023 · 18 comments

Comments

@Dr-Pe
Copy link

Dr-Pe commented Dec 13, 2023

Windows Version

Microsoft Windows [Versión 10.0.19045.3803]

WSL Version

2.0.14.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

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

Copy link

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:

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

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 13, 2023

/logs

@Dr-Pe
Copy link
Author

Dr-Pe commented Dec 14, 2023

Sorry, I should've done it before.
Done!

WslLogs-2023-12-14_15-27-27.zip

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 15, 2023

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:

  • reg.exe add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss\MSI /t REG_SZ /v UpgradeLogFile /d C:\wsl-upgrade.txt /f
  • wsl.exe echo test

And share the content of the C:\wsl-upgrade.txt file ?

@Dr-Pe
Copy link
Author

Dr-Pe commented Dec 15, 2023

The first one returns success, but when I run wsl.exe echo test it gives me "server execution failed" (Error code: Wsl/CallMsi/0x80080005) and no .txt file is created.

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 15, 2023

The first one returns success, but when I run wsl.exe echo test it gives me "server execution failed" (Error code: Wsl/CallMsi/0x80080005) and no .txt file is created.

Interesting. Can you capture /logs when that happens ? This is not expected

@Dr-Pe
Copy link
Author

Dr-Pe commented Dec 15, 2023

The first one returns success, but when I run wsl.exe echo test it gives me "server execution failed" (Error code: Wsl/CallMsi/0x80080005) and no .txt file is created.

Interesting. Can you capture /logs when that happens ? This is not expected

Ok:
WslLogs-2023-12-14_23-35-36.zip

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 15, 2023

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
]https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#11-reporting-a-wsl-process-crash) and see if any crash dump is generate ?

While you're collecting crash dumps, can you also try to run (elevated cmd.exe):

sc.exe start wslinstaller

and see if that generates a crash ?

@Dr-Pe
Copy link
Author

Dr-Pe commented Dec 15, 2023

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 ]https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#11-reporting-a-wsl-process-crash) and see if any crash dump is generate ?

While you're collecting crash dumps, can you also try to run (elevated cmd.exe):

sc.exe start wslinstaller

and see if that generates a crash ?

Running sc.exe start wslinstaller returns "an instance of this service is already running" (error 1056) and these logs:
WslLogs-2023-12-15_19-09-55.zip

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 15, 2023

Running sc.exe start wslinstaller returns "an instance of this service is already running" (error 1056) and these logs: WslLogs-2023-12-15_19-09-55.zip

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 wslinstaller.exe ?

@Dr-Pe
Copy link
Author

Dr-Pe commented Dec 15, 2023

Running sc.exe start wslinstaller returns "an instance of this service is already running" (error 1056) and these logs: WslLogs-2023-12-15_19-09-55.zip

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 wslinstaller.exe ?

wslinstaller.zip

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 15, 2023

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.

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 15, 2023

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 ?

@Dr-Pe
Copy link
Author

Dr-Pe commented Dec 16, 2023

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 wsl on the command prompt and two wsl.exe processes spawned but exited with "update failed" (exit code: 1603, error code: Wsl/CallMsi/E_ABORT). Now there's not wsl or wslinstaller process running.

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 19, 2023

Firstly, there wasn't any wsl.exe process running. Then I ran wsl on the command prompt and two wsl.exe processes spawned but exited with "update failed" (exit code: 1603, error code: Wsl/CallMsi/E_ABORT). Now there's not wsl or wslinstaller process running.

Does manually installing the MSI package solve the issue ?

@Dr-Pe
Copy link
Author

Dr-Pe commented Dec 22, 2023

Firstly, there wasn't any wsl.exe process running. Then I ran wsl on the command prompt and two wsl.exe processes spawned but exited with "update failed" (exit code: 1603, error code: Wsl/CallMsi/E_ABORT). Now there's not wsl or wslinstaller process running.

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).
Here are the dumps:
WslLogs-2023-12-22_18-27-48.zip

@OneBlue
Copy link
Collaborator

OneBlue commented Jan 3, 2024

Now I get the same error I was getting at the beginning (Error code: Wsl/0x8007041d). Here are the dumps: WslLogs-2023-12-22_18-27-48.zip

Hmm this is very surprising. Let's try something else: What if you completely uninstall and then only install the above MSI package ?

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

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

2 participants