In the VBox.log I always see this line:
HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
I've tried a number of things that seem to be the typical recommendations:
- Remove Hyper-V
Remove WSL2
bcdedit /set hypervisorlaunchtype off
Unfortunately, no. There's no VT-x/AMD-V user scanner that we know of. But to the best of our knowledge, only active host Hyper-V causes the error you're seeing.Davidian1024 wrote:if there's a way to tell what's making use of VT-x and therefore preventing VirtualBox from using it.
No need, and pointless since you already noted that it doesn't work. Just follow the link that Scott provided. The magic bullet is the "bcdedit /set hypervisorlaunchtype off" command, provided it is followed by a full reboot from power off.Davidian1024 wrote: This link takes you to where you need to go to get the tool that can disable it:
No, the magic bullet was not "bcdedit /set hypervisorlaunchtype off" followed by a full reboot from power off. I tried that, several times, it did not work.mpack wrote:No need, and pointless since you already noted that it doesn't work. Just follow the link that Scott provided. The magic bullet is the "bcdedit /set hypervisorlaunchtype off" command, provided it is followed by a full reboot from power off.Davidian1024 wrote: This link takes you to where you need to go to get the tool that can disable it:
Then your PC is unique. Meanwhile the rest of us who use standard Win10 PCs have a few years of experience with this subject matter, and we know what works. That's why we put it in a FAQ response.Davidian1024 wrote: No, the magic bullet was not "bcdedit /set hypervisorlaunchtype off" followed by a full reboot from power off. I tried that, several times, it did not work.
Ah, the one shield to the silver bullet. Previously mentioned in the "Attempting fall back to NEM" tutorial. If IT forces it on, it's good MS gave a way to turn it off per boot. IT will block that soon as they find out you're using it, so ixnay on iscussingday that ooltay with your oworkerscay.Davidian1024 wrote:my corporate IT department
InfoSecDr wrote: I have followed all of the instructions explicitly to no avail. Multiple times. I even checked the registry to verify that DeviceGuard is not enabled. However, I did discover one registry setting that is not mentioned in any of the published instructions that was set to enabled.
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\SystemGuard
I set the Enabled REG_DWORD value to 0 and rebooted the machine. Now msinfo32 shows that virtualization-based security is not enabled. I started VirtualBox and the turtle is gone and the V icon is there.