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

Get a Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0xffffffff when restart the WSL after shutdown #11549

Closed
1 of 2 tasks
PinKevin opened this issue May 2, 2024 · 4 comments

Comments

@PinKevin
Copy link

PinKevin commented May 2, 2024

Windows Version

Microsoft Windows [Version 10.0.19045.2965]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu

Other Software

Visual Studio Code version 1.88.1 with Remote - SSH extension version v0.110.1

Repro Steps

I just want to connect to WSL via Visual Studio Code using the Remote-SSH extension, but it gives me error that looks like this: (the message is VS Code Server for WSL closed unexpectedly. Check WSL terminal for more details).
image

Then, I tried to reboot the WSL with wsl --shutdown and wsl. The first command was succeeded, but the second one got the error like the title (Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0xffffffff). I tried to set it using .wslconfig that I made first (because there is no such file in my directory), but it keeps giving me error.

Expected Behavior

I can connect to the WSL in VS Code

Actual Behavior

It gives me error:
Failed to configure network (networkingMode Nat). To disable networking, set wsl2.networkingMode=None in C:\Users\user.wslconfig
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0xffffffff

Diagnostic Logs

No response

Copy link

github-actions bot commented May 2, 2024

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 scipt will output the path of the log file once done.

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

View similar issues

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!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@PinKevin
Copy link
Author

PinKevin commented May 2, 2024

Copy link

github-actions bot commented May 2, 2024

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
.wslconfig found
Detected appx version: 2.1.5.0
Found no WSL traces in the logs

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

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

No branches or pull requests

1 participant