You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cannot get WSL information through wsl -l -v command in the terminal, it is always in a stalling state, I confirm that there is WSL in my process.
Expected Behavior
WSL information should be displayed correctly:
Actual Behavior
The instruction to execute the WSL is always in a blocking state, with no return and no stop.
In fact, this is the second time I've had this problem, before I fixed it by resetting the network, which did solve my problem, but it happened again today.
Diagnostic Logs
'Virtual Machine' failed to restore. (Virtual machine ID BDE5013F-116B-4654-A625-CA75D2A590B5)
'Virtual Machine' Virtual SMB Device (Instance ID FEA6E63B-45DA-4E32-8B3D-1873B2CE50E7): Failed to restore with Error 'Cannot restore this virtual machine because a file read from the vSMB saved state data could not be found. Delete the saved state data and then try to start the virtual machine. ' (0xC0370400). (Virtual machine ID BDE5013F-116B-4654-A625-CA75D2A590B5)
The text was updated successfully, but these errors were encountered:
Looks like something probably crashed when you tried to install the first time. I suggest doing wsl.exe --unregister <distro> and re-trying (with tracing enabled).
Version
Microsoft Windows [Version 10.0.22000.978]
WSL Version
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
I cannot get WSL information through
wsl -l -v
command in the terminal, it is always in a stalling state, I confirm that there is WSL in my process.Expected Behavior
WSL information should be displayed correctly:
Actual Behavior
The instruction to execute the WSL is always in a blocking state, with no return and no stop.
In fact, this is the second time I've had this problem, before I fixed it by resetting the network, which did solve my problem, but it happened again today.
Diagnostic Logs
The text was updated successfully, but these errors were encountered: