Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
reisraff opened this issue Nov 19, 2024 · 6 comments

Comments

@reisraff
Copy link

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

Image

Copy link

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

@HyperBrain
Copy link

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
Copy link

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
Copy link
Author

@flerxu
Copy link

flerxu commented Nov 21, 2024

Me too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants