-
Notifications
You must be signed in to change notification settings - Fork 839
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
WSL vEthernet adapter shows up as disconnected after the latest Windows 10 update (10.0.20197.1000) #5821
Comments
Seems like it's the same issue as #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. 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: 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. |
@mwoodpatrick @craigloewen-msft |
@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,
|
@sc0ttwad3 I'm not experiencing this duplication issue with 20201. |
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)
|
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. A. Restart the WSL service (
|
Steps above is a workaround. As stated, I've restarted randomly and finally, it starts working after a couple times. |
This works fine on my pc. |
Even though it is not disconnecting the interface anymore, I can observe the same connectivity issues as if it was disconnected on build 20236. |
Each time it happens to me, it is always the LxssManager Service. I don’t have to touch the other service or devices anymore. Just LxssManager. I have to stop the service, and when it hangs, end the entire process tree in Resource Monitor, and start the service in Services. Then it works for a while until it happens again, when I then need to end the process tree and start the service again. I haven’t had to touch Host Network Service for the last few builds.
|
this is happening to me too since today |
Is there any feedback on this yet? I installed a fresh version of Windows 10 on my new laptop, and this issue started to happen again. |
I have the same issue, and I also think that it's happening since the last Windows update. I've reported it here: microsoft/vscode-remote-release#3899 |
There was no firm indication whether the |
@therealkenc , @craigloewen-msft I have the same issue here : #6771 So is it possible to backport the fix in version 19xxx ? |
Is it possible to make this fix also available for the 20H2 release (19042.867). We do nut use Insider builds on our company PCs. |
This issue is not done and still present. I do not know why this is closed. I have to do this every boot to get internet in WSL2. |
Experiencing a similar issue... usually happens when i plug in or unplug a ethernet cable while im connected to a wifi, LxssManager just hangs on restart and doesn't wanna stop, I basicly have to restart my machine every time i need to plug in an ethernet cable, the WSL2 basicly becomes useless for me if i don't |
When that happens to me I use Resource Monitor to terminate the entire process tree and allow it to restart. If it doesn't restart in a few seconds, I start it using Services. Have to do it less than I used to but it still happens from time to time. |
Not sure if this is the same issue but the internet connectivity inside of wsl2 is incredibly intermittent. Instead of straight up not working until I need a manual solution it stops working and I have to wait a couple minutes then try whatever I was doing again. |
Try setting the HNS service to automatic. You also may need to reset your networking. After doing both, I haven't seen that issue. I'm now on the latest build. |
@onomatopellan thanks for the pointer. Indeed, it seems there was still an issue with Undoing the compression on |
Thanks, this works fine for me, Windows 11 Home Single Language V 22H2 Build 22621.1702 |
Why is this issue closed? I just faced this on latest windows build (22H2 / 22621.2134). Computer goes to sleep and after wake up, WSL2 (ubuntu) loses access to DNS resulting in no internet connectivity. |
22621.2134 isn't the latest build. You're actually several updates behind. Update to at least one more revision higher than 22621.2134 and try again. I'm not involved with the Windows Preview program due to the machine being too old and I am at 22H2 / 22621.2215. I have not seen this above issue for some time. |
And it was working fine before. Why push broken builds like this on to people? Since this issue happened before on windows TEN, why there isn't a test to catch this? how did it happen again in 22621.2134? ridiculous. |
There are many permutations in hardware and software that can result in such a problem cropping up on a system unexpectedly. Programmers sometimes end up with a code regression. But sometimes they don't catch it if they don't have the same combination of hardware and software that you are using. But your build still is behind. You should update. You also can try updating WSL before updating your build to the current public release of Windows 11. In a terminal or powershell prompt, run: wsl --update or wsl --update --pre-release Then, shutdown WSL and restart it. |
Any working solution for this |
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).
The text was updated successfully, but these errors were encountered: