Stuck on Starting Local Machine after upgrade

Support
1

Hi Everyone,
After upgrading to 2.3.0 it’s starting to hang again on Starting Local Machine.

I have Windows 10 Machine with Bitdefender security installed

Error Log

Apr 20, 2018, 2:59 PM GMT+1 - info: [main/docker-machine] Starting "local-by-flywheel"...
Apr 20, 2018, 2:59 PM GMT+1 - warn: [main/docker-machine] C:\Program Files\Oracle\VirtualBox\VBoxManage.exe showvminfo local-by-flywheel --machinereadable failed:
Apr 20, 2018, 2:59 PM GMT+1 - warn: [main/docker-machine] VBoxManage.exe: error: Failed to create the VirtualBox object!
Apr 20, 2018, 2:59 PM GMT+1 - warn: [main/docker-machine] VBoxManage.exe: error: Failed to instantiate CLSID_VirtualBox w/ IVirtualBox, but CLSID_VirtualBox w/ IUnknown works.
Apr 20, 2018, 2:59 PM GMT+1 - warn: [main/docker-machine] VBoxManage.exe: error: PSDispatch looks fine. Weird
Apr 20, 2018, 2:59 PM GMT+1 - warn: [main/docker-machine] VBoxManage.exe: error: Details: code E_NOINTERFACE (0x80004002), component VirtualBoxClientWrap, interface

Thanks

Mark

2

Hi Mark,

Sorry for the trouble!

Can you please try manually upgrading to VirtualBox v5.2.8? Here’s the direct link to the installer/upgrader: https://download.virtualbox.org/virtualbox/5.2.8/VirtualBox-5.2.8-121009-Win.exe

Once you’ve done that, try the following:

  1. Open VirtualBox
  2. Check the status of local-by-flywheel
  3. If it’s on, right-click on it and go to Close » ACPI Shutdown
  4. Once local-by-flywheel is “Powered Off”, re-open Local
3

Hi Clay,
That did the trick thank you

Mark

1 Like
4