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

WSL doesn't see enabled virtualization #7676

Closed
1 of 2 tasks
k-zd opened this issue Nov 12, 2021 · 5 comments
Closed
1 of 2 tasks

WSL doesn't see enabled virtualization #7676

k-zd opened this issue Nov 12, 2021 · 5 comments
Labels

Comments

@k-zd
Copy link

k-zd commented Nov 12, 2021

Version

Microsoft Windows [Version 10.0.19043.1288]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

Kernel version: 5.4.72

Distro Version

Kali linux

Other Software

No response

Repro Steps

Everything was working fine. Don't know if I installed something (doubt it, because I did system restore to the point where I know WSL worked) but suddenly trying to start Kali on WSL, I'm getting error message:

`Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/wsl2-install

[process exited with code 4294967295]`

And from systeminfo, I see that everything is enabled:
Hyper-V Requirements: VM Monitor Mode Extensions: Yes Virtualization Enabled In Firmware: Yes Second Level Address Translation: Yes Data Execution Prevention Available: Yes

From Task Manager -> Performance = Virtualization: Enabled

Expected Behavior

Kali on WSL should start

image

Actual Behavior

image
Doesn't work

Diagnostic Logs

No response

@k-zd
Copy link
Author

k-zd commented Nov 12, 2021

After uninstalling VirtualBox and few restarts, everything is working now :/

@k-zd k-zd closed this as completed Nov 12, 2021
@Biswa96
Copy link

Biswa96 commented Nov 12, 2021

It is not required to uninstall VirtualBox.

  • Run this bcdedit /set {current} hypervisorlaunchtype off if you want to use VirtualBox.
  • Run this bcdedit /set {current} hypervisorlaunchtype auto if you want to use WSL2.

@k-zd
Copy link
Author

k-zd commented Nov 12, 2021

That wasn't the problem, this seems to make impact (don't know why yet):
image

When it's off WSL doesn't work, when ON it works, just tried few times

Previously there were no issues with that (Core Isolation was always OFF)

@k-zd k-zd reopened this Nov 12, 2021
@ghost ghost self-assigned this Nov 16, 2021
@ghost ghost added the bug label Nov 16, 2021
@DanPinGF
Copy link

Try turning off Hyper-V. Sometimes it can conflict with other virtualization-based software, from what I know so far.

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
Projects
None yet
Development

No branches or pull requests

3 participants