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

Open

k3rst1n opened this issue

Mar 7, 2020

· 61 comments

Comments

Hi,

After installing Windows 10 on my desktop, I installed the Debian distribution. Right after installation, it loaded and worked fine, however after closing the shell and re-opening it, it got stuck while loading and my CPU usage increased to 100% - in the services I could see around 8 processed called "init" that were running and using up all cpu resources. I wasn't able to kill the processes, only a reboot helped. As the processes came back every time I opened the Debian shell, I eventually deinstalled the disto. Now, when I try to install any distro, I always end up with the same error:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80070002
Error: 0x80070002 The system cannot find the file specified.
Press any key to continue...

I tried all possible combinations of deinstalling, reboot, etc. wsllist never shows any of the Distros, even if they show up in the installed programs.

wsl --list --all
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore

Attached you can find my logs - I was collecting them while I tried to install the Ubuntu distribution.

logs.zip

Windows version: Win 10 Pro, Version 1909 Build 18363.657.

Please let me know if you require anything else!

Thank you, Kerstin

The text was updated successfully, but these errors were encountered:

Same here. I add this working. Today I've tried to open my Ubuntu terminal and I'm having the same problem.

Same here. Happened when I upgraded to WSL 2.

@CBornes @k3rst1n Did yall find any fixes for this?

Not to bump but.... also having this issue. Windows 10.0.19041.264

I also have this issue on 2004 Build 20150.1000

Same issue here on Windows version 2004 build 19041.329

I was able to get this resolved by removing the WSL kernel update from programs/features, and then removing the WSL feature, rebooting, and then re-enabling the WSL feature and rebooting. I also deleted my WSL instances during this process.

I was able to get this resolved by removing the WSL kernel update from programs/features, and then removing the WSL feature, rebooting, and then re-enabling the WSL feature and rebooting. I also deleted my WSL instances during this process.

Hey @chancez, I tried this at 20150.1000 - it unfortunatly did not help.

I was able to get this resolved by removing the WSL kernel update from programs/features, and then removing the WSL feature, rebooting, and then re-enabling the WSL feature and rebooting. I also deleted my WSL instances during this process.

Thank You for the info, I've tried this partially, by uninstalling that WSL kernel update because since a couple of reboots ago WSL2 is completely broken... I'm desperate to recover my WSL2 filesystem, hopefully somebody from the dev team can help us here :(

I'm on build

19592 and my WSL2 only says this:

I've tried de-registering Ubuntu but it's dead and won't launch... I'm really in need to recover the WSL2 filesystem if there's a way. oh, and btw to make it work again!

Thanks for your time / help.

The only way I fixed this is by disabling WSL and re-enabling it again, I tried everything.

The only way I fixed this is by disabling WSL and re-enabling it again, I tried everything.

WSL2 on insider previews has been so unreliable I've gone back to something I can control: an Ubuntu VM made in HyperV which is basically the same, and I'm already feeling the experience is much better.

I now feel confident that no windows update will wipe out my WSL2 distros, as a next step I'm opting out of insider previews, I'm probably done with WSL and evangelizing it, It's a good concept but the execution is so lacking... I don't feel it's really worth it.

insider previews

unreliable

Well, it's not like you weren't warned about it. I don't believe this is a valid reason to hate on WSL2.

Sure, i was aware of the insider "disclaimer" and that's just my personal opinion.

But I won't deny I'm sick of WSL2, too many things broke at the wrong time, I'm outta here. Enjoy the ride!

Bumping this since it is really an issue and blocked the usage of WSL 2

Issue still appears in December.

have anyone found fix for this issue? i was using 2sl2 kali-linux peacefully but today i tried to overwrite the kali-linux.vhdx file, then this problem started for me and i did every fixes posted on other git issues, still i can't find any fix. anyone help me .

the same issue. I tried reinstalling wsl and disabling virtual machine and then enabling it again, didn't work.

Same problem here!

As people are suggesting on

5107, I also think that it is related to the absence of vEthernet (WSL) adapter. No matter how much I try reinstalling WSL stuff in different order, there is no way the nic adapter being installed again.

Iv'e also tried to "manually" install the adapter via Hyper-V with no luck.😥

Same problem here!

As people are suggesting on

5107, I also think that it is related to the absence of vEthernet (WSL) adapter. No matter how much I try reinstalling WSL stuff in different order, there is no way the nic adapter being installed again.

Iv'e also tried to "manually" install the adapter via Hyper-V with no luck.😥

I Agree, I also having this problem on 20H2, it's frustating Edit :

I fix it using in-place upgrade with latest windows 20H2 and it works. I take sometimes and no data/Apps deleted as like reset windows. It works for me anyway, I could install fedora on WSL now

I encountered this issue today. I had Docker Desktop installed, I removed it but no luck starting with WSL Ubuntu :(

I encountered this issue today. I had Docker Desktop installed, I removed it but no luck starting with WSL Ubuntu :(

exactly same situation as u, and have no idea what to do

I wish I hadn't of updated. Everything was working fine util about a week ago. I hope we are getting close to a fix reliable permanent fix.

I have the same issue on 21H1 Build 19043.1237. I tried wsl --set-default-version 1 and this works for me.

Philip-W, halbarba, l3nnartt, lsusr, kk140906, Haleem85, Wolframme, Luluzao0, slawkens, NDK0045, and 4 more reacted with thumbs up emoji Philip-W, l3nnartt, lsusr, Wolframme, Luluzao0, SufyanCS, and mlbrothers reacted with hooray emoji SOUKAINAEZZAAMI reacted with heart emoji

All reactions

• 👍14 reactions
• 🎉7 reactions
• ❤️1 reaction

I just managed to fix this, but am unsure of the exact underlying issue, or what caused it (the original issue was Docker Desktop failing to start with various random errors).

Firstly I noticed the comment above about a possible link to network adapters. I noticed I had a "VMWare Bridge Protocol" attached to my ethernet adapter, probably left over from an old VMWare Player install, but I was unable to remove/uninstall it (0x8007007E error).

I then did a Network Reset in Windows, which broke all my networking, the adapters had the error "Windows is still setting up the class configuration for this device, Code 56" which is relatively obscure, and again apparently related to an incompatible underlying driver. This error seems to be impossible to solve by a user (ie. through the normal Windows UI) except by a system restore or something. I was only able to fix it by running the CCleaner software (free version), and accepting all it's recommendations in the registry clean section.

After a reboot all the networking worked fine again, and I was able to install WSL2 and then reinstall Docker Desktop (which is what started me on the trail of fixing it all!)

mattkotys, Zeratoxx, l3nnartt, Durbek-Gafur, kehao-chen, copapp, jazzlost, CocoDico78, frankiee12a9, Erokos, and 5 more reacted with thumbs up emoji kehao-chen reacted with laugh emoji Francis-Ferri-personal, rz1027, and hieudtrung reacted with heart emoji

All reactions

• 👍15 reactions
• 😄1 reaction
• ❤️3 reactions

I was only able to fix it by running the CCleaner software (free version), and accepting all it's recommendations in the registry clean section.

I guess that fixed it for me! WSL 2 is working fine again.

I was switching to WPM/WinGet from Chocolatey because I have a bunch of software installed through choco that didn't install shortcuts, thinking winget would be more reliable - then this happened 😂

Kaspersky Antivirus disabled WSL from starting when I unknowingly told it to fix running Linux apps from Windows. To enable, lookup how to set LxssManager startup to manual via registry (Access Denied on the GUI)

The only way I fixed this is by disabling WSL and re-enabling it again, I tried everything.

I double tried, triple tried but seems like your solution did not work

for anyone still looking for solution here, try to delete the .wslconfig under your `C:\Users\<your username>`.

gibait, RostigerDagmer, takam1602, jerrychong25, allan-holbrook, hartlpa, mattDuque, hmajid2301, MaheshMaya, Seryta, and 8 more reacted with thumbs up emoji

All reactions

• 👍18 reactions

for anyone still looking for solution here, try to delete the .wslconfig under your C:\Users.

I uninstalled Docker Desktop. Removed Ubuntu install. Disabled and re-enabled WSL. This is what made it work eventually! Thank you

for anyone still looking for solution here, try to delete the .wslconfig under your C:\Users\<your username>\.

Thanks @hguitar !

This method works for my end!

I just managed to fix this, but am unsure of the exact underlying issue, or what caused it (the original issue was Docker Desktop failing to start with various random errors).

Firstly I noticed the comment above about a possible link to network adapters. I noticed I had a "VMWare Bridge Protocol" attached to my ethernet adapter, probably left over from an old VMWare Player install, but I was unable to remove/uninstall it (0x8007007E error).

I then did a Network Reset in Windows, which broke all my networking, the adapters had the error "Windows is still setting up the class configuration for this device, Code 56" which is relatively obscure, and again apparently related to an incompatible underlying driver. This error seems to be impossible to solve by a user (ie. through the normal Windows UI) except by a system restore or something. I was only able to fix it by running the CCleaner software (free version), and accepting all it's recommendations in the registry clean section.

After a reboot all the networking worked fine again, and I was able to install WSL2 and then reinstall Docker Desktop (which is what started me on the trail of fixing it all!)

Using CCleaner and cleaning registry helped me. Thanks

help, couldnt solve by solution above, I have tried

• docker desktop was uninstalled
• I dont have .wslconfig in

  wsl --list --all Windows Subsystem for Linux has no installed distributions. Distributions can be installed by visiting the Microsoft Store: https://aka.ms/wslstore

  0
• wsl feature off->ccleaner to clean registry->reboot->wsl feature on again->reboot->

  wsl --list --all Windows Subsystem for Linux has no installed distributions. Distributions can be installed by visiting the Microsoft Store: https://aka.ms/wslstore

  1 return

  wsl --list --all Windows Subsystem for Linux has no installed distributions. Distributions can be installed by visiting the Microsoft Store: https://aka.ms/wslstore

  2

I thought it was because

wsl --list --all
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore

3 was stopped, but wsl --install was run with

wsl --list --all
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore

3 running. I dont know what else I could try

Edit: problem was solved, vEthernet (WSL) adapter was failed to installed, since vmware blocking hyper-v to install the adapter, I uninstalled it. Problem solved

Could not find root cause of problem.

What achieved a successful install for me was to forgo using winget and just install from Microsoft Store.

Just to see if that cleared the root cause, used

wsl --list --all
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore

6, rebooted, then tried

wsl --list --all
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore

7

which resulted in

wsl --list --all
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore

8

So maybe this is a winget issue and not a

If you want to rename your WSL distro, you have to:
Stop all instances of WSL
Open Registry Editor and go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
Find the distro you want to rename, look for the DistributionName
Change it as you want
Start WSL again, you can also execute wsl.exe -l -v to check if it changes

0 issue.

A speculation of mine as to what I did that is the root cause is that I renamed a distribution by editing a distribution name as per https://superuser.com/a/1613251/125532

If you want to rename your WSL distro, you have to:
Stop all instances of WSL
Open Registry Editor and go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
Find the distro you want to rename, look for the DistributionName
Change it as you want
Start WSL again, you can also execute wsl.exe -l -v to check if it changes

As per microsoft/winget-cli

1705 using Windows Event Viewer in branch

Applications and Services Logs/Microsoft/Windows/AppXDeployment-Server/Microsoft-Windows-AppXDeploymentServer/Operational

for tab: Details find error: 0x80073cf1

For more on the error code see: Troubleshooting packaging, deployment, and query of Windows apps

Error code: ERROR_INSTALL_PACKAGE_NOT_FOUND Value: 0x80073CF1 Description and possible causes: The package couldn't be found. You may get this error while removing a package that isn't installed for the current user.

Same problem here!

As people are suggesting on

5107, I also think that it is related to the absence of vEthernet (WSL) adapter. No matter how much I try reinstalling WSL stuff in different order, there is no way the nic adapter being installed again.

Iv'e also tried to "manually" install the adapter via Hyper-V with no luck.😥

My solution based on CollapsedMetals idea that the problem can be related to missing the vEthernet (WSL) adapter. Was to try and fix its as a missing network adapter. When i made it to windows network reset, what ended up happening was that all my network adapters got corrupted and returned code 56 forever. This error led me to this, which made me update to the latest windows from a USB drive. After the update my internet adapters worked fine, vEthernet (WSL) adapter had returned, and WSL2 worked fine after installing the latest kernel update.

wsl --set-default-version 1 seems to work on build 2004

I got same problem. And I remembered that I uninstalled the VMware Workstation Player before the problem occur. So I tried to reinstall the VMware Workstation Player and it was solved. You could try to install VMware Workstation Player if it helps.

for anyone still looking for solution here, try to delete the .wslconfig under your C:\Users\<your username>\.

This worked for me right away, no reboots or uninstall/reinstall required, thank you!

Error: 0x80070002 The system cannot find the file specified

Here's how I fixed it today! Thanks, everyone for this wonderful discussion above, it did help me to fix it!

1. Install the free version of CCleaner and use it to fix the issues present in your system. I've used v6.09 at the time of doing
   
2. Check whether Windows feature windows subsystem for Linux is on. If not then turn it ON and restart your machine
   
3. From the windows store get your desired Ubuntu version and run it. Set your username and password. That's all. Now it will work.
   

I just managed to fix this, but am unsure of the exact underlying issue, or what caused it (the original issue was Docker Desktop failing to start with various random errors).

Firstly I noticed the comment above about a possible link to network adapters. I noticed I had a "VMWare Bridge Protocol" attached to my ethernet adapter, probably left over from an old VMWare Player install, but I was unable to remove/uninstall it (0x8007007E error).

I then did a Network Reset in Windows, which broke all my networking, the adapters had the error "Windows is still setting up the class configuration for this device, Code 56" which is relatively obscure, and again apparently related to an incompatible underlying driver. This error seems to be impossible to solve by a user (ie. through the normal Windows UI) except by a system restore or something. I was only able to fix it by running the CCleaner software (free version), and accepting all it's recommendations in the registry clean section.

After a reboot all the networking worked fine again, and I was able to install WSL2 and then reinstall Docker Desktop (which is what started me on the trail of fixing it all!)

Thank you, from all the proposed solutions only this one worked for me! You're a life saver!

I just managed to fix this, but am unsure of the exact underlying issue, or what caused it (the original issue was Docker Desktop failing to start with various random errors).

Firstly I noticed the comment above about a possible link to network adapters. I noticed I had a "VMWare Bridge Protocol" attached to my ethernet adapter, probably left over from an old VMWare Player install, but I was unable to remove/uninstall it (0x8007007E error).

I then did a Network Reset in Windows, which broke all my networking, the adapters had the error "Windows is still setting up the class configuration for this device, Code 56" which is relatively obscure, and again apparently related to an incompatible underlying driver. This error seems to be impossible to solve by a user (ie. through the normal Windows UI) except by a system restore or something. I was only able to fix it by running the CCleaner software (free version), and accepting all it's recommendations in the registry clean section.

After a reboot all the networking worked fine again, and I was able to install WSL2 and then reinstall Docker Desktop (which is what started me on the trail of fixing it all!)

i wanna just say thanks for your sharing. it help me to solve my mind blowing problem.

I just managed to fix this, but am unsure of the exact underlying issue, or what caused it (the original issue was Docker Desktop failing to start with various random errors).

Firstly I noticed the comment above about a possible link to network adapters. I noticed I had a "VMWare Bridge Protocol" attached to my ethernet adapter, probably left over from an old VMWare Player install, but I was unable to remove/uninstall it (0x8007007E error).

I then did a Network Reset in Windows, which broke all my networking, the adapters had the error "Windows is still setting up the class configuration for this device, Code 56" which is relatively obscure, and again apparently related to an incompatible underlying driver. This error seems to be impossible to solve by a user (ie. through the normal Windows UI) except by a system restore or something. I was only able to fix it by running the CCleaner software (free version), and accepting all it's recommendations in the registry clean section.

After a reboot all the networking worked fine again, and I was able to install WSL2 and then reinstall Docker Desktop (which is what started me on the trail of fixing it all!)

I just had to use CCleaner to remove the registry

Same issue suddenly occurs, and none of the above solutions work for me.

wsl --set-default-version 1 seemed to "work" temporarily for me, but ended up creating a new distribution with none of my existing files. So I eventually had to wipe WSL (not just the distro, like all of WSL) and reinstall it. Make sure to back up your filesystem before deleting/uninstalling anything by backing up

If you want to rename your WSL distro, you have to:
Stop all instances of WSL
Open Registry Editor and go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
Find the distro you want to rename, look for the DistributionName
Change it as you want
Start WSL again, you can also execute wsl.exe -l -v to check if it changes

6, then copying the backup to the original location once you're reinstalled everything. In my case (using the

If you want to rename your WSL distro, you have to:
Stop all instances of WSL
Open Registry Editor and go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
Find the distro you want to rename, look for the DistributionName
Change it as you want
Start WSL again, you can also execute wsl.exe -l -v to check if it changes

7 distro) the

If you want to rename your WSL distro, you have to:
Stop all instances of WSL
Open Registry Editor and go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
Find the distro you want to rename, look for the DistributionName
Change it as you want
Start WSL again, you can also execute wsl.exe -l -v to check if it changes

8 folder was called

If you want to rename your WSL distro, you have to:
Stop all instances of WSL
Open Registry Editor and go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
Find the distro you want to rename, look for the DistributionName
Change it as you want
Start WSL again, you can also execute wsl.exe -l -v to check if it changes

9.

I just managed to fix this, but am unsure of the exact underlying issue, or what caused it (the original issue was Docker Desktop failing to start with various random errors).

Firstly I noticed the comment above about a possible link to network adapters. I noticed I had a "VMWare Bridge Protocol" attached to my ethernet adapter, probably left over from an old VMWare Player install, but I was unable to remove/uninstall it (0x8007007E error).

I then did a Network Reset in Windows, which broke all my networking, the adapters had the error "Windows is still setting up the class configuration for this device, Code 56" which is relatively obscure, and again apparently related to an incompatible underlying driver. This error seems to be impossible to solve by a user (ie. through the normal Windows UI) except by a system restore or something. I was only able to fix it by running the CCleaner software (free version), and accepting all it's recommendations in the registry clean section.

After a reboot all the networking worked fine again, and I was able to install WSL2 and then reinstall Docker Desktop (which is what started me on the trail of fixing it all!)

Ok I have to confess, I thought I caused this problem for myself by blindly deleting huge vhdx's and uninstalling docker desktop. But just before this problem I coincidentally installed VMware Workstation. It seems interestingly unrelated but solved my problem like charm, despite trying tons of other solution. Cheers bro, you're a magician

I just managed to fix this, but am unsure of the exact underlying issue, or what caused it (the original issue was Docker Desktop failing to start with various random errors).

Firstly I noticed the comment above about a possible link to network adapters. I noticed I had a "VMWare Bridge Protocol" attached to my ethernet adapter, probably left over from an old VMWare Player install, but I was unable to remove/uninstall it (0x8007007E error). I then did a Network Reset in Windows, which broke all my networking, the adapters had the error "Windows is still setting up the class configuration for this device, Code 56" which is relatively obscure, and again apparently related to an incompatible underlying driver. This error seems to be impossible to solve by a user (ie. through the normal Windows UI) except by a system restore or something. I was only able to fix it by running the CCleaner software (free version), and accepting all it's recommendations in the registry clean section. After a reboot all the networking worked fine again, and I was able to install WSL2 and then reinstall Docker Desktop (which is what started me on the trail of fixing it all!)

Using CCleaner and cleaning registry helped me. Thanks

It really works! I tried to solve this problem all day and you really saved me.

I tired many things over past 24 hours, and the only thing that worked for me was removing the whole wsl and then re-installing it.

I just managed to fix this, but am unsure of the exact underlying issue, or what caused it (the original issue was Docker Desktop failing to start with various random errors).

Firstly I noticed the comment above about a possible link to network adapters. I noticed I had a "VMWare Bridge Protocol" attached to my ethernet adapter, probably left over from an old VMWare Player install, but I was unable to remove/uninstall it (0x8007007E error).

I then did a Network Reset in Windows, which broke all my networking, the adapters had the error "Windows is still setting up the class configuration for this device, Code 56" which is relatively obscure, and again apparently related to an incompatible underlying driver. This error seems to be impossible to solve by a user (ie. through the normal Windows UI) except by a system restore or something. I was only able to fix it by running the CCleaner software (free version), and accepting all it's recommendations in the registry clean section.

After a reboot all the networking worked fine again, and I was able to install WSL2 and then reinstall Docker Desktop (which is what started me on the trail of fixing it all!)

After years of development, this WSL2 issue still hit my computer today. I tried all solutions proposed here and installing CCleaner was the only way. Thank you very much.