Reset your WSL network connection trying to fix WSL2 media disconnected error

WSL2-Net-Fix.ps1

# Check these threads before proceeding:
# https://github.com/microsoft/WSL/discussions/5857
# https://github.com/microsoft/WSL/issues/5821
if (-Not ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator')) {
  $CmdLine = "-File `"" + $MyInvocation.MyCommand.Path + "`" " + $MyInvocation.UnboundArguments
  Start-Process -FilePath PowerShell.exe -Verb Runas -ArgumentList $CmdLine
  Exit
}
# Restart the Host Network Service 
Restart-Service -Force -Name hns
# Restart the Windows Subsystem for Linux Manager
Restart-Service LxssManager
# Restart the WSL Network adapter
Restart-NetAdapter -Name "vEthernet (WSL)"

Restart-NetAdapter -Name "vEthernet (WSL)" cannot be run because vEthernet (WSL) is gone when Restart-Service LxssManager.

But, when I start my windows terminal, then open Ubuntu WSL, I can restart the vEthernet (WSL). Is it common behavior? Because it's like everytime I shutdown the WSL, then the hyper-v adapter is also gone.

This script is working for me, many thanks, I have seen the case where "vEthernet (WSL)" disappears not sure why, if I run "wsl --shutdown" and the adaptor still shows up,

Restart-NetAdapter -Name "vEthernet (WSL)" cannot be run because vEthernet (WSL) is gone when Restart-Service LxssManager.

But, when I start my windows terminal, then open Ubuntu WSL, I can restart the vEthernet (WSL). Is it common behavior? Because it's like everytime I shutdown the WSL, then the hyper-v adapter is also gone.

@Rizary Does it help if you restart the adapter before Lxss ?

Restarting eventually fixed it for me - I had to toggle WSL integration on/off for my distro after reboot. Also realizing that toggling on Windows-container mode broke WSL networking again...

I added

wsl --shutdown
wsl ping google.com -c 4

At the end just to check that the wsl internet connection works at the end

Thanks
It's working for me. Is there any permanent solution?
This is very dangerous and annoying.

It worked for me. Thx

It worked for me. Thx

What exactly did you get to work I'm having mixed luck using this script, what version of windows are you currently running

I'm using the insider dev version of windows 10. You have to close all the terminals.

…

On Wed, Sep 23, 2020 at 4:14 AM Mark Wood-Patrick ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ It worked for me. Thx What exactly did you get to work I'm having mixed luck using this script, what version of windows are you currently running — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://gist.github.com/9486bf730371436131cb888ff4c2ceb6#gistcomment-3464260>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE47UPB6XYGQ3OJSQSL2WI3SHHKADANCNFSM4Q3WT6UA> .

It didn't work for me.
I had to add a firewall rule to whitelist the Network Interface.

This is a godsend!

This did the trick for me!

This works :) I initially copy pasted your code directly into PowerShell terminal and it didn't work. Then I created a separate .ps1 file and ran it and then it worked. Thanks!

This is works.
Thanks

I added

wsl --shutdown
wsl ping google.com -c 4

At the end just to check that the wsl internet connection works at the end

This fixed things for me, Thank you!

After 1h30 of trying everything on stackoverflow, this worked ! I am surprised this is still needed and still works after 2 years.

@dtraparic Happy that it help you. I'm also surprised that it's still relevant.

Thank you so much! You saved me an entire day of frustration. I was stuck reconfiguring IPs, default routes, interface preferences, restarting LxssManager, my PC, and WSL multiple times. Even when everything seemed perfectly set up, nothing worked.

I ran your script, restarted my WSL instance, and suddenly everything went back to normal. The key component I was missing was:

Restart-Service -Force -Name hns

For those interested in why this works:

The Host Network Service (HNS) is a critical component in Windows that manages network virtualization and container networking. It's responsible for creating and managing virtual networks, including the one used by WSL.

When HNS encounters issues or gets into an inconsistent state, it can cause networking problems for WSL, even if all the configurations look correct. Restarting HNS forces it to reinitialize, which can clear up any stuck or inconsistent states.

This script effectively performs a "hard reset" on the networking components related to WSL:

1. It restarts HNS, clearing any network virtualization issues.
2. It restarts the LxssManager, which manages WSL instances.
3. It restarts the WSL network adapter, ensuring it's in a clean state.
4. Finally, it shuts down all WSL instances, forcing them to reinitialize their network stack on next start.

This comprehensive approach addresses multiple potential points of failure in the WSL networking stack, which is why it's so effective at resolving complex networking issues that persist even after seemingly correct configuration.

Again, thank you for sharing this solution. It's a real time-saver for anyone encountering stubborn WSL networking problems!

Thank you @hadamrd
Your additional information will help users too.

Thanks God this script save my life :)))

wsl ping google.com -c 4

thanks man, all that I needed to do was ping and it just setup a new IP and Adapter by itself