I Can't Launch my WSL2 anymore

[SJoJoK]

Windows Build Number

Microsoft Windows [Version 10.0.21390.1]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.10.16

Distro Version

Ubuntu-20.04

Other Software

No response

Repro Steps

I just reboot my computer and then cant use anything about my WSL2
It takes longer time on connecting when i use VSCode than yesterday, so i realize there must be some problem
Then i launch my windows terminal, but this happens

The Chinese Text means
"No response from the virtual machine or container was received, and the operation timed out."
"Progress exited, Code is 4294967295"
Then I want to access my file in the WIndows File Explorer, but it just loading...with a ERROR as last
"Try to access invalid address"
Well.. After many times of reboot and relaunch the WSL service, it just keep wrong

Expected Behavior

I WANT TO RE-CONNECT TO MY WSL.

Actual Behavior

cant launch it

Diagnostic Logs

No response

[SJoJoK]

Well...A weird solution is that I install Ubuntu-18.04 in MS store, it installed correctly, and then my 20.04 just works well.
Now all my files back, but i think the bug still exists

[jaocarli]

@SJoJoK Just install and configure 18.04 for the first time?

[SJoJoK]

@SJoJoK Just install and configure 18.04 for the first time?

@fl4m3x Yes, install it from MS Store, after setting the username and password, i found that 20.04 can be launched

[DeletorDev]

Same issue for me, but when I was trying to navigate to /mnt/c the message error was "Input/Output Error"

Helped me below solution commented in issue #4122

powershell -> wsl --shutdown
powershell -> wsl

[therealkenc]

"No response from the virtual machine or container was received, and the operation timed out."

Please collect WSL logs and post the backlink to the feedback item here. Ref #6627.

[SJoJoK]

Same issue for me, but when I was trying to navigate to /mnt/c the message error was "Input/Output Error"

Helped me below solution commented in issue #4122

powershell -> wsl --shutdown
powershell -> wsl

Shutdown wasnt work for me.. but thanks

[SJoJoK]

"No response from the virtual machine or container was received, and the operation timed out."

Please collect WSL logs and post the backlink to the feedback item here. Ref #6627.

@therealkenc To recreate my problem I need to shutdown (press the button to power off) my computer , idk whether the capturing keeps working or not during recreating the bug ... sorry for that

[SJoJoK]

I may find the cause of this bug: Ever time after a Force Shutdown(press the button to power off), the WSL goes wrong. However, normally shut down the computer from Window Start Menu doesnt lead to the bug. Maybe the Force Shutdown broke some files that WSL needed.

[therealkenc]

idk whether the capturing keeps working or not during recreating the bug

Your reproduction step was:

Then i launch my windows terminal, but this happens

When following the collect logs instructions, start recording prior to "then I launch my windows terminal".

[SJoJoK]

idk whether the capturing keeps working or not during recreating the bug

Your reproduction step was:

Then i launch my windows terminal, but this happens

When following the collect logs instructions, start recording prior to "then I launch my windows terminal".

Got it. Because the failure happens when i force the computer to shut down (and after some searching i found that this may be harm to my SSD), so i will collect the log next time when i must force it shut down. Thank you.

[therealkenc]

so i will collect the log next time when i must force it shut down

Please open a new issue if/when the problem manifests again.