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

[reisraff]

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

[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 here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] 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]

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]

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]

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]

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]

Me too.

[Kostovite]

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

[flerxu]

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

Did not work.

[illiafilipov]

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:

[Anandha001]

i am not able to fix it even after network reset, uninstalled ubuntu, reinstalled ubuntu, installed kali nothing worked

[Artain]

For me worked to run
wsl --install --no-distribution
after a reboot of the host the network was working again.

[acagnetti]

same here, tried all workarounds here but nothing... I can connect to network from WSL but certain python apps do not work anymore (when connecting to some services in the WSL machine

[borjamunozf]

Same for one developer. It started to show that err and we cannot fix it:

Tried to:

• wsl --install --no-distribution
• Reinstall Windows Hypervisor Platform / Virtual Machine Platform / Windows Subsystem for Linux.

This is extremely annoying....

[vinsent2002]

Check if Virtual Machine Platform is installed on your device. For me Virtual Machine Platform was not installed after upgrading to Windows 11 24H2.
Enable-WindowsOptionalFeature -Online -FeatureName "VirtualMachinePlatform"

[markodraisma]

Same problem for me. Dns works, now that I've added 172.0.0.2 to the nameservers (using this fix), ping doesn't work. I've also tried to install another distribution (had Debian, added Ubuntu), hoping that it would add some missing adapter, but it has no effect.

[markodraisma]

I've tried many things, but I think that what finally worked for me was:

• update WSL2 to pre-release with wsl --update --pre-release
• remove Virtual Machine Platform from windows options, and add it again
• add the following to %UserProfile%/.wslconfig:

[wsl2]
dnsTunneling=false

• start /etc/resolv.conf with:
  nameserver 1.1.1.1

[unablem]

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:

Wsl Network True Ways thank you work