Fails to load after Windows update

Support
1

I have checked my Task Manager to see if previous instances were running. I also tried the windows background issue fix for update 2.4.5. Neither solution has allowed me to get back to using Local. This is disappointing as this was my first day using the program. This is what I receive in the local-by-flywheel.log

Oct 31, 2018, 11:35 PM CDT - warn: [main/docker-machine] Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm local-by-flywheel --type headless failed:
Oct 31, 2018, 11:35 PM CDT - warn: [main/docker-machine] VBoxManage.exe: error: The virtual machine 'local-by-flywheel' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\MLanc\.docker\machine\machines\local-by-flywheel\local-by-flywheel\Logs\VBoxHardening.log'
Oct 31, 2018, 11:35 PM CDT - warn: [main/docker-machine] VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Oct 31, 2018, 11:35 PM CDT - warn: [main/docker-machine]  
Oct 31, 2018, 11:35 PM CDT - warn: [main/docker-machine] Details: 03:37:24.418874 Console: Machine state changed to 'Paused'
2

Hi Marious,

It looks like VirtualBox may not be initialized correctly. I recommend following the steps here: How can I manually update VirtualBox?

if the issue persists after reinstalling VirtualBox, you may need to go through the steps here: How can I forcefully restart the Local by Flywheel VM?

1 Like
3

Thank you Clay. I am currently implementing Step 2 and it looks like it might be the winner. I will keep you and the community updated if something else arises.

1 Like
4

I may have to simply uninstall and reinstall both Local and VirtualMachine

Nov 1, 2018, 10:23 AM CDT - error: [main/docker-create-machine] Error creating machine: Error in driver during machine creation: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm local-by-flywheel --type headless failed:
Nov 1, 2018, 10:24 AM CDT - error: [main/docker-create-machine] VBoxManage.exe: error: The virtual machine 'local-by-flywheel' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\Users\MLanc\.docker\machine\machines\local-by-flywheel\local-by-flywheel\Logs\VBoxHardening.log'
Nov 1, 2018, 10:25 AM CDT - error: [main/docker-create-machine] VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Nov 1, 2018, 10:25 AM CDT - error: [main/docker-create-machine]

These errors are occuring on the “Welcome to Local by Flywheel” screen. VirtualBox is checkmarked but the errors arise when Host Machine is in process.

5

Since you’re new to Local and don’t have any existing sites in Local, here’s what you can try.

Note to other readers: This will delete the site containers and site databases so you must have site backups if you have existing sites in Local.

  1. Quit Local if it’s running
  2. Open VirtualBox
  3. Right-click on local-by-flywheel and go to Close » Power Off if it is running
  4. Right-click on local-by-flywheel and click “Remove” then “Delete all files”
  5. Re-open Local

If the issue still persists, feel free to upload the following VirtualBox log file: C:\Users\MLanc\.docker\machine\machines\local-by-flywheel\local-by-flywheel\Logs\VBoxHardening.log

1 Like
6

Problem still persists. That file is not found either. It’s just a wash all together.

7

Bummer. Are you still running into the same errors in the local-by-flywheel.log error file as before?

8

@clay on the “Welcome to Local by Flywheel” screen? Yes. I did manage to locate the VBoxHardening.log so I have it below.

VBoxHardening.log (31.1 KB)

9

Is there any remote support possible for this product? I believe this is a great product and see the endless possibilities that can be done with it. I have only owned the product for 48 hours now and have only been able to access the project view 1 time so far. This is quite discouraging. I removed Virtual Box and chose to go with the installation through Local. I uninstalled and removed all traces of version 2.4.5 and installed 2.4.6 instead. The same issue persists.

Nov 1, 2018, 10:05 PM CDT - warn: [main/docker-machine] Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm local-by-flywheel --type headless failed:
Nov 1, 2018, 10:05 PM CDT - warn: [main/docker-machine] VBoxManage.exe: error: The virtual machine ‘local-by-flywheel’ has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in ‘C:\Users\MLanc.docker\machine\machines\local-by-flywheel\local-by-flywheel\Logs\VBoxHardening.log’
Nov 1, 2018, 10:05 PM CDT - warn: [main/docker-machine] VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

Whatever is going on, I believe Local is not optimized to run through the current iteration of Virtual Box despite the updates. I appreciate any and all assistance.

VBoxHardening.log (30.9 KB)

10

UPDATE: The new version is allowing me to get past the installation phase after uninstalling once more, restarting my laptop, and installing again. So progress. However, now I am encountering errors in retrieving the requested Docker image. This error is occurring whether I use the Preferred or Custom settings.

local-by-flywheel.log (145.4 KB)

1 Like