3

Just got a Surface Pro 7 and been pretty happy with it. However, when I tried to run a an Android emulator, I received an error saying that Hyper-V was enabled.

I went to go disable it, and here's where I ran into issues.

I undoubtedly have some form of hypervisor running.

System Info page shows that there is a hypervisor:

System Info page shows that there is a hypervisor.

However, from control panel in the "turn windows features on and off" panel, Hyper-V is not even an entry. Related items like Virtual Machine Platform and Windows Hypervisor Platform are unchecked.

Beginning of the list:

Beginning of the list

End of the list:

End of the list

Furthermore, trying to run the command

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor

in an elevated Powershell window following the instructions of this article gives an error saying that the specified feature is not found.

Powershell fails:

Powershell fails

I don't have any additional security software installed apart from Windows Defender. I'm trying to run MuMu emulator. I'm frankly at a loss as to what else to try at this point.

I know Microsoft is paranoid about security since IIRC they cited a potential vulnerability as their reason for not including Thunderbolt, so do Surface products have some sort of baked-in hypervisor functionality or something?

Bakr
  • 238
  • 3
  • 7

2 Answers2

2

Solution found. I blame MuMu devs being lazy and assuming any virtualization based issue was because of Hyper-V. The issue was not Hyper-V as the error message claimed but rather hardware virtualization being used by Memory Isolation in Windows Defender as well as Device Guard in Windows.

For any users googling around with a similar issue, I'll leave disabling Memory Isolation to the numerous other articles.

To disable Device Guard, open Regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard, then set the value for EnableVirtualizationBasedSecurity to 0.

Finally, in an elevated command prompt use the command:

bcdedit /set hypervisorlaunchtype off
Bakr
  • 238
  • 3
  • 7
1

Try this...

In an elevated Command Prompt write this :

To disable: bcdedit /set hypervisorlaunchtype off

To enable: bcdedit /set hypervisorlaunchtype auto

Just used it today to get VirtualBox working again after Microsoft wiped out my bcd boot record on an upgrade.

I got the information from this post