Network boot mode is enabled, WSL2 cannot be accessed after hibernation startup

[cheezmil]

Windows Version

Microsoft Windows [Version 10.0.22631.6199]

WSL Version

WSL 版本: 2.6.3.0 内核版本: 6.6.87.2-1 WSLg 版本: 1.0.71 MSRDC 版本: 1.2.6353 Direct3D 版本: 1.611.1-81528511 DXCore 版本: 10.0.26100.1-240331-1435.ge-release Windows: 10.0.22631.6199

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

默认分发: Ubuntu-22.04 默认版本: 2

Distro Version

Release: 22.04

Other Software

No response

Repro Steps

Enable the network mirror mode in the settings. After the computer goes to hibernation and then starts up, WSL2 can never be accessed unless WSL2 is manually closed and reopened, which is very troublesome, that is, WSL2 must be restarted to access.

Expected Behavior

fix

Actual Behavior

Network boot mode is enabled, WSL2 cannot be accessed after hibernation startup

Diagnostic Logs

No response

[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'.