WSL2 has no internet access on Windows 10 build 19045.6332 (NAT broken, mirrored networking

[MohammedMogeab]

Windows Version

Windows version: 10.0.19045.6332

WSL Version

2.6.1.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

kali 2025.3

Other Software

No response

Repro Steps

Inside WSL2 (Kali), there is no internet connectivity.
Symptoms:

• ip route shows a default gateway (172.25.112.1).
• Cannot ping the gateway from WSL (ping 172.25.112.1 → 100% packet loss).
• Cannot ping external IPs (ping 8.8.8.8 → 100% packet loss).
• Cannot resolve DNS (ping google.com → fails).
• Host (Windows 10) has internet access normally.

What I tried

• wsl --shutdown and restart
• netsh winsock reset
• Restarted hns, vmms, LxssManager
• Removed & recreated the vEthernet (WSL) adapter
• Full reset of HNS database (Remove-Item C:\ProgramData\Microsoft\Windows\HNS)
• Reinstalled WSL
• Tried .wslconfig with networkingMode=mirrored, but this is not supported on Windows 10 build 19045.

None of these restored connectivity.

Expected Behavior

WSL2 should have internet access via NAT

Actual Behavior

WSL2 has no connectivity at all. WSL1 does have connectivity, but WSL2 is required for my work.

Diagnostic Logs

┌──(mohammed㉿DESKTOP-UBE0QVD)-[~]
└─$ ping -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2045ms

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[desertstsung]

I encountered a similar situation, have you got a solution yet?

[MohammedMogeab]

@desertstsung try to change the network that you are connecting to . If it doesn't work that mean the network give one internal ip to accessing internet

[desertstsung]

thanks for your advice. I'll try it later.

[MohammedMogeab]

Try it. if doesn't work .we will do it together.
DM MohammedMogeab

[desertstsung]

I tried changing internet adapter from ethernet to wireless USB, and also combined with nat or mirrored, the problem is still there, I cannot ping wsl's default route, which is not the same as ip a shows. BTW, I have already disable and re-enable WSL and VM before my try.