![]() Ubuntu will again run its installation and initial configuration (and it should now work with the "bad" version unregistered). Rerun the ubuntu2004.exe or ubuntu.exe (either from the command-line or the Start menu) Remember that this is a destructive operation: wsl -l -v With two different backups in place, it's time to unregister Ubuntu from WSL. Then find the CanonicalGroupLimited.Ubuntu (the name may vary. Start in File Explorer with: %userprofile%\AppData\Local\Packages Second, find the virtual drive for your Ubuntu WSL distribution. Wsl -export Ubuntu-20.04 ubuntu_backup.tar # Change "Ubuntu-20.04" in the next line to match the distribution name in use Exit the distribution, then go to PowerShell and: wsl -l -v Note that this is a destructive operation that will remove your existing Ubuntu distribution.Īssuming that the distribution still runs, via the wsl command, it is possible to back it up before unregistering, then restore it afterwards.įirst, create a backup of the distribution via the wsl -export command. Edit - It's worthwhile to actually fix this.įrom the Github reports, you can truly fix the issue by unregistering the Ubuntu distribution. Assuming that Ubuntu is your default WSL distribution (found via wsl -l -v), then will have the same effect and just launch it. Personally, I'd just change any link to use the wsl.exe command instead of ubuntu.exe (or ubuntu2004.exe). But the WSL files are already extracted and configured, leading to the error. It doesn't find it (because your version is incorrectly named Ubuntu20.04LTS), so it attempts to run the rootfs/configuration stage again.ubuntu2004.exe is looking for a distribution named Ubuntu-20.04.Unfortunately, if you installed during that window where the "bad version" was in the Store, then the fix breaks things for you, because now: However, it seems Canonical quickly pushed a fix for the issue. This would have caused a similar problem for all users that updated. The previous version appears to have had a bug where this was renamed Ubuntu2004.LTS (thanks for pointing this out in the comments). The name of the distribution that is installed should be (historically), Ubuntu-20.04. The problem seems to have actually started in the previous version of the "Ubuntu 20.04" app in the Microsoft Store. ![]() ![]() If it's already installed, it launches WSL using that distribution. If not, it extracts the Ubuntu rootfs and asks you to configure a username and password. The ubuntu.exe command really does two things - It first checks to see if Ubuntu is installed in WSL. ![]() The ubuntu.exe or ubuntu2004.exe ( edit: I now believe this only happens with ubuntu2004.exe, but please let me know if you experience this on the ubuntu.exe version) is broken after update. This answer contains the background on the problem and why both of these techniques work for correcting it.įrom reading through several Github issues (including, from the looks of it, one that you posted there), this appears to be a problem with the recent Store update of the Ubuntu app. However, the "quick and easy" (but less "safe") registry edit that I posted as a second answer appears to be working for multiple users as well. Update: This answer was my first attempt at the solution (which does work), and the "safe" way of doing it. WslRegisterDistribution failed with error: 0x80070050 May I please get any guidance on this one? as I have to use WSL for my educational purpose that would be really helpful thanks Installing, this may take a few minutes. I also restarted the computer and checked to make sure my Virtual Machine Platform and Windows Subsystem for Linux are ON and I found out that both of these services were already ON. But after the I got an update regarding WSL from Microsoft Store I updated WSL and since then it is throwing this error. Hello I had successfully installed WSL few days ago and everything was working fine. Windows Subsystem for Linux is already installed so it should operate normally. ![]() I got an update about the WSL from Microsoft Store and I updated it then it stopped working.īash shell. I already had WSL installed from Microsoft Store few days and it was working fine. ![]()
0 Comments
Leave a Reply. |