-
Notifications
You must be signed in to change notification settings - Fork 822
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
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 |
I have the same issue but there was no clear action I took to trigger it explicitly (maybe a Windows update did). Just appeared. |
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 |
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 |
Me too. |
After a system recovery (from a restore point) the wls started to print this out.
The text was updated successfully, but these errors were encountered: