Closed abun880007 closed 3 years ago
Hello!
That's because you have to first disable the Linux sub-environment, reboot, then re-enable it and it works again.
This is because they have changed the implementation.
On my "old" Windows 10 they wouldn't load either, I did that, disabled the feature, rebooted, enabled it and 100% functional agian.
Nope, it's a bug... after a minute the VM breaks... but the latest stable works perfectly.
I would go to check what's happening... strange.
I am unable to get any of the 5.13 kernels to run they always error and lock WSL2 up
Now works!
Issue closed?
I am unable to get any of the 5.13 kernels to run they always error and lock WSL2 up