I didnt see a specific area to post stuff about virtualization so here goes.
I am getting the “Virtual machine could not be started because the hypervisor is not running.” error when attempting to start VM’s from Hyper-V and further getting the “Please enable the Virtual machine Platform Windows feature and ensure virtualization is enabled in the BIOS.” message when trying to launch my Kali WSL instillation.
The problem is that virtualization is enabled and confirmed working by the host OS windows 10. I have verified it is enabled in the BIOS.All the Hyper-V stuff is checked in services and Hyper-V Virtual machine Management is listed as Running and set to Automatic.
The only thing I can think of is that I registered this copy of Windows somewhat recently and i dont think but am not sure if I have been able to run a VM since then since I dotn run VM’s often anyways… Does any one have any ideas? Maybe I should disable and re-enable HyperV in windows features?
I also tried installing Docker and it failed to function after install I dont recall the exact message because I removed it to confirm that Hyper-V is not functioning. Also can Hyper-V function with docker?
Has it ever worked since enabling the Hyper-V feature, or has it been like this since initial setup?
Likewise, were the BIOS options turned on after installing Hyper-V (or, otherwise maybe flipped back off by a BIOS update since installing)?
You mentioned the Hyper-V features are enabled in the feature list. Are ‘Virtual Machine Platform’ and ‘Windows Hypervisor Platform’ also enabled?
Otherwise, all of the following get their best information when Hyper-V and/or other hypervisors aren’t present, but they may give some clues:
Check ‘coreinfo -v’ and make sure everything comes back with a * (present) rather than a - (missing) next to it. Coreinfo is part of Sysinternals – Coreinfo - Sysinternals | Microsoft Learn
Also check ‘bcdedit’ (requires a Run as Administrator terminal/powershell/cmd, but native in default Windows installs) and look for hypervisorlaunchtype. If it’s off, ‘bcdedit /set hypervisorlaunchtype auto’. Restart required afterwards.
Also, at the end of the ‘systeminfo’ output in a terminal it will show the Hyper-V requirements check. However it only does it when no hypervisor is present - so you’d be halfway to uninstall and reinstall then anyway.
1 Yes it was working and I have 3 VM’s that were working.
2 I dont think so. I always enable virtualization.
2 Hyper-V, Virtual machine Platform and Windows Hypervisor Platform are all installed.
coreinfo -v output reads
HYPERVISOR - Hypervisor is present
SVM * Support AMD hardware-assisted virtualization
NP * Support AMD nested page tables (SLAT)
bcdedit hypervisorlaunchtyp off
I checked this before but must have gotten info with bad syntax and it returned errors without the relevant info just saying it was non existent. Posting these things with the links to documentation is def a good call. Thx. Well see if this works… It probably will.
Tho I would be interested in any theory’s about how it might have gotten turned off as to avoid or be able to recognize when this might happen in the future…
Not 100% certain on why it might’ve changed, to be honest. Possibly an update, possibly the registration, from poking around a bit there’s also potential other things that might adjust those settings (type 2 hypervisors like vmware workstation or virtualbox, virtual display apps, etc.).
I tripped over these afterwards, but has a few maybes in the discussion: