The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

View similar issues

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!

Open similar issues:

• WSL Service becomes unresponsive some time after system startup (#11103), similarity score: 0.74
• Systemd not starting correctly on fresh install after reboot (#9207), similarity score: 0.71

Closed similar issues:

• WSL Service goes into manual mode after reboot (#11526), similarity score: 0.72
• LxssManager keeps shutting down and getting stuck in STOP_PENDING state (#10505), similarity score: 0.71
• WSL2 does not keep running since Version 0.60.0 (#8642), similarity score: 0.71

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

.wslconfig found
Detected appx version: 2.2.4.0
Found no WSL traces in the logs

from wsl.

I'm 99% sure I caught the problem with this log. IDK what a wsl trace is; however, I'm wondering if there would be one given that, on power-up, WSL Service is not running until there is a demand. If I quickly open a terminal, WSL Service will start running and there is no problem. The problem occurs if there is no demand within about a minute, at which time WSL Service changes to Disabled. So WSL never runs and cannot be made to run without changing the service back to manual or auto.

If I'm missing something, please let me know. Thx

from wsl.

Thank you for reporting this @SidJnsn66.

This is most likely caused by a third party program (there's no logic to ever disable wslservice), so this is most likely an antivirus / security solution.

Could you share the list of all running process & services right after boot ? That should help scope down where this is coming from.

from wsl.

That makes sense. Thanks for hanging with me to get closer to a solution. Here is the output of tasklist right after reboot and before WSL Service switches to Disabled.
As mentioned above, I have uninstalled Avast AV and, at one time or another, have turned off Defender, disabled Secure Health Service, turned of PIA (vpn client) and CCleaner, all with no effect.

list.txt

from wsl.

@SidJnsn66: I see a few processes that could potentially explain this service configuration change:

• CCleanerPerformanceOptimi
• MpDefenderCoreService
• MsMpEng
• CCleaner64

Could you try disabling those and see if that solves the issue ?

from wsl.

Seems the problem is solved before I got your last message. I decided to clean up the registry using CCleaner in case traces of Avast were left and problematic. Apparently something in that did the trick. WSL service was Automatic - Delayed Start when I next rebooted, and never returned to Disabled. WSL runs as expected.
FWIW, the four services you mentioned are still running.
Thank you for your help!!

from wsl.

Good to know, thank you !

from wsl.