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/0x80370102 after update #10054

Open
1 of 2 tasks
bckelley opened this issue May 1, 2023 · 12 comments
Open
1 of 2 tasks

Comments

@bckelley
Copy link

bckelley commented May 1, 2023

Windows Version

10.0.19045.2846

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

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

.

@ghost
Copy link

ghost commented May 2, 2023

Thanks for reporting. We would love some /logs, please.

  • Start log collection
  • Reproduce the issue
  • Stop log collection and attach it to this bug.

@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!

@ghost
Copy link

ghost commented May 2, 2023

In powershell: What's the output of Get-WindowsOptionalFeature -online | Where-Object { $_.FeatureName -match "hyper" -or $_.FeatureName -match "linux"} ?

@bckelley
Copy link
Author

bckelley commented May 4, 2023

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

@andritcharthur
Copy link

I have the same issue

@benhillis
Copy link
Member

Looks like the virtual machine platform feature might be in a bad state. Could you please try disabling, and re-enabling it?

@bckelley
Copy link
Author

Looked a little deeper and upon opening ubuntu this message appears.

image

@XLPE
Copy link

XLPE commented May 17, 2023

I am also encountering the exact same problem. May I ask if you have resolved the issue? @bckelley

@XLPE
Copy link

XLPE commented May 17, 2023

I am also encountering the exact same problem. May I ask if you have resolved the issue? @bckelley

I resolved the issue !
To enable hypervisor run in an elevated powershell:
bcdedit /set hypervisorlaunchtype Auto

@bckelley
Copy link
Author

I am also encountering the exact same problem. May I ask if you have resolved the issue? @bckelley

I resolved the issue ! To enable hypervisor run in an elevated powershell: bcdedit /set hypervisorlaunchtype Auto

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.

@Thannix
Copy link

Thannix commented Sep 29, 2023

I am also encountering the exact same problem. May I ask if you have resolved the issue? @bckelley

I resolved the issue ! To enable hypervisor run in an elevated powershell: bcdedit /set hypervisorlaunchtype Auto

Thank you. this worked on me too.
Just need to run the command prompt on administrator mode

@TulioTsuruda
Copy link

I am also encountering the exact same problem. May I ask if you have resolved the issue? @bckelley

I resolved the issue ! To enable hypervisor run in an elevated powershell: bcdedit /set hypervisorlaunchtype Auto

It really solved my issue!
I think I encountered this problem after updating my Windows 11 with either release KB5032007 or KB4023057."

@github-actions github-actions bot mentioned this issue Oct 1, 2024
2 tasks
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

6 participants