-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove wsl --unregister DISTRO_NAME
from the recommended commands to be run when "something goes wrong"
#307
Comments
wsl --unregister DISTRO_NAME
from the recommended commands to be run when "something goes wrong"
Ihave the same problem |
I had to run wsl --update and then I got past the Ubuntu installer error. |
Worked perfectly! |
@clmnin Do you remember which steps you undertook to recover your filesystem after using the --unregister flag? |
@pinzutu I moved to a Mac and even stopped being a PC gamer (got a PS and a steam deck). I'm never even touching WSL with a ten foot pole.
|
@clmnin I see. Thank you for the reply still! I do agree that the "unregister" flag being synonymous to "delete filesystem" could be highlighted more clearly to the user than through a --help entry. |
Description
I had the below two windows updates performed
And on restart I see a window saying "Something went wrong". And was asked to run the following commands
But
wsl --unregister DISTRO_NAME
is a dangerous command and should not be run by the uninitiated.This does not seem to be a Windows WSL issue. I was redirected to this repo - here is my original issue raised in microsoft/WSL#9049
I've attached the image of the window asking me to run
wsl --unregister DISTRO_NAME
Need and use case
No warning is currently given when asking the user to run
wsl --unregister DISTRO_NAME
.I had previously faced this same issue ("Something went wrong") and had unknowingly ran
wsl --unregister
(link to my previous issue - microsoft/WSL#8992 ). Which resulted me in loosing my data, I've recovered since then. But adding a warning to let future users know of the consequence would be great.Additional information
No response
The text was updated successfully, but these errors were encountered: