Downloaded local-by-flywheel-2-2-2-windows.exe - executed as Admin & standard - nothing happens except the “busy” thing. Can’t even close Windows Explorer.
Task Manager shows SmartScreen (whatever that is).
Help?
Hi Albert,
Can you please provide a screenshot of what you’re seeing?
Sorry for the trouble!
Actually, I see what’s going on.
Click on “More Info” and then “Run Anyway”.
I’ll make sure this is resolved ASAP.
Wasn’t seeing the “Run Anyway” but tried again and it appeared and I clicked on it.
But nothing else happens except the “working” hourglass thing. (tech term for it?)
Now I clicked on Task Manager and see an entry for "Asking for Permission"
but I cannot find any way to giver permission because there is nothing on the
task bar to click on! How can that be??? What am I missing?
Tried Local again - installed starting Local Machine
Removed VirtualBox 5.2.4 - rebooted - installed VirtualBox 5.2.6
tried again - stalled on starting Local Machine.
The Log file is the same as it has been since Local stopped working - see below.
Jan 25, 2018, 12:29 PM PST - info: [main/index] Existing Pressmatic data does not exist.
Jan 25, 2018, 12:29 PM PST - info: [main/check-system] Check System: Docker Machine:
{ stdout: 'Stopped\n', stderr: '' }
Jan 25, 2018, 12:29 PM PST - info: [renderer/CheckEnvPage] Check system promise response:
[ undefined, 'machine-halted' ]
Jan 25, 2018, 12:29 PM PST - info: [main/docker-machine] Checking Boot2Docker.iso hash
Jan 25, 2018, 12:29 PM PST - info: [main/docker-machine] Boot2Docker.iso hash does not match!
Jan 25, 2018, 12:29 PM PST - info: [main/docker-machine] Copying C:\Users\ALBERT WALTNER\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\boot2docker.iso to C:\Users\ALBERT WALTNER\.docker\machine\machines\local-by-flywheel\boot2docker.iso
Jan 25, 2018, 12:29 PM PST - info: [main/docker-machine] Running C:\Users\ALBERT WALTNER\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Jan 25, 2018, 12:29 PM PST - info: [main/docker-machine] Starting "local-by-flywheel"...
Jan 25, 2018, 12:29 PM PST - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Jan 25, 2018, 12:29 PM PST - info: [main/docker-machine] (local-by-flywheel) Windows might ask for the permission to create a network adapter. Sometimes, such confirmation window is minimized in the taskbar.
Jan 25, 2018, 12:30 PM PST - info: [main/docker-machine] (local-by-flywheel) Creating a new host-only adapter produced an error: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe hostonlyif create failed:
Jan 25, 2018, 12:30 PM PST - info: [main/docker-machine] (local-by-flywheel) 0%...
Jan 25, 2018, 12:30 PM PST - info: [main/docker-machine] (local-by-flywheel) Progress state: E_FAIL
Jan 25, 2018, 12:30 PM PST - info: [main/docker-machine] (local-by-flywheel) VBoxManage.exe: error: Failed to create the host-only adapter
Jan 25, 2018, 12:30 PM PST - info: [main/docker-machine] (local-by-flywheel) VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
Jan 25, 2018, 12:30 PM PST - info: [main/docker-machine] (local-by-flywheel) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
Jan 25, 2018, 12:30 PM PST - info: [main/docker-machine] (local-by-flywheel) VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp
Jan 25, 2018, 12:30 PM PST - info: [main/docker-machine] (local-by-flywheel)
Jan 25, 2018, 12:30 PM PST - info: [main/docker-machine] (local-by-flywheel) This is a known VirtualBox bug. Let's try to recover anyway...
Jan 25, 2018, 12:30 PM PST - warn: [main/docker-machine] Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue
hope this helps
Thanks! Also, thanks for your patience!
If you just re-installed VirtualBox, a restart of your PC may be required to make sure VirtualBox’s drivers are all up to speed.
Hi there.
I am getting the exact same error message as this line for line.
Tried reinstalling the latest version of Virtual box multiple times (including leftover registry items / files) Version 5.2.6 r120293 (Qt5.6.2). Have been trying for a full week now to get this sorted and no luck.
Log error is exactly the same word for word.
Is it possible there are some old VirtualBox files cached or could this be a more serious issue with the current Windows app?
I previously used Local on Windows home with no issues but since upgrading to Windows Pro, this has now happened - not sure if that could be related.
Microsoft Windows 10 Pro
10.0.16299 Build 16299
Thanks a ton for any help.
I wish I could help but my Windows 10 Pro stopped working after the Creators Update.
I met a man at a MeetUp whose system is up to date & Local by Flywheel is working.
I am disappointed – to say the least & not use bad language.
Yes tried latest Local & VirtualBox – no difference at all.
Albert Waltner - albertwwz@gmail.com - Reno, NV