-
Notifications
You must be signed in to change notification settings - Fork 852
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/CreateVm/ERROR_PATH_NOT_FOUND #10170
Comments
WslLogs-2023-06-07_17-57-29.zip I have attached WSL logs while attempting to install a distro above, as suggested here: https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs |
Thank you for reporting this @MatousKundrik. Looking at the logs it looks like Hyper-V is in a bad state, which causes the VM to fail to start. Can you try to disable both Virtual machine platform and all hyper-v components, then reboot, re-enable them and reboot again ? I'd be curious to see if that will solve the issue. |
Thanks for the feedback, seems you're exactly right! WSL + Ubuntu 22.04.2 LTS is now working as expected! 😁 For anyone else having the same issue, the exact steps I followed were:
WslLogs-2023-06-08_01-30-00.zip I was at my wits end and about to do an in-place reinstall of Windows, glad this worked! |
@MatousKundrik thank you very much, you save my day |
Windows Version
Microsoft Windows [Version 10.0.19045.3031]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
No response
Other Software
No response
Repro Steps
Unable to install WSL 2 distros. Can successfully install and access WSL 1 distro but attempting to update from 1 to 2 results in the following:
Attempting to install a WSL 2 distro directly results in the following:
I have tried installing various distributions both from the command line and from the Microsoft Store, all of which result in the same issue. Most relevant support I have found suggests ensuring Intel VT-x is enabled in BIOS (which I have verified to be the case) as well as enabling the correct Windows features, which I also believe I have done correctly.
The closest existing issue (#9349) I was able to find suggests clearing out missing values from
Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss
but that dosen't appear to be the problem in my case.This issue (#6363) also appears similar, unfortunately I have no
.wslconfig
present and making the suggested changes to the registry yielded no results.Expected Behavior
See Above
Actual Behavior
See Above
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: