-
Notifications
You must be signed in to change notification settings - Fork 848
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
I can't use WSL2 #10469
Comments
I have the same issue!! |
2 tasks
2 tasks
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! |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Windows Version
Microsoft Windows [Version 10.0.22621.2283]
WSL Version
1.2.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
4.4.0
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
I run
dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
and
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
and reboot the computer.
wsl --set-default-version 2
wsl --install -d Ubuntu
error :
Installing, this may take a few minutes... WslRegisterDistribution failed with error: 0x80370102 Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. For information please visit https://aka.ms/enablevirtualization Press any key to continue...
check task manager and find that the vt bios is enabled
So how can I fix it?
Expected Behavior
I could download Ubuntu using WSL2 successfully
Actual Behavior
error :
Installing, this may take a few minutes... WslRegisterDistribution failed with error: 0x80370102 Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. For information please visit https://aka.ms/enablevirtualization Press any key to continue...
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: