It will load the elevated Command Prompt.
Resetting its launch type configuration should fix this issue.
If you already use VirtualBox v6+, it is possible that Hypervisor is not running correctly. So, update VirtualBox to the latest version to avoid this issue. However, VirtualBox 6 has introduced experimental support for Hyper-V. So it was impossible to use VirtualBox together with any applications that needed Hyper-V, such as Docker. Update VirtualBoxīefore, VirtualBox VMs would not run when Hypervision (Hyper-V) was active. You can do so from your BIOS/UEFI settings.Ĭheck out our article on How to Enable Virtualization in BIOS for more information. You must enable Virtualization in your system to operate the VirtualBox. Try the methods below to debug this issue: Enable Virtualization in BIOS/UEFI Its because Hypervisor conflicts with VirtualBoxs usage of virtualization resources in your system. If the error is due to Hypervisor, youll likely see VT-x or Hyper-V in the error messages. Result Code: E_FAIL (0x80004005) due to Hypervisor Here, replace with your user profile name and with the VM where you get this error.