WSL2 loses networking after resume from hibernate

[jamcpherson-clgx]

Windows Version

Microsoft Windows [Version 10.0.26100.3194]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-microsoft-standard-WSL2

Distro Version

Ubuntu 24.04

Other Software

Appgate SDP 6.4.1-39256-release
Zscaler 4.3.0.188

Repro Steps

I have a Dell Latitude 7450 with an "Intel Core Ultra 7" cpu, 32Gb ram.
Due to concerns about mis-interactions on resume with USB3 docking stations, $work has disabled sleep in the bios, leaving only hibernate.

I have noticed that after resume from hibernate my WSL2 vm is unable to make use of any network-related functionality - routing and DNS at a minimum.

The consistent misbehaviour is that I lose the ability to resolve DNS - and I cannot get any ICMP Reply packets when I ping lo or ping loopback0.

Sometimes after resume I can see traffic on the eth? interfaces - including both ICMP Request and Reply - but something is blocking the return path inside the VM for every packet. Other times I cannot see any traffic on the interfaces. I can also see that routes are getting updated but no traffic passes.

I've tried restarting systemd-networkd and systemd-resolved, setting the links down and then up, and even tried manually adding routes. Nothing works to get networking back.

I noticed this morning that running reboot in the VM does not bring the stack back up, I have to use shutdown -h.

Expected Behavior

I expect networking to "just work" after resuming from hibernation

Actual Behavior

WslLogs-2025-03-27_10-05-36.zip

Diagnostic Logs

pcaps.zip

[github-actions]

Failed to parse logs. Unexpected file: eth0-post-resume-restart.pcap
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

Multiple log files found, using: https://github.com/user-attachments/files/19478814/pcaps.zip
Found no WSL traces in the logs

[jamcpherson-clgx]

@github-actions bot - please re-scan the description

WslLogs-2025-03-27_10-05-36.zip

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.3.26.0

[alexandroid]

I am not sure if this is related or a different issue, but I have a somewhat similar issue which I think has started after installing Ubuntu system updates. After resuming my PC from sleep, my WSL2 terminal session works just fine and WSL shell can access internet, but the host Windows shell can no longer invoke wsl.exe:

]  wsl
Catastrophic failure
Error code: Wsl/Service/E_UNEXPECTED

This also breaks VSCode connectivity and requires complete wsl shutdown (wsl --shutdown) and then WSL restart. Attaching the minimal log (collected using the preferred method) of invoking wsl.exe and getting an error.

WslLogs-2025-03-31_23-13-32.zip

[LiPtP0000]

@alexandroid I experienced this when I was running MinerU in WSL distro with CUDA. vscode suddenly losed connection with WSL when processing a specific file and I tried to restart the connection (but not the restart of WSL) . After that the windows terminal shows exactly the same log as you. Maybe I could reproduce this problem later, and I would attach a log file at this issue then.

[tcostermans]

I experience the same issue after my system resumes from hibernate and WSL was still running:

I need to run wsl --shutdown and then start a terminal again.

[bestis]

One me too, to this that WSL2 is totally broken after hibernate. Running wsl --shutdown doesn't seem to fix all things related to WSL. Docker desktop seems to keep in borked state, trying to restart/quit it doesn't do anything so to fix the state is just easiest to reboot. Neither the VSCode seems to be able to reconnect or reload. So easiest seems to be just rebooting the whole system :(

@alexandroid What is this WSL restart you talk about after shutdown? At least for me, running shutdown and then having wsl running does not fix things.

[auroradanier]

I have the same issue too. I just got a new laptop. Now everytime wake up, I have to wsl --shutdown and reopen wsl inorder to connect to wsl from vscode or cursor.

[lukebehling]

++ 1 as this is impacting our developers as well.

[Einhorntom]

Same here.

Closing all the WSL windows/tabs and restarting it temporarily fixes the issue

[sirianni]

+1 this seems to be a regression as I had been running WSL with VScode for months without this issue. Now it seems to happen every time my PC wakes from sleep.

Related issues:

• Error code: Wsl/Service/E_UNEXPECTED #9490
• Errorcode Wsl/Service/E_UNEXPECTED #12810