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

Error code: Wsl/Service/CreateInstance/CreateVm/ERROR_PATH_NOT_FOUND #10482

Closed
1 of 2 tasks
kevin820606 opened this issue Sep 16, 2023 · 5 comments
Closed
1 of 2 tasks

Comments

@kevin820606
Copy link

Windows Version

Microsoft Windows [Version 10.0.22621.2134]

WSL Version

1.2.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

Recently, I encountered a Windows update problem that crashed my computer several times, and I accidentally removed the virtual infrastructure driver, which made me face error code 0x8037012.
When I tried to fix the former problem, I reinstalled wsl by wsl --install and some other action, like re-enabling the virtual platform and hyper-v several times.
In the end, I fixed the problem by reinstalling VID with the device manager. However, after reinstalling the vid, I solved the situation above but met a new problem: "Error code: Wsl/Service/CreateInstance/CreateVm/ERROR_PATH_NOT_FOUND."
Because I do too many things, I need help figuring out what led to the problem I meet now.
Thanks for helping!

Expected Behavior

Normally start wsl.

Actual Behavior

Error code: Wsl/Service/CreateInstance/CreateVm/ERROR_PATH_NOT_FOUND

Diagnostic Logs

WslLogs-2023-09-16_21-14-00.zip

@kevin820606
Copy link
Author

I use strace wsl and got following result. Am I possible to know what file is it looking for?
image

@ghost
Copy link

ghost commented Sep 19, 2023

I'm not sure I know what you mean by strace wsl, strace is only going to capture what is going on in the guest.

You need to let the /log collection script run while running wsl --install or whatever the problematic commands are. I don't see anything in the traces attached.

@microsoft-github-policy-service
Copy link
Contributor

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!

@kevin820606
Copy link
Author

I have rerun the script. I notice that i did it wrong before. thanks!
WslLogs-2023-09-21_14-26-51.zip

Copy link
Contributor

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

Thank you!

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

1 participant