Sometimes your windows’ HyperV Hypervisor will refuse to start.
The problem is tricky because the services seems started if you check them. Also the installation is successful, virtualization is enabled and so on. So what is wrong?
Because Hyper-V is a type 1 hypervisor, it has to be started before the Windows kernel, much like Xen….
- Type 1 hypervisor: hypervisors run directly on the system hardware – A “bare metal” embedded hypervisor,
- Type 2 hypervisor: hypervisors run on a host operating system that provides virtualization services, such as I/O device support and memory management.
To diagnose the problen, you can fire a cmd.exe as administrator and type
and if hypervisorlaunchtype is not set to “Auto”, you can fix your troubles with:
bcdedit /set hypervisorlaunchtype auto