-
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
Error code: Wsl/Service/CreateInstance/CreateVm/0x80370102 after update #10054
Comments
Thanks for reporting. We would love some /logs, please.
|
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:
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! |
In powershell: What's the output of |
WslLogs-2023-05-04_11-34-29.zip Get-WindowsOptionalFeature -online | Where-Object { $_.FeatureName -match "hyper" -or $_.FeatureName -match "linux"}
FeatureName : Microsoft-Windows-Subsystem-Linux
State : Enabled
FeatureName : HypervisorPlatform
State : Disabled
FeatureName : Microsoft-Hyper-V-All
State : Enabled
FeatureName : Microsoft-Hyper-V
State : Enabled
FeatureName : Microsoft-Hyper-V-Tools-All
State : Enabled
FeatureName : Microsoft-Hyper-V-Management-PowerShell
State : Enabled
FeatureName : Microsoft-Hyper-V-Hypervisor
State : Enabled
FeatureName : Microsoft-Hyper-V-Services
State : Enabled
FeatureName : Microsoft-Hyper-V-Management-Clients
State : Enabled |
I have the same issue |
Looks like the virtual machine platform feature might be in a bad state. Could you please try disabling, and re-enabling it? |
I am also encountering the exact same problem. May I ask if you have resolved the issue? @bckelley |
I resolved the issue ! |
Good to hear!! Yes, I did but leaving it open to hopefully get some insight from the Microsoft team as to why this happened in the first place. |
Thank you. this worked on me too. |
It really solved my issue! |
Windows Version
10.0.19045.2846
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.90.1
Distro Version
can't access wsl
Other Software
can't access wsl
Repro Steps
YOU UPDATED MY SYSTEM
Expected Behavior
FOR WSL TO START
Actual Behavior
[process exited with code 4294967295 (0xffffffff)]
Diagnostic Logs
.
The text was updated successfully, but these errors were encountered: