-
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/ERROR_SERVICE_DOES_NOT_EXIST #11882
Comments
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:
Diagnostic information
|
1 similar comment
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:
Diagnostic information
|
WslLogs-2024-08-05_16-35-22.zip does anyone know how to fix this issue |
The specified service does not exist as an installed service. |
I've looked at the similar issues. In particular, I've tried:
No success. The error message says that the service does not exist. As far as I know, the important service is "LxssManager". I have ensured that LxssManager is running (and has a startup type of "Automatic") in the Services control panel. Is there some other service I should check? It's possible my computer has a weird permissions setup that is causing trouble. (For example, as shown above, when I ran |
how can i solve my issue |
Inspired by this Super User dot com answer, I tried removing my It did not work. But for what it's worth here are the details: I renamed
to
(This folder was empty anyway.) I went to the Windows features control panel, unchecked "Windows Subsystem for Linux", and rebooted. I ran
I ran
It said:
I rebooted then ran I looked in the Services control panel and found that LxssManager was not running and its startup type was set to "Manual". I started it and ran Another weird permissions thing—when I tried to set LxssManager's startup type to "Automatic" I got "Access is denied", even when running the Services control panel as administrator. I was, however, able to change it by
For the record, this reinstall did not recreate the |
@arundelo: It looks like your installation is corrupted. Does manually installing the latest package solve the issue ? |
Thanks @OneBlue. Today I did the following:
It gave me a "Confirm Execution" dialog box which I said "Yes" to. Then the installer ran but it stopped with the error: "The older version of Windows Subsystem for Linux cannot be removed. Contact your technical support group." This is a work computer so I'm going to ask my company's helpdesk for help but I would like to keep this issue open for a little longer in case they have trouble solving the problem. |
Thank you @arundelo. Let's collect MSI logs to see what's causing this. Can you run:
As administrator, and share the resulting |
@OneBlue, here it is: |
Thank you @arundelo. This is the root cause of the error you're seeing:
It looks like the currently installed package is corrupted and can't be removed. One thing you can try is this: https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d to help remove the old package |
@OneBlue, for what it's worth, I'll try the troubleshooter at the link you gave, thanks. |
@OneBlue, I believe the troubleshooter worked! I told it I was trying to uninstall WSL, it said it fixed the problem, then I was able to reinstall WSL. A co-worker of mine pushed some security policy changes to my computer about the same time so it's also possible that had to do with it. Now when I run |
Windows Version
Microsoft Windows [Version 10.0.19045.4651]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
cmd
prompt as administrator.wsl --status
Expected Behavior
A display of the status of Windows Subsystem for Linux.
Actual Behavior
Sixty seconds pass, then this error is printed:
This also happens if I run it in a regular (non-administrator)
cmd
prompt and it happens with mostwsl
commands, for example:It does not happen with
wsl --help
(which prints a help message right away).Diagnostic Logs
I ran the
collect-wsl-logs.ps1
script in an admin PowerShell and ranwsl --status
(in an admincmd
window) whilecollect-wsl-logs.ps1
was running. It said:Here is that file:
WslLogs-2024-08-05_16-35-22.zip
The text was updated successfully, but these errors were encountered: