How to solve WSL2 error 0x803b0017?

[m-takahashi-lattice]

Windows Version

Microsoft Windows [Version 10.0.19045.2965]

WSL Version

1.2.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.90.1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

1. Enable "Virtualization Technology" in BIOS.
2. Run the following commands on CMD.exe as admin:

   > wsl --set-default-version 2
   > wsl --install
   

3. Then, wsl2 installs latest Ubunts and starts.
4. Exit Ubunts with exit command.
5. Exit CMD.exe with exit command.
6. Start CMD.exe again.
7. Run wsl command and get the following error:

   低下状態のオブジェクトに対する操作の試みがありました。
   Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x803b0017
   

Expected Behavior

Ability to access my WSL2.

Actual Behavior

Diagnostic Logs

No response

[benhillis]

/logs

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

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

Thank you!

[m-takahashi-lattice]

The attachment is logs output by collect-wsl-logs.ps1.
WslLogs-2023-06-02_16-56-15.zip

[kitag-personal]

Hello.
I also encountered the same error, but in my case I was able to start successfully after doing the following.

1. Run netcfg -d as Administrator.
2. Reboot the system.

[OneBlue]

@m-takahashi-lattice: I'm not seeing any WSL logs in the zip file you shared. Can you run the log collection while you reproduce the issue and share logs again ?

/logs

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

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

Thank you!

[microsoft-github-policy-service]

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-open it.

Thank you!

[microsoft-github-policy-service]

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-open it.

Thank you!