Closed Prashansa1998 closed 1 year ago
Try disabling virtual-machine-platform and windows-hypervisor-platform in windows features menu
It is turned off
The specific software or feature that's blocking it is not reported by Windows. Core Isolation, Credential Guard, Device Guard, some virtualization software, and even some anti-virus software block VirtualBox from accessing VT-x/AMD-V. The script does not provide an exhaustive list of all software that blocks VirtualBox, and VirtualBox doesn't (and probably can't) specify which software is blocking it, so troubleshooting this issue is up to you. People have reported that running the following command as administrator and rebooting twice usually solves the issue:
bcdedit /set hypervisorlaunchtype off
I tried the bcdedit command to turn off the hypervisor but still the issue is not resolved.
Remember to reboot twice. If that doesn't work, then something else is blocking VirtualBox from accessing VT-x/AMD-V, or possibly the CPU doesn't support these features.
Checking that VirtualBox starts the virtual machine without errors.
Checking that VirtualBox uses hardware-supported virtualization.
Virtualbox is not using hardware-supported virtualization features. Check that software such as Hyper-V, Windows Sandbox, WSL2, memory integrity protection, and other Windows features that lock virtualization are turned off. Exiting.
I am facing this issue while installing macos vm on my windows 10 machine. I tried the bcdedit command to turn off the hypervisor but still the issue is not resolved.