WSL icon indicating copy to clipboard operation
WSL copied to clipboard

Probably a solution for WSL not working on Canary Insider Release

Open Annlix opened this issue 7 months ago • 1 comments

If you upgrade to the latest Canary Insider Release, you may encounter the issue of WSL not working :(

Specifically, it could be that Docker can't start, or can't install the wsl distribution (when you attempt to install a distribution, you will spend a lot of time during the install stage and then failed, the error code maybe HCS_E_SERVICE_NOT_AVAILABLE or something similar).

Maybe you can try turn off the Hyper-V feature on appwiz.cpl, like this:

Image

I tried that on 27818 and start my wsl successfully.

Annlix avatar Jun 13 '25 18:06 Annlix

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

github-actions[bot] avatar Jun 13 '25 18:06 github-actions[bot]

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-file it as a new issue.

Thank you!