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: 0x80370102 The virtual machine could not be started because a required feature is not installed #8730

Open
1 of 2 tasks
ThePresence opened this issue Aug 17, 2022 · 6 comments

Comments

@ThePresence
Copy link

ThePresence commented Aug 17, 2022

Version

Microsoft Windows Server 2022

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

I'm running Windows Server 2022 base with container on AWS EC2 i3 instance.

Installed WSL using command
wsl --install
after installation, I've restarted the system, and I'm getting this error "Error: 0x80370102 The virtual machine could not be started because a required feature is not installed."

I've also tried enabling hyper-v but still the same issue.

Expected Behavior

Ubuntu installed successfully.

Actual Behavior

"Error: 0x80370102 The virtual machine could not be started because a required feature is not installed."

Diagnostic Logs

No response

@magicweirdoo
Copy link

magicweirdoo commented Aug 20, 2022

Try bcdedit /set hypervisorlaunchtype auto in CMD and then reboot.

@ThePresence
Copy link
Author

ThePresence commented Sep 13, 2022

Try bcdedit /set hypervisorlaunchtype auto in CMD and then reboot.

Hi @magicweirdoo ,

Thank you for the response, but I'm still getting the same error after running that command.

@Tao-2019
Copy link

Hi, I am having the same problem with my project, can you share your solution if you found it? thanks in advance.

@hisbanliu
Copy link

Has this problem been fixed?

@Tao-2019
Copy link

Tao-2019 commented Apr 11, 2024

Has this problem been fixed?

Yes, it was fixed. Solution is to pick different VM framework (With metal layer support) from AWS, then WSL2 can be installed.

@hisbanliu
Copy link

Has this problem been fixed?

Yes, it was fixed. Solution is to pick different VM framework (With metal layer support) from AWS, then WSL2 can be installed.

What should be done about Microsoft azure VMs?

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

4 participants