WSL: Very slow network speeds
Version
Microsoft Windows [Version 10.0.22000.556]
WSL Version
- WSL 2
Kernel Version
5.10.60.1
Distro Version
Ubuntu 20.04
Repro Steps
- Install branch latest version of windows 11 (just did a complete reinstall of my computer)
- Install everything wsl2 related from the docs (I did this twice to ensure it was not a faulty setup)
- Install NVM from the docs
- Try to download a node env (very slow speeds)
- Try to download the same tar using curl instead (also very slow speeds)
Downloading this from windows is almost instant.
Speedtest in my windows environment:

Speedtest in my WSL environment
$ speedtest
Retrieving speedtest.net configuration...
Testing from REDACTED...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by REDACTED [28.19 km]: 44.639 ms
Testing download speed
Download: 788.47 Mbit/s
Testing upload speed
Upload: 137.57 Mbit/s
Expected Behavior
I would expect it to not be much slower than my host machine.
Actual Behavior
~4 hours for 14mb makes it quite unusable…

Diagnostic Logs
Let me know if I should include the networking diagnostic from windows as well, they are long, so I did not add it.
WSL Networking Summary:
paul@PAUL-DESKTOP:~/temp/wsl/diagnostics $ ./networking.sh
If you see 'ping: socket: Operation not permitted' errors, run this command as root.
+ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.4 LTS
Release: 20.04
Codename: focal
+ uname -a
Linux PAUL-DESKTOP 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
+ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d2:c0:01:6a:1b:ed brd ff:ff:ff:ff:ff:ff
3: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 76:4b:c8:32:c2:9a brd ff:ff:ff:ff:ff:ff
4: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1350 qdisc mq state UP group default qlen 1000
link/ether 00:15:5d:7c:a2:af brd ff:ff:ff:ff:ff:ff
inet 172.30.22.56/20 brd 172.30.31.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::215:5dff:fe7c:a2af/64 scope link
valid_lft forever preferred_lft forever
+ ip route show
default via 172.30.16.1 dev eth0
172.30.16.0/20 dev eth0 proto kernel scope link src 172.30.22.56
++ ip route show
++ awk '/default/ { print $3 }'
+ gateway=172.30.16.1
+ ping -c 4 172.30.16.1
PING 172.30.16.1 (172.30.16.1) 56(84) bytes of data.
--- 172.30.16.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3097ms
+ ping -c 4 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=18.6 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=19.0 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=18.8 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=18.7 ms
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 18.639/18.811/19.028/0.143 ms
+ traceroute 1.1.1.1
./networking.sh: line 28: traceroute: command not found
+ cat /etc/resolv.conf
nameserver 8.8.8.8
+ type curl
+ curl -m 5 -v https://microsoft.com
* Trying 104.215.148.63:443...
* TCP_NODELAY set
* Connected to microsoft.com (104.215.148.63) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=US; ST=WA; L=Redmond; O=Microsoft Corporation; CN=microsoft.com
* start date: Jan 24 04:39:56 2022 GMT
* expire date: Jan 19 04:39:56 2023 GMT
* subjectAltName: host "microsoft.com" matched cert's "microsoft.com"
* issuer: C=US; O=Microsoft Corporation; CN=Microsoft Azure TLS Issuing CA 06
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55dc5d401880)
> GET / HTTP/2
> Host: microsoft.com
> user-agent: curl/7.68.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 301
< date: Sat, 19 Mar 2022 09:44:03 GMT
< location: https://www.microsoft.com/
< server: Kestrel
< content-length: 0
< strict-transport-security: max-age=31536000; includeSubDomains
<
* Connection #0 to host microsoft.com left intact
About this issue
- Original URL
- State: open
- Created 5 years ago
- Reactions: 22
- Comments: 33 (1 by maintainers)
I tried everything and finally I could solve it:
/etc/resolv.conf→ Not workingFinally I tried to disable IPv6 from the vEthernet of WSL and in W11 doesn’t appears listed in the control panels, reading GitHub I found out that is because is a hidden device, from PowerShell I managed to disable it and right now WSL is has regular network speeds, the command:
Disable-NetAdapterBinding -Name "vEthernet (WSL)" -ComponentID ms_tcpip6 -IncludeHiddenFor those of you that can’t easily disable the “Large Send Offload Version 2 (IPv4)” (or IPv6) because the WSL adapter is hidden in the control panel, here are the steps I took to disable this setting via powershell: (full disclosure: I have zero understanding/comprehension of what this setting does… so I’m essentially pressing buttons at random)
In PowerShell:
get-netadapterThis will give you a list of network adapters on your system:
Next, run the following command to view the advanced properties of the “vEthernet (WSL)” adapter:
Get-NetAdapterAdvancedProperty -Name "vEthernet (WSL)" | Format-Table -AutoSizeHere, you can see that this setting had a value of 1, which I speculate maps to “enabled”.
Next, change the value to “Disabled”:
Set-NetAdapterAdvancedProperty -Name "vEthernet (WSL)" -DisplayName "Large Send Offload Version 2 (IPv4)" -DisplayValue Disabled.I applied this change and network speed in my WSL environment seemed to have improved.
I solved the problem by trying the following (Windows 11 Home).
try this once
PASTE ON POWERSHELL
Restart WSL Network Adapter
PASTE WSL Distro (Ubuntu)
upload speed
Just restarting the WSL network adapter worked for me. Had 5Mbps upload speed, after restart back to normal speeds (>800Mbps)
In Administrator Powershell:
Restart-NetAdapter -Name "vEthernet (WSL)" -IncludeHiddenDid you try with this? It absolutely worked for me
https://townsyio.medium.com/wsl2-how-to-fix-download-speed-3edb0c348e29
I also experienced inconsistent and slow network speed with my ASUS XG-C100C.
Disabling IPv6 on the network adapter gave me expected network speeds in WSL2
This works for me:
1- Press the Windows Key and type “Control Panel” and hit enter 2- Click “Network and Internet” 3- Click “View network status and tasks” 4- Click “Change adapter settings” 5- Find the “vEthernet (WSL)” adapter and click properties 6- Click “configure” and open the advanced tab
Note: 2 and 3 might be under “Network and Sharing Center” in the Control Panel
Select “Large Send Offload Version 2 (IPv4)” and change the drop-down to disabled. To the same for “Large Send Offload Version 2 (IPv6)”.
Once this is done click “OK” and you are all done. You may experience a slight downtime in connection while this is saved.
Looks like disabling TCP Segmentation Offload inside WSL/Linux also works:
Credit: https://github.com/microsoft/WSL/issues/4901#issuecomment-1580750148
That fixed my upload speed being really slow.
Thanks, the only response that works for us since we are running WSL on Windows 11 Pro where vEthernet adapters are hidden. So I executed:
Set-NetAdapterAdvancedProperty -Name "vEthernet (WSL)" -IncludeHidden -DisplayName "Large Send Offload Version 2 (IPv4)" -DisplayValue Disabled… and voilà… from 0-60kb/s to fullspeed
I have tried so many things by now. The one that fixed it for me was:
Admin PowerShell:
wsl --shutdownDisable-NetAdapterLso -IncludeHidden -Name "vEthernet *"I refactored that a bit to be more verbose
I woke up this morning and found that my Windows box had been “updated”. I also saw that my WSL speeds were slow again. I opened up this thread and followed the steps in my previous post and immediately saw the download speeds increase:
This is really bad. This suggests that updates are wiping out the workout that people are using.
Had to include “| Format-Table -AutoSize” to get the full adapter name:
get-netadapter -IncludeHidden | Format-Table -AutoSize | Where-Object Name -like "vEthernet (WSL (Hyper-V firewall))" | Get-NetAdapterAdvancedProperty -IncludeHidden | Where-Object DisplayName -like "Large Send Offload Version 2*" | Set-NetAdapterAdvancedProperty -DisplayValue DisabledThis is getting silly, I’ve had to “fix” this countless times now. Which is only possible due to this thread. So I had to modify the above instructions by @peterfelts and @davorpa as there seems to have been a new change. The adapter is now hidden from
get-netadapter, and might have a different name.I’ve made the assumption that the adapter will start with vEthernet and have WSL somewhere else following in the name. With that in mind here is a combined query to get the properties to check your setup
To check only for LSOv2, you can run just the below
Now to disable tjhe properties for both ipv4 and ipv6
For me restarting the WSL adapter does not work. What worked is deactivating the wifi adapter in windows network control panel and activating it again, then it gained full speed, until it worked again.
@paul-vd What version of Windows/WSL are you running? There are a few reports of this issue going away in 22H2 (around version 10.0.22623.730 or later).
wsl --versionshould give enough information.