Local will not run anymore - Hyper-V conflict

Support
6

SOLUTION:
bcdedit /set hypervisorlaunchtype off

I have tried everything I could Google to get this working. So many solutions I found simply do not work for me.

  • A VirtualBox forum post suggests turning off the three main virtualization settings built-in to Windows. All three were already unchecked for me.
  • A Spiceworks post lists a few command-line sequences to run in both CMD and PowerShell. Tried these (and it took a long time to run them) without success.
  • An answer on StackOverflow says to try just enabling Hyper-V, rebooting, diabling Hyper-V, then rebooting again. Didn’t help.
  • Another answer on that same SO post suggests running a bcdedit command if the main bcdedit response shows that hypervisorlaunchtype was set to on or auto. Mine never showed up, so I initially disregarded this answer.
  • A GitHub post recommended I disable Secure Boot in the BIOS/UEFI. I felt that would be going too far, so I didn’t even bother trying it.

In the end, as a Hail Mary, I tried the bcdedit command suggested in the fourth link in the above list even though hypervisorlaunchtype didn’t appear at all when I ran bcdedit by itself. After running

bcdedit /set hypervisorlaunchtype off

and making sure that it was reported as such:

image
image1838×1020 39.4 KB

I rebooted and tried starting up Local by Flywheel. It takes a good 20–30 seconds now to start up the local machine, but at least I no longer get the errors and I can, indeed, create some WordPress test sites.

Perhaps this information should be made accessible to others who are also having this issue and for whom the typical fixes don’t work? I’ve seen it reported in many places.

1 Like