Can not install any distro, can not use WSL2 or 1 at all, nothing is working in WSL
Windows Version
Microsoft Windows [Version 10.0.26100.4061]
WSL Version
2.5.7.0
Are you using WSL 1 or WSL 2?
- [x] WSL 2
- [ ] WSL 1
Kernel Version
No response
Distro Version
No response
Other Software
Docker version 28.1.1, build 4eba377 Docker Client: Version: 28.1.1 API version: 1.49 Go version: go1.23.8 Git commit: 4eba377 Built: Fri Apr 18 09:53:24 2025 OS/Arch: windows/amd64 Context: desktop-linux
Repro Steps
- installed all the required components for WSL by turning windows features on
- Opened PowerShell as Admin
- Ran Command 'wsl.exe --install Ubuntu-24.04'
- The distro started downloading
- Error produced: WSL2 is not supported with your current machine configuration. Please enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS. Enable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution For information please visit https://aka.ms/enablevirtualization Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
Expected Behavior
I believe after running the command 'wsl.exe --install Ubuntu-24.04', it should download the Linux and then install it with no errors
Actual Behavior
Error produced: WSL2 is not supported with your current machine configuration. Please enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS. Enable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution For information please visit https://aka.ms/enablevirtualization Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
Diagnostic Logs
Diagnostic information
.wslconfig found
Detected appx version: 2.5.7.0
Detected user visible error: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
I have virtualization on in BIOS
I have Windows 11 Home edition with 24H2 version
@AshKot1 - I have seen cases where virtual machine platform looks like it is enabled, but it is not. Could you please try disabling the feature, and re-enabling it?
@benhillis - I have done that, I have done following actions: Through GUI use turned off the 'virtual machine platform', rebooted the system. Again Turned on the 'virtual machine platform', rebooted the system. Still following is the response: WSL2 is not supported with your current machine configuration. Please enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS. Enable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution For information please visit https://aka.ms/enablevirtualization Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
The system is officially broken!
The Ubuntu installation does not work, Docker does not work, nothing works!
AshKot1 have you done what the system wants? That is gone into the BIOS (or its equivalent for your system) and confirmed that the virtualization functions are enabled?
WSL2 is not supported with your current machine configuration. is a symptom of virtualization not being available.
Can you double check that all CPU virtualization extensions are enabled in the BIOS ?
it seems that your hyperV is not installed that's why it is saying that it doesn't have but virtual machine platform but you have virtual machine platform Enabled you need height will be installed to install it you need to go to turn windows features on or off and turn on hyperv then click apply and after it finishes. Restart and then wsl --shutdown and then it should work
it seems that your hyperV is not installed that's why it is saying that it doesn't have but virtual machine platform but you have virtual machine platform Enabled you need height will be installed to install it you need to go to turn windows features on or off and turn on hyperv then click apply and after it finishes. Restart and then wsl --shutdown and then it should work
I'm using Windows 11 Home edition. Hyper-V is not viable on home edition of win11. I do have hypervisor platform active, but that does not work either. it is been on and off multiple times, multiple times the windows been restarted, and every time after rebooting it does not work at all.
@OneBlue Yes, I have checked it multiple times by going into BIOS. At first, both technologies, the VT-x and VT-d were on, still I decided to turn off rebooted the machine, again rebooted the machine, while rebooting went to BIOS, turned both tech back on, and booted to win11. However, still no does not work!
The problem is in win11 24H2 Update, it broke something inside, and now whole virtualization does not work! and I can't even rollback, since the update past the 10 days window. outside of that 10 day window, if anyone know how to rollback, I'm happy to listen/learn.
I believe the cautionary tale is that, DON'T UPDATE THE WINDOWS. If Microsoft claims that not updating will compromise the security of the windows. Well by updating, I'm compromised on my work.
@DoctorWho8 Yes, I have done that. Multiple times! Still does not work. The problem is in win11 24H2 Update, it broke something inside, and now whole virtualization does not work! and I can't even rollback, since the update past the 10 days window. outside of that 10 day window, if anyone know how to rollback, I'm happy to listen/learn.
@AshKot1 In an elevated powershell, what it shows when you run systeminfo at the last part, "Hyper-v Requirements"?
@OneBlue Yes, I have checked it multiple times by going into BIOS. At first, both technologies, the VT-x and VT-d were on, still I decided to turn off rebooted the machine, again rebooted the machine, while rebooting went to BIOS, turned both tech back on, and booted to win11. However, still no does not work!
Interesting. I wonder if other tools work. For instance can you create virtual machines with VMware or VirtualBox ?
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.
Thank you!