WSL network was not found #10089

Activity

1. soroshsabz commented on May 10, 2023

   

   soroshsabz

   on May 10, 2023

   Author

   More actions

   related to https://superuser.com/q/1783419/167405
2. Ben Hillis (benhillis)

   added

   network

   on May 10, 2023
3. benhillis commented on May 10, 2023

   

   Ben Hillis (benhillis)

   on May 10, 2023

   Member

   More actions

   /logs
4. microsoft-github-policy-service

   added

   needs-author-feedback

   on May 10, 2023
5. soroshsabz commented on May 10, 2023

   

   soroshsabz

   on May 10, 2023

   Author

   More actions

   After I remove WSL vEthernet on all Hyper-V virtual machine, this error has gone, but I get another error, that my WSL does not connect to internet

   What is your info needed to provide some help to me?

   thanks
6. microsoft-github-policy-service

   removed

   needs-author-feedback

   on May 10, 2023
7. soroshsabz commented on May 10, 2023

   

   soroshsabz

   on May 10, 2023

   Author

   More actions

   Ben Hillis (@benhillis) After restarting my PC, this problem is gone :|

   this system is not reliable enough
8. soroshsabz

   closed this as completedon May 10, 2023
9. Raven-Singularity commented on Sep 19, 2024

   

   Raven-Singularity

   on Sep 19, 2024

   More actions

   I had a similar incident after installing then uninstalling VMware, which left my Hyper-V Extensible Virtual Switch entirely broken. I was unable to load WSL2 for about 10 days due to the missing virtual network adapter.

   What fixed it for me was removing this registry key which VMware left behind:

   HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b}
   

   After removing this registry key manually, then clicking Network Reset on the Networking Control Panel page, my system came back up with fully working networking, including my WSL2 launching again!

   Note: Network Reset made me wait 5 minutes before it rebooted the system.

   Hope it helps other people who are stuck!

   Other error codes and error messages I experienced:

   Windows is still setting up class configuration for this device. (Code 56)
   0x80071779
   0x80041002