search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.53k stars 822 forks source link

wsl: Failed to configure network (networkingMode Nat), falling back to networkingMode VirtioProxy. #12297

Open reisraff opened 1 week ago

reisraff commented 1 week ago

After a system recovery (from a restore point) the wls started to print this out.

Image

github-actions[bot] commented 1 week ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.
reisraff commented 1 week ago

Log files

logs.etl.txt appxpackage.txt bcdedit.txt HKCU.txt HKLM.txt optional-components.txt P9NP.txt windows-version.txt Winsock2.txt wpr.txt wslservice.txt wslsupport-impl.txt acl.txt

HyperBrain commented 6 days ago

I have the same issue but there was no clear action I took to trigger it explicitly (maybe a Windows update did). Just appeared.

blaisemGH commented 6 days ago

I have this error message since the latest windows update (build 19045) about a week ago. The vmmem process started hanging, couldn't access it or stop it (tried both task manager and stop-process in PS, both had access denied). Restarting it with wsl --shutdown just hanged. I eventually stopped it with taskkill /f /im wslservice.exe. When it started up again, I had this error message.

reisraff commented 6 days ago

What had worked for me was to reset the network settings as follow https://answers.microsoft.com/en-us/windows/forum/all/how-to-reset-network-settings-in-windows-10/699e8f07-0e0d-4be3-9da9-f4094ff9746d

flerxu commented 5 days ago

Me too.

Kostovite commented 5 days ago

I just got this problem to day too 🥲, a network reset do fix it

flerxu commented 4 days ago

I just got this problem to day too 🥲, a network reset do fix it

Did not work.

illiafilipov commented 1 day ago

WSL version:

WSL version: 2.3.26.0 Kernel version: 5.15.167.4-1 WSLg version: 1.0.65 MSRDC version: 1.2.5620 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.2033

Resolved by switching to the 'Mirrored' networking mode in the WSL settings as follows: Image