Open ofoacimr opened 7 months ago
Failed to parse logs. Unexpected file: HKLM.txt The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
Found no WSL traces in the logs
thanks for reporting the issue
can you please collecting networking logs using instructions at https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues?
It will create a zip with name starting with "WslNetworkingLogs"
please make sure you have IPv4 connectivity before starting the logs and IPv4 connectivity is lost before stopping the logs
thanks
Windows Version
Microsoft Windows [Version 10.0.26100.268]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 20.04
Other Software
WSLg: 1.0.61 MSRDC: 1.2.5326 Direct3D: 1.611.1-81528511 DXCore: 10.0.26091.1-240325-1447.ge-release
Repro Steps
ip a
Expected Behavior
Always have IPv4 connection
Actual Behavior
Lose IPv4 connection