wsl --set-default-version 2 The service cannot be started, either because it is disabled or because it has no enabled devices associated with it

user_14946095 0
Viewed 5896

I'm trying to install again Ubuntu on my Windows 10 Home Version 20H2 OS Build 19042.685 using WSL2.

The problem is the WSL2 installation is not finished. I received the following message doing Step 5 - Set WSL 2 as your default version

PS C:\WINDOWS\system32> wsl
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Previous steps done:

PS C:\WINDOWS\system32> dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19042.685

Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.
PS C:\WINDOWS\system32> dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19042.685

Enabling feature(s)
[==========================100.0%==========================]
The operation completed successfully.
PS C:\WINDOWS\system32>

Then I restarted Windows and

execute wsl_update_x64.msi
wsl-2 failed-installation
3 Answers

I had the same issue

C:\WINDOWS\system32> wsl --set-default-version 2
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

The problem was Kaspersky. The solution is simple Open cmd.exe and run the following code

sc config LxssManager start=auto

Kaspersky will give you a pop-up about a potential thread. Tell Kaspersky to ignore the alert. Please don't click on "Fix it" button for Kaspersky or you will undo the solution.

That should fix it

user_33534470

Docans is right; running:

sc config LxssManager start=auto

in Command Prompt seems to fix the issue. However, you must run Command Prompt as an Administrator. I don't have enough reputation to comment or edit the post to clarify this so I have to make it a separate answer.

user_97555250

PS: Windows Command shell needs to be open with Admin privileges (Run as administrator)

user_17495290
Related