Power up failed - Can't start local

Support
1

Local 2.2.0 for Windows
Can’t Start the program. Getting the “Starting Local Machine” message and it’s stuck.

In the log file:

Dec 7, 2017, 4:21 PM GMT+2 - info: [main/index] Existing Pressmatic data does not exist.
Dec 7, 2017, 4:21 PM GMT+2 - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Dec 7, 2017, 4:21 PM GMT+2 - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Dec 7, 2017, 4:21 PM GMT+2 - info: [main/docker-machine] Checking Boot2Docker.iso hash
Dec 7, 2017, 4:21 PM GMT+2 - info: [main/docker-machine] Running  C:\Users\DoroNess\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Dec 7, 2017, 4:21 PM GMT+2 - info: [main/docker-machine] Starting "local-by-flywheel"...
Dec 7, 2017, 4:21 PM GMT+2 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Dec 7, 2017, 4:21 PM GMT+2 - warn: [main/docker-machine] Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm local-by-flywheel --type headless failed:
Dec 7, 2017, 4:21 PM GMT+2 - warn: [main/docker-machine] VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Dec 7, 2017, 4:21 PM GMT+2 - warn: [main/docker-machine] VBoxManage.exe: error: Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND)
Dec 7, 2017, 4:21 PM GMT+2 - warn: [main/docker-machine] VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
Dec 7, 2017, 4:21 PM GMT+2 - warn: [main/docker-machine]  
Dec 7, 2017, 4:21 PM GMT+2 - warn: [main/docker-machine] Details: 00:00:01.808649 Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, rc=E_FAIL (0X80004005))
2

Hi @doroness,

Sorry for the trouble!

Can you please try restarting your computer and then re-open Local?

3

Hey

Thank’s for your reply. Restarted my computer - Issue persists - machine won’t start.

Log entries:

Dec 7, 2017, 5:30 PM GMT+2 - info: [main/index] Existing Pressmatic data does not exist.
Dec 7, 2017, 5:30 PM GMT+2 - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Dec 7, 2017, 5:30 PM GMT+2 - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Dec 7, 2017, 5:30 PM GMT+2 - info: [main/docker-machine] Checking Boot2Docker.iso hash
Dec 7, 2017, 5:30 PM GMT+2 - info: [main/docker-machine] Running  C:\Users\DoroNess\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Dec 7, 2017, 5:30 PM GMT+2 - info: [main/docker-machine] Starting "local-by-flywheel"...
Dec 7, 2017, 5:30 PM GMT+2 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Dec 7, 2017, 5:31 PM GMT+2 - warn: [main/docker-machine] Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm local-by-flywheel --type headless failed:
Dec 7, 2017, 5:31 PM GMT+2 - warn: [main/docker-machine] VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Dec 7, 2017, 5:31 PM GMT+2 - warn: [main/docker-machine] VBoxManage.exe: error: Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND)
Dec 7, 2017, 5:31 PM GMT+2 - warn: [main/docker-machine] VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
Dec 7, 2017, 5:31 PM GMT+2 - warn: [main/docker-machine]  
Dec 7, 2017, 5:31 PM GMT+2 - warn: [main/docker-machine] Details: 00:00:02.585342 Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, rc=E_FAIL (0X80004005))
Dec 7, 2017, 5:51 PM GMT+2 - info: [main/index] Existing Pressmatic data does not exist.
Dec 7, 2017, 5:51 PM GMT+2 - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Dec 7, 2017, 5:51 PM GMT+2 - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Dec 7, 2017, 5:51 PM GMT+2 - info: [main/docker-machine] Checking Boot2Docker.iso hash
Dec 7, 2017, 5:51 PM GMT+2 - info: [main/docker-machine] Running  C:\Users\DoroNess\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Dec 7, 2017, 5:51 PM GMT+2 - info: [main/docker-machine] Starting "local-by-flywheel"...
Dec 7, 2017, 5:51 PM GMT+2 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Dec 7, 2017, 5:51 PM GMT+2 - warn: [main/docker-machine] Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm local-by-flywheel --type headless failed:
Dec 7, 2017, 5:51 PM GMT+2 - warn: [main/docker-machine] VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Dec 7, 2017, 5:51 PM GMT+2 - warn: [main/docker-machine] VBoxManage.exe: error: Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND)
Dec 7, 2017, 5:51 PM GMT+2 - warn: [main/docker-machine] VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
Dec 7, 2017, 5:51 PM GMT+2 - warn: [main/docker-machine]  
Dec 7, 2017, 5:51 PM GMT+2 - warn: [main/docker-machine] Details: 00:00:02.573062 Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, rc=E_FAIL (0X80004005))
4

Thanks for giving that a try.

No guarantees on this, but can you please try updating VirtualBox to 5.2.2? Here’s the direct download link to do so: http://download.virtualbox.org/virtualbox/5.2.2/VirtualBox-5.2.2-119230-Win.exe

Once you do that, re-open Local.

5

Hey

It Worked! Updating VirtualBox solved the issue

Thanks for your help!

6

Just wanted to add, if anyone else has had a similar problem since the latest Windows Creator update, the link to the new VirtualBox update in this thread got me working again too.

Thanks!