Error code: Wsl/0x80070422 Immediately after 1024-10 latest Windows Update

[EricBLivingston]

Windows Version

Microsoft Windows [Version 10.0.22631.4317]

WSL Version

WSL version: 2.3.24.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Kernel version: 5.15.153.1-2

Distro Version

Can't start it

Other Software

No response

Repro Steps

Any wsl command besides --version generates this error. I can't unregister, install, or do anything else with it.

I've tried sc config LxssManager start=auto and ensuring it's running
I've also ensured vmcompute is set to auto and is running

The only hint I have is that I noticed that after a reboot or two LxssManager has been reset to Manual and was off again. It seems something in the update is resetting that - perhaps it's part of the issue.

Expected Behavior

wsl should run. I had been running it for months and changed nothing except applied the latest update.

Actual Behavior

(base) 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.
Error code: Wsl/0x80070422

Diagnostic Logs

WslLogs-2024-10-09_06-46-06.zip

[github-actions]

The logs show that wslservice is disabled. Try to run (elevated command prompt): sc.exe config wslservice start= demand and see if that solves the issue

Diagnostic information

Detected appx version: 2.3.24.0
Detected user visible error: Wsl/0x80070422

[EricBLivingston]

That command did work, and I was able to run wsl afterwards. However, when I rebooted, the WSL Service had returned to Disabled again. Something appears to be re-disabling the service each reboot.

[Hotziplotzi]

I have a similar issue now on Windows 11 Pro, Build 26100.3194.
WSL-Version: 2.4.10.0
It seem that recently a Windows update changed the setup.
Most posts I read on similar issues talk about a Windows service "LxssManager" but that exists no more. Now there is this service called "C:\Program Files\WSL\wslservice.exe"
And this one also turns itself to "disabled" every single time I reboot my PC.
The temporary workaround is to set it to "automatic" and the manually start it, but after next boot it is turned to disabled again.

This here describes the same:
https://superuser.com/questions/1725594/windows-lxssmanager-is-missing-from-services-msc

I have both Ubuntu from MS Store installed and Docker Desktop. Both rely on the WSL service running.

Any ideas on how to make the service automatically start?

[EricBLivingston]

I've been having exactly the same issue. I notice when I boot up that the service is initially set to automatic and starts up successfully - I can even open a WSL console if I'm quick enough. Then, at some point during the start-up sequence, *something* shuts it down and disables is: if I have a wsl console open, it just closes by itself. Then I have to go in, reset it to automatic once more and manually restart it. Major pain. I can't work out what is shutting WSL down during every startup!

…

On Thu, Feb 13, 2025 at 11:40 AM Mr. Hotz van der Plotz < ***@***.***> wrote: I have a similar issue now on Windows 11 Pro, Build 26100.3194. It seem that recently a Windows update changed the setup. Most posts I read on similar issues talk about a Windows service "LxssManager" but that exists no more. Now there is this service called "C:\Program Files\WSL\wslservice.exe" And this one also turns itself to "disabled" every single time I reboot my PC. The temporary workaround is to set it to "automatic" and the manually start it, but after next boot it is turned to disabled again. I have both Ubuntu from MS Store installed and Docker Desktop. Both rely on the WSL service running. Any ideas on how to make the service automatically start? — Reply to this email directly, view it on GitHub <#12146 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDUGN4ZKQUT7R3FUEGJOGD2PTDHDAVCNFSM6AAAAABPUHSJUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGE3DOMJQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: Hotziplotzi]*Hotziplotzi* left a comment (microsoft/WSL#12146) <#12146 (comment)> I have a similar issue now on Windows 11 Pro, Build 26100.3194. It seem that recently a Windows update changed the setup. Most posts I read on similar issues talk about a Windows service "LxssManager" but that exists no more. Now there is this service called "C:\Program Files\WSL\wslservice.exe" And this one also turns itself to "disabled" every single time I reboot my PC. The temporary workaround is to set it to "automatic" and the manually start it, but after next boot it is turned to disabled again. I have both Ubuntu from MS Store installed and Docker Desktop. Both rely on the WSL service running. Any ideas on how to make the service automatically start? — Reply to this email directly, view it on GitHub <#12146 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEDUGN4ZKQUT7R3FUEGJOGD2PTDHDAVCNFSM6AAAAABPUHSJUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJXGE3DOMJQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Hotziplotzi]

Ok, with a lot more searching and trying I found this one:
#11628 (comment)
and it actually did solve my issue as well.

So the problem cause is Avast One, specifically the Avast One service "Avast Cleanup" ("C:\Program Files\Avast Software\Cleanup\TuneupSvc.exe").

Once I disable (set to just "manual" is not enough) this crap Avast service, the WSL service keeps autostarting and running.
The cleanup service also doesnt seem to be any crucial protection service but only related to "system tuning" which is less than important.

Just for reference I found the following related issues:
#7746
#11582
#11628