Numerous Virtual Box Errors after Windows 10 Home update

Hi. I’m running the latest LocalByFlywheel version on a laptop with Windows 10 Home. Windows 10 Home did a auto update and now LocalByFlywheel just hangs at ‘Starting Local Machine’. Installed the latest Virtual Box but to no avail. Did some research and found that Windows Hyper V need to be running for Virtual Box to work. Unfortunately Hyper V is not available Windows 10 Home but before the update LocalByFlywheel/Virtual Box worked. Tried uninstalled the new version of VirtualBox and installing the previous version(5.0) but that didn’t work. Now I don’t know what to do. I’ve got a few clients waiting on projects. Desperate for help!

Hey @sepia -

That doesn’t sound too good. Can you please provide your local-by-flywheel.log file? See this Community Forum post for instructions on how to do so:

There might be more information in there to help point us in the right direction!

Hi, Ben. I manage to solve my problem by researching some of the errors in GoogleLand. In VirtualBox, I went to ‘Settings’, selected ‘System’ in the list, chose the ‘Processor’ tab, and in ‘Extended Features’, checked ‘Enable PAE/NX’ and ‘Enable Nested VT-x/AMD-V’. The last selection was important because my laptop has a AMD processor.

1 Like

I’m glad you got it working!

You might also be interested in the latest version of Local (v5) which doesn’t rely on VirtualBox, and therefore doesn’t run into this kind of an error:

If I upgrade to version 5, will I lose all of my settings, websites, etc?

Hi @sepia,

Local Lightning is a separate application from Local by Flywheel so you will need to migrate your sites from Local by Flywheel.

Note: Local by Flywheel automatically exports the SQL file when the site is stopped/exported so you might be able to import the site from its folder. See for more details.

In other words, if I update Local By Flywheel, it would be in my best interest to backup my sites before updating. Also, what is "Local Lightning?

Hey @sepia

Local Lightning is what we were calling the work done to create a new version of Local that doesn’t rely on Virtual Machines. We did this because this new version is so different from the original version of Local by Flywheel.

Going forward, this “Local Lightning” will just be called “Local” and be the main Local application.

The old “Local by Flywheel” should still work for a while, but there won’t be active development happening on it.

When Clay mentions that these are separate applications, he means that you can have both installed at the same time and they won’t interfere with each other. One thing to note though, is that if you want the sites from “Local by Flywheel” to be moved over to “Local”, then you’ll need to export them from Local by Flywheel and then import them into “Local”

I know that’s a lot to take in, but I hope that helps clarify things. Let me know if you have any other questions!