WSL not working after open Linux filesystem in windows 10 explorer

[MuMuuuu]

Windows Version

Microsoft Windows [Version 10.0.19045.3570]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Cannot open

Distro Version

Ubuntu 22.03 LTS

Other Software

Windows Explorer

Repro Steps

1. Click on the Linux list and click default WSL version Ubuntu (Cannot open in screenshot cause wsl no response)
   
2. After waiting a long time, restart the windows explorer.
3. WSL still can use now but cannot open a new session.
4. Try to wsl -l -v or wsl --shutdown still no response.
5. Terminate wslservice.exe not working neither.
   
6. Get-Service LxssManager | Restart-Service but still not working.

Expected Behavior

WSL should open a new session or just response which list distributions.

Actual Behavior

WSL hangs for a long time with no output.


Notice : wsl --help still working

Diagnostic Logs

WslLogs-2024-01-01_11-12-04.zip

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Open similar issues:

• WSL2: can't access linux file system from Windows Explorer (#4812), similarity score: 0.86
• Can't access wsl in File Explorer + Possible Fix (#9010), similarity score: 0.82

Closed similar issues:

• WSL2: can't access linux file system from windows (#4260), similarity score: 0.83
• Can't open WSL files directly from File Explorer (#5594), similarity score: 0.83
• WSL file system not available to any windows applications until after I start WSL Terminal (#8508), similarity score: 0.82

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

[MuMuuuu]

Sadly news : Reboot Windows didn't make it works appropriate.

[MuMuuuu]

Seems WSL is still running, press Ctrl+C got error code 3221225786.
Then run command wsl --update will fix it.
#9718

[OneBlue]

Thank you @MuMuuuu. Can you share a /dump of when WSL gets into this "stuck" state ?

[MuMuuuu]

Thank you @MuMuuuu. Can you share a /dump of when WSL gets into this "stuck" state ?

Hello, I think I had already provide a diagnostic log ?
WslLogs-2024-01-01_11-12-04.zip

[ghost]

/dump

[microsoft-github-policy-service]

Hello! Could you please provide logs and process dumps to help us better diagnose your issue?

To collect WSL logs and dumps, 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 -Dump

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

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

Click here for more info on logging

Thank you!

[microsoft-github-policy-service]

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!