Closed peteykun closed 4 years ago
I'm having the same issue on 20197.
This is the output of Powershell ipconfig
I do not use a VPN, just WSL2 and docker desktop.
Trying to change the DNS settings inside WSL to 8.8.8.8
doesn't work either
Does anyone have a workaround ?
Seems like it's the same issue as https://github.com/microsoft/WSL/issues/5805
Having same issue. For me it appear that connectivity is there but once I connect to a wireless connection or plug in the ethernet Media Disconnect happens.
There is a new insider build. Would you like to check?
I currently have it installed and hasn't changed any of the issues.
20201,The same problem, wsl network does not work when the system wakes up from sleep.
20201 has the same problem, the availability of wsl2 is too poor, and it has been rolled back to wsl1.
I'm seeing this issue as well. Build 20197. wsl2 with both Ubuntu 18.04 and 20.04 vm's.
WSL vEethernet adapter appears media disconnected. working fine after reboot. but will be disconnected again within 30 mins.
Hey folks we're looking into resolving this issue! If you're seeing it could you please collect some logs for us and file it in Feedback hub? You can find the instructions to do that here. Please link to your feedback hub item here in this issue to help us find it. Thank you!
heres the feedback hub link - https://aka.ms/AA9g338l
mine as well - https://aka.ms/AA9hjik
If it worth mentioning, after sleeping the same network problem also affects Windows Sandbox
@craigloewen-msft do you have some workaround to force the vEthernet to connect with a command or something ? thx
I reported what appears to be a related issue in:
https://github.com/microsoft/WSL/issues/5805
At least in one occurrence for me the disconnection appears to be related to enabling VPN. Is there a log of when events such as switches being connected/disconnected are logged? I currently have not found a way of re-enabling the switch anyone know of a PowerShell command which will do this?
@craigloewen-msft Hey I'm having the same issue in build 20197 with Ubuntu 18.04 running with WSL2. Feedback hub link: https://aka.ms/AA9hz4q
@mwoodpatrick @craigloewen-msft I'm having a similar issue. When I connect the host windows machine to an OpenVPN server with the OpenVPN windows client, my Ethernet Adapter vEthernet (WSL) crashes : Does anyone knows how to restart it from the host, ie with Powershell ?
@craigloewen-msft Have the same problem. Just submitted a ticket throuhg the feedback hub. Wasn't signed in so didn't get a link to it.
Tried to see if the problem was resolved in build 20201 but no dice
Another report if it still need https://aka.ms/AA9hmex
Now, with build 20201, it hasn't been corrected, it's gotten worse!
On a laptop with 1 ethernet adapter, 1 Wireless adapter, WSL 2 with one distro, ipconfig
shows 30 entries! (Powershell Get-NetIPConfiguration
shows the same). How can I purge this back to reality? Note, I've replaced real IP addresses with x.x.x.x
C:\Toolkit>ipconfig
Windows IP Configuration
Ethernet adapter vEthernet (Default Switch):
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL):
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 4:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 5:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 4:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 5:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 8:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 8:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (Default Switch) 13:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 13:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : x.x.x.x
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : x.x.x.x
Unknown adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Local Area Connection* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : x.x.x.x
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : x.x.x.x
Ethernet adapter vEthernet (Default Switch) 14:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter vEthernet (WSL) 14:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : xxxx::xxxx:xxxx:xxxxxxxx
IPv4 Address. . . . . . . . . . . : x.x.x.x
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
@sc0ttwad3 I'm not experiencing this duplication issue with 20201. My WSL2 network was also working fine after my laptop woke up from sleep today. I had some issue with Docker Desktop, but so far no weird disconnect. I did try to use openvpn with my host windows and it broke the wsl connection though. I am not sure if those issues are related.
Can confirm that the issue still exists with 20201.1000, though I do not face the adapter duplication @sc0ttwad3 seems to be having. I just tried putting my laptop to sleep and waking it up and the adapter immediately disconnected. Spent the better part of the day trying to install the update, for those having trouble here is my solution to the problem. Regardless, the issue with the WSL adapter still very much persists.
Still experimence it since 20197 update. Relevant info: build 20201.1000 ,WSL2 with Ubuntu 20.04.1 VSCode 1.48.2 synching local '//wsl$/...' git repo. Got this sequence repeting in event viewer Hyper-V Switch ext (last 3 events)
Device ROOT\VMS_VSMP\0000 had a problem starting.
Driver Name: wvms_mp_windows.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Service: VMSMP
Lower Filters:
Upper Filters:
Problem: 0xA
Problem Status: 0xC0000001
Device ROOT\VMS_VSMP\0000 was deleted.
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Device ROOT\VMS_VSMP\0000 was configured.
Driver Name: wvms_mp_windows.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.20201.1000
Driver Provider: Microsoft
Driver Section: VMSVSMP.ndi
Driver Rank: 0xFF0000
Matching Device Id: vms_vsmp
Outranked Drivers:
Device Updated: true
Parent Device: HTREE\ROOT\0
We are investigating, something clearly broke recently in the networking stack.
Any workaround?
Best suggestion I can give until this problem is resolved is disconnect any external adapters. Immediately after you boot up if you aren't using a wired connection, connect to your Wi-Fi. Avoid changing or disconnecting any adapters for the time that you need WSL on. For me since doing this the WSL2 adapters has been working and no problems as of yet. (6 Hours since boot time and doing this)
Some temporary solution I found to fix the problem after PC sleep, works without rebooting. Do steps A, B, C below a few times. I'm not sure about the proper order -- it works differently every time for me, but the connection appears after a few trials.
Restart-Service LxssManager
from admin power shell)or
Win+R
⇒ services.msc
Host Network Service
Go to Device Manager (in Control Panel)
Enable 'Show hidden devices'
- Open 'Network Adapters'
- Disable and then Enable the Hyper-V adapters you have
Doing ABC for a few times brings back the connection to WSL and it does not seem to go away!
Steps above is a workaround.
As stated, I've restarted randomly and finally, it starts working after a couple times.
I think I got a permanent solution: First go to device manager
Show hidden devices
Delete all Hyper-V Virtual Switch Extension Adapter
Restart your computer and then next time you sleep it should still hav e network
I notice that after reboot, Service Host: DNS Client
and Service Host: Network List Service
would go crazy consuming a lot of CPU
Have same issue as sc0ttwad3. After every reboot I get additional adapters showing up. On 20201.rs_prerelease.200822-1922. Neither Default Switch or WSL adapter are functioning properly. Only way I've found to get rid of extra adapters is to use a combination of "Network Reset" and Disable Hyper-V/reboot/Enable Hyper-V/reboot. Reboot+disable/enable doesn't fix networking issue, but clears out extraneous adapters. I'd back off to earlier version, but 20201 also broke the checkpoint so that didn't work :(
I think I got a permanent solution: First go to device manager
Show hidden devices
Delete all Hyper-V Virtual Switch Extension Adapter
Restart your computer and then next time you sleep it should still hav e network
I just realized, it worked for the first time. After restarting it stopped working again, even repeating the steps didn't help.
I notice that after reboot,
Service Host: DNS Client
andService Host: Network List Service
would go crazy consuming a lot of CPU
Same for me as well. Service Host: DNS Client
took almost 50% of my CPU load after a reboot.
Also happening on build 20201. What a time to convert my Linux to WSL2... Converting back to WSL1 post haste. Need it to work, and I need network access to work in WSL. Cannot run GUI apps without it, or certain utilities. Cannot update Linux, either. Tried to look for vEthernet (WSL) but it is nowhere to be found.
Same problem here, network is disconnected, usually after trying to connect using OpenVPN o computer going to sleep.
It's really weird, too! Don't even have to use a VPN or put it to sleep and it still only partly works. Crazy thing is that ifconfig reported the IP address as 172.20.248.8 while pinging a router acts as though Linux's IP address is 172.20.248.7. I've tried everything I can find from scouring the Internet, but nothing has fixed the problem.
Oddly enough, I managed to get lynx and htop to work and run properly (although htop reported zero activity and 0.0% usage on the processor cores even when things were running on them. Anything with a GUI? Forget it. It wouldn't work.
I thought that the newest version of WSL2 also was supposed to be capable of running GUI apps without a third-party Xserver. (At least that was stated at Build 2020. But maybe that feature hasn't made it down to us yet?) That also was a bust.
With or without a third-party Xserver I could not get a single GUI app to run without stating that the connection was refused, or throw some other related error. Performance of those CLI apps was better than in WSL1, so I really was hoping I could use WSL2. But so much doesn't work, and I cannot even update Linux in WSL2 with the CLI, so I had to convert it back to WSL1.
I've been seeing this too on build 20201. The virtual network adapter will show up as disabled and have no IP address.
PS C:\> Get-NetIPConfiguration
InterfaceAlias : vEthernet (WSL) 2
InterfaceIndex : 29
InterfaceDescription : Hyper-V Virtual Ethernet Adapter #2
NetAdapter.Status : Disconnected
InterfaceAlias : vEthernet (WSL)
InterfaceIndex : 8
InterfaceDescription : Hyper-V Virtual Ethernet Adapter
NetAdapter.Status : Disconnected
.. [others removed]
PS C:\> Get-NetAdapter
Name InterfaceDescription ifIndex Status MacAddress LinkSpeed
---- -------------------- ------- ------ ---------- ---------
vEthernet (WSL) 2 Hyper-V Virtual Ethernet Adapter #2 29 Disconnected 00-15-5D-27-12-FA 0 bps
vEthernet (WSL) Hyper-V Virtual Ethernet Adapter 8 Disconnected 00-15-5D-89-30-2F 10 Gbps
... [others removed]
I tried disabling the second adapter, and after rebooting a third one showed up:
PS C:\> Disable-NetAdapter "vEthernet (WSL) 2"
Confirm
Are you sure you want to perform this action?
Disable-NetAdapter 'vEthernet (WSL) 2'
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): y
... [rebooted]
PS C:\WINDOWS\system32> Get-NetAdapter
Name InterfaceDescription ifIndex Status MacAddress LinkSpeed
---- -------------------- ------- ------ ---------- ---------
vEthernet (WSL) 3 Hyper-V Virtual Ethernet Adapter #3 31 Disconnected 00-15-5D-74-66-FF 0 bps
vEthernet (WSL) 2 Hyper-V Virtual Ethernet Adapter #2 29 Disabled 00-15-5D-27-55-85 10 Gbps
vEthernet (WSL) Hyper-V Virtual Ethernet Adapter 8 Disconnected 00-15-5D-89-30-2F 10 Gbps
.. [others removed]
Trying to mess with restarting services lead to things working eventually
PS C:\> wsl --shutdown
PS C:\> stop-service hns
PS C:\> stop-service vmcompute
PS C:\> wsl dig example.com soa +short
The remote procedure call failed and did not execute.
.. [waited many minutes]
PS C:\> wsl dig example.com soa +short
ns.icann.org. noc.dns.icann.org. 2020080310 7200 3600 1209600 3600
.. [this means wsl has a working network again]
I also disabled "vEthernet (WSL)":
PS C:\> Disable-NetAdapter "vEthernet (WSL)"
Confirm
Are you sure you want to perform this action?
Disable-NetAdapter 'vEthernet (WSL)'
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): y
PS C:\> Get-NetAdapter
Name InterfaceDescription ifIndex Status MacAddress LinkSpeed
---- -------------------- ------- ------ ---------- ---------
vEthernet (WSL) 3 Hyper-V Virtual Ethernet Adapter #3 31 Disconnected 00-15-5D-74-66-FF 0 bps
vEthernet (WSL) 2 Hyper-V Virtual Ethernet Adapter #2 29 Disabled 00-15-5D-27-55-85 10 Gbps
vEthernet (WSL) Hyper-V Virtual Ethernet Adapter 8 Disabled 00-15-5D-89-30-2F 10 Gbps
.. [others removed]
So far it's been working for a few days and hasn't created any new adapters, but I don't know if it'll stay that way.
Some temporary solution I found to fix the problem after PC sleep, works without rebooting. Do steps A, B, C below a few times. I'm not sure about the proper order -- it works differently every time for me, but the connection appears after a few trials.
A. Restart the WSL service (
Restart-Service LxssManager
from admin power shell)or
Win+R
⇒services.msc
B. Restart the
Host Network Service
C. Disable and then Enable the Hyper-V network device
- Go to Device Manager (in Control Panel)
- Enable 'Show hidden devices'
- Open 'Network Adapters'
- Disable and then Enable the Hyper-V adapters you have
Doing ABC for a few times brings back the connection to WSL and it does not seem to go away!
Yeah!! I worked for me too!! Thank you for this!!!
I've got the same problem on Build 20201, happening since 20197. Works for awhile after reboots, after a few minutes connected to a VPN and networking literally crashes.
WSL2 was doing so well after the localhost thing was fixed 😞
Below solution appears to have worked, at least once, only did Step A & B
Some temporary solution I found to fix the problem after PC sleep, works without rebooting. Do steps A, B, C below a few times. I'm not sure about the proper order -- it works differently every time for me, but the connection appears after a few trials.
A. Restart the WSL service (
Restart-Service LxssManager
from admin power shell)or
Win+R
⇒services.msc
B. Restart the
Host Network Service
C. Disable and then Enable the Hyper-V network device
- Go to Device Manager (in Control Panel)
- Enable 'Show hidden devices'
- Open 'Network Adapters'
- Disable and then Enable the Hyper-V adapters you have
Doing ABC for a few times brings back the connection to WSL and it does not seem to go away!
Yeah!! I worked for me too!! Thank you for this!!!
Windows 20206: problem still exists.
Also, do you guys experience Service Host: Network List Service
using a high amount of CPU after restart, like 80-90%? Maybe this is somehow related?
Restarting the LxssManager
and Host Network Service
worked for me as well. (Build 20201, have not submitted logs to feedback hub.)
Issue still present on latest insider build: Version 10.0.20206 Build 20206
Feedback hub: https://aka.ms/AA9jjjd
Restarting the services and disabling and re-enabling the Hyper-V devices from Device Manager, multiple times, eventually worked. Unfortunately there are other issues. Some of the programs I use require a system-wide DBus service to be running. For some weird reason, services don't stay running in WSL2. So, programs depending on it crash out, sometimes taking the Xserver with it. Cannot print from apps, either, in WSL2 like I can in WSL1. Not fun. Have to convert back to WSL 1 again. So close, yet so far away...
Restarting those services worked 100% for me for a few days. Stopping working again and after restarting them again, working again, this nails the problem area done!
Current Working fix:
Build: 20201 - 200822-1922
Restarting the
LxssManager
andHost Network Service
worked for me as well. (Build 20201, have not submitted logs to feedback hub.)
I notice that after reboot,
Service Host: DNS Client
andService Host: Network List Service
would go crazy consuming a lot of CPUSame for me as well.
Service Host: DNS Client
took almost 50% of my CPU load after a reboot.
Same for me, not only triggers after rebooting, start WSL, enable VPN over TAP adapter also triggers it.
Edit: Windows Version 10.0.20201.1000
@xan-der Are you also seeing even more vEthernet adapters after build 20206? My list has grown to 23 vEthernet (WSL) adapters and 23 vEthernet (Default switch) adapters on a laptop with ( 1 ) WiFi, ( 1 ) USB-to-Ethernet adapter, ( 1 ) WSL2 Ubuntu distro, and a completely uninstalled ProtonVPN client, removed after build 20197, when something broke DNS resolution in WSL2 after/when using a VPN connection [ #5764, #5256, #5061, #5831, .... ] and related.
Here's the crazy I'm seeing ever since 20197 (and I apologize in advance for the scroll-time ;-) That I would really like to understand/know how to cleanup. I mean this is ridiculous from a simple ipconfig
, IMHO.
C:\temp>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : SOMEHOSTNAME
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : some.domain
Ethernet adapter vEthernet (Default Switch):
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : 00-15-5D-DC-B6-44
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #3
Physical Address. . . . . . . . . : 00-15-5D-FA-EE-6D
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL):
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : 00-15-5D-33-6E-FD
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #5
Physical Address. . . . . . . . . : 00-15-5D-06-F8-15
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #4
Physical Address. . . . . . . . . : 00-15-5D-16-EC-A1
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 4:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #7
Physical Address. . . . . . . . . : 00-15-5D-52-06-B0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #6
Physical Address. . . . . . . . . : 00-15-5D-45-E7-85
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 5:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #9
Physical Address. . . . . . . . . : 00-15-5D-A0-54-18
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 4:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #8
Physical Address. . . . . . . . . : 00-15-5D-36-49-B8
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #11
Physical Address. . . . . . . . . : 00-15-5D-DC-E7-F1
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 5:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #10
Physical Address. . . . . . . . . : 00-15-5D-41-65-A7
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #13
Physical Address. . . . . . . . . : 00-15-5D-AA-33-C2
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #12
Physical Address. . . . . . . . . : 00-15-5D-CA-CC-60
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 8:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #15
Physical Address. . . . . . . . . : 00-15-5D-F2-B7-BF
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #14
Physical Address. . . . . . . . . : 00-15-5D-BB-B3-8A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #17
Physical Address. . . . . . . . . : 00-15-5D-DD-37-29
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 8:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #16
Physical Address. . . . . . . . . : 00-15-5D-BD-E7-19
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #19
Physical Address. . . . . . . . . : 00-15-5D-D8-0A-21
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #18
Physical Address. . . . . . . . . : 00-15-5D-D7-6B-DC
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #21
Physical Address. . . . . . . . . : 00-15-5D-77-3F-0F
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #20
Physical Address. . . . . . . . . : 00-15-5D-AA-F1-EA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #23
Physical Address. . . . . . . . . : 00-15-5D-E7-AD-B3
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #22
Physical Address. . . . . . . . . : 00-15-5D-B1-F6-39
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 13:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #25
Physical Address. . . . . . . . . : 00-15-5D-0C-51-FB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #24
Physical Address. . . . . . . . . : 00-15-5D-92-F0-D7
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 14:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #27
Physical Address. . . . . . . . . : 00-15-5D-92-8D-17
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 13:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #26
Physical Address. . . . . . . . . : 00-15-5D-8C-F2-11
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 15:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #29
Physical Address. . . . . . . . . : 00-15-5D-02-7A-C9
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 14:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #28
Physical Address. . . . . . . . . : 00-15-5D-E2-EA-13
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 16:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #31
Physical Address. . . . . . . . . : 00-15-5D-12-1C-DD
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 15:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #30
Physical Address. . . . . . . . . : 00-15-5D-EC-91-78
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 17:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #33
Physical Address. . . . . . . . . : 00-15-5D-E3-7B-EC
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 16:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #32
Physical Address. . . . . . . . . : 00-15-5D-EE-09-5A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 18:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #35
Physical Address. . . . . . . . . : 00-15-5D-41-6D-5B
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 17:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #34
Physical Address. . . . . . . . . : 00-15-5D-A9-0C-12
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 19:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #37
Physical Address. . . . . . . . . : 00-15-5D-3F-63-6A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 18:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #36
Physical Address. . . . . . . . . : 00-15-5D-5D-8A-2A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 20:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #38
Physical Address. . . . . . . . . : 00-15-5D-05-AD-26
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 21:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #40
Physical Address. . . . . . . . . : 00-15-5D-D8-58-1C
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 19:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #39
Physical Address. . . . . . . . . : 00-15-5D-30-EB-45
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 22:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #42
Physical Address. . . . . . . . . : 00-15-5D-63-58-DB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 20:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #41
Physical Address. . . . . . . . . : 00-15-5D-FB-03-B0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch) 23:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #44
Physical Address. . . . . . . . . : 00-15-5D-0F-3D-4F
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 21:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #43
Physical Address. . . . . . . . . : 00-15-5D-C8-58-46
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 22:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #45
Physical Address. . . . . . . . . : 00-15-5D-AE-C7-A9
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . : neo.rr.com
Description . . . . . . . . . . . : ASIX AX88179 USB 3.0 to Gigabit Ethernet Adapter #2
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : NOT SHOWN
IPv4 Address. . . . . . . . . . . : x.x.x.x(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, September 4, 2020 12:42:36 AM
Lease Expires . . . . . . . . . . : Saturday, September 5, 2020 12:42:37 AM
Default Gateway . . . . . . . . . : x.x.x.x
DHCP Server . . . . . . . . . . . : x.x.x.x
DHCPv6 IAID . . . . . . . . . . . : NOT SHOWN
DHCPv6 Client DUID. . . . . . . . : NOT SHOWN
DNS Servers . . . . . . . . . . . : x.x.x.x
Primary WINS Server . . . . . . . : x.x.x.x
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter Local Area Connection* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 36-F6-4B-DC-FC-6C
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . : neo.rr.com
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8265
Physical Address. . . . . . . . . : XX-XX-XX-XX-XX-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : x.x.x.x(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, September 4, 2020 12:36:51 AM
Lease Expires . . . . . . . . . . : Saturday, September 5, 2020 12:42:46 AM
Default Gateway . . . . . . . . . : x.x.x.x
DHCP Server . . . . . . . . . . . : x.x.x.x
DNS Servers . . . . . . . . . . . : x.x.x.x
Primary WINS Server . . . . . . . : x.x.x.x
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter vEthernet (Default Switch) 24:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #46
Physical Address. . . . . . . . . : 00-15-5D-E0-33-3E
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (WSL) 23:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #47
Physical Address. . . . . . . . . : 00-15-5D-39-03-1B
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Build 20206 and Ubuntu 18.04 had same problem with this build install -- no vEthernet (WSL). Enabling Hyper-V in Windows Features solved the problem for me.
@sc0ttwad3 I also have lots of these. Does your CPU consumption also go very high after restart with Service Hosts DNS and Network List consuming a crazy amount of CPU?
@ad-on-is Yes! Charting it with ProcessExplorer shows it maxing CPU resources while it restarts and dips down to 70-80%.
@sc0ttwad3 And it takes quite a couple of minutes, like 15 or more or so, to settle down?
Environment
Steps to reproduce
ipconfig
on Windows showsExpected behavior
Network access should be available.
Actual behavior
As the adapter is disconnected, cannot access the network from inside WSL.
This issue did not exist prior to installing the latest Windows update from the dev channel.
Requires a Windows restart to restore network access, but the adapter disconnects once again arbitrarily.
Putting the laptop to sleep and waking it up almost always causes the adapter to show up as disconnected immediately.
Does not seem to be related to the use of a VPN although I use one (via the OpenConnect client).