I wanted to try Android gaming emulators on my PC. Some of the recommended ones were Bluestacks (v4.260) and Memu (v.7.3.3), so I installed them. Bluestacks handled it fine and was able to run. Memu however said that it wont work with Hyper-V enabled and told me to repair. I searched around online and found that Memu is able to run with Hyper-V if Program Files\Microvirt\MEmuHyperv exists. I checked and it did, so I assumed repair would allow Memu to run with Hyper-V. Instead it just disabled it, but apparently in a somewhat harmful way I will soon discover. So I uninstalled it completely with Revo Uninstaller and reenable Hyper-V from the control panel. The problem is Bluestacks began to fail to recognize that Hyper-V is enabled and my ArchWSL2 instance started to crash on startup. I did reenable the necessary Windows (10 Pro) features and rebooted it. I tried reenabling it through cmd DISM and Admin Powershell. I checked Task Manager to see if virtualization was enabled. I checked services.msc and also the BIOS. All of them pointed that Hyper-V was enabled. So I decided to restore to a point that was a few hours ago, before all this emulator mess. But the problem still persists, Bluestacks won't start and Arch kept crashing. What the hell did Memu do to my computer?
Windows 10 – Hyper-V Not Recognized by Some Programs
bluestackshyper-vvirtualizationwindows 10wsl2
Related Solutions
Just to add a solution that worked for me:
If you are using the basic Window 10 HOME updated to the latest 2018 build level, VMware will not function, because some elements of Hyper-V are included, although they cannot be controlled.
In addition, many of the functions available in bcdedit and Powershell are not available with Windows 10 Home. For example, in Powershell, none of the vm cmdlts are available. Credential Guard/Device Guard are also not available. The Microsoft site solutions will not work. Even the so-called "Hypervisor readiness" do not run.
In "Programs" "Windows Functions" there are no selections for Hyper-V. There is only a generic tickbox for "Windows Hypervisor Platform".
However this sequence works:
untick "Windows Hypervisor Platform"
run bcdedit /set hypervisorlaunchtype off
reboot
steps 1-3 are not enough ! You must also deactivate the "Core Isolation" function in the Windows Defender Security Center.
Reboot again.
VMware will then function.
It is strange but interesting that "Core Isolation" also has an effect on some system drivers. With Core Isolation activated, my laptop CD/DVD drive was dead, Windows would not recognise its own native driver cdrom.sys. But everything returns to normal when Core Isolation is deactivated.
Did you enable the Memory Integrity option in the Core Isolation menu on Windows Defender? This option is available on Windows 1709 and later. Try disabling it. Here's the pic:
And if you see that you can't disable it because of the lack of administrator rights, even though you're the owner of the administrator account, go to this registry directory in regedit:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity
Then go to the right side pane, double click on the Enabled, change its value data from 1 to 0 and click OK to save changes.
Hope this helps.
Best Answer
Update or reinstall a fresh Windows OS. The ArchWSL network folder can be opened again and Bluestacks Hyper-V runs normally.