Setting up first site - can't access node-x64.exe or hosts file

Support Uncategorized
, ,
1

When setting up a new site I get error Windows cannot find ‘C:\Users[Username]\AppData\Local\Programs\local-by-flywheel\resources\extraResources\node\node-x64.exe’. Make sure that you typed the name correctly, and then try again.

I can browse to the exe file and it is there.

image
image1205×807 79.4 KB

The message is followed by a second error:

Uh-oh! Could not update the hosts file

Local ran into a problem when trying to update the hosts file.

Please ensure that the hosts file is not locked by antivirus.

image
image1183×796 75.7 KB

I have Kaspersky AV installed but disabled it and the same errors occur. Tried logged in as an administrator and the same errors occur.

Please advise.

2

Hi @letooth ,

Sorry to hear about these issues - could you please provide your local-by-flywheel.log file? See this Community Forum post for instructions on how to do so:

I’d be happy to take a look to see if I can spot any further detail that would point to a root cause here.

3

Hi everybody, i have the same problem setting up the first site: here is my log:

Aug 16, 2019, 11:27 AM GMT+2 - info: [main/EnvironmentLoader] Loading Environment: C:\Users\Tito\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-2\out\environment.js
Aug 16, 2019, 11:27 AM GMT+2 - info: [main/EnvironmentLoader] Successfully Loaded Environment: C:\Users\Tito\AppData\Local\Programs\local-by-flywheel\resources\extraResources\environments\flywheel-1-3-2\out\environment.js
Aug 16, 2019, 11:27 AM GMT+2 - info: [main/check-system] Check System: Docker Machine:  
{ stdout: 'Stopped\n', stderr: '' }
Aug 16, 2019, 11:27 AM GMT+2 - info: [renderer/CheckEnvPage] Check system promise response: 
[ undefined, 'machine-halted' ]
Aug 16, 2019, 11:27 AM GMT+2 - info: [main/docker-machine] Checking Boot2Docker.iso hash
Aug 16, 2019, 11:27 AM GMT+2 - info: [main/docker-machine] Running  C:\Users\Tito\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe start local-by-flywheel
Aug 16, 2019, 11:27 AM GMT+2 - info: [main/docker-machine] Starting "local-by-flywheel"...
Aug 16, 2019, 11:27 AM GMT+2 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Aug 16, 2019, 11:28 AM GMT+2 - info: [main/docker-machine] (local-by-flywheel) Windows might ask for the permission to configure a dhcp server. Sometimes, such confirmation window is minimized in the taskbar.
Aug 16, 2019, 11:28 AM GMT+2 - info: [main/docker-machine] (local-by-flywheel) Waiting for an IP...
Aug 16, 2019, 11:28 AM GMT+2 - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Aug 16, 2019, 11:28 AM GMT+2 - info: [main/docker-machine] Waiting for SSH to be available...
Aug 16, 2019, 11:28 AM GMT+2 - info: [main/docker-machine] Detecting the provisioner...
Aug 16, 2019, 11:28 AM GMT+2 - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Aug 16, 2019, 11:28 AM GMT+2 - info: [main/set-docker-env] Getting Docker Machine env.
Aug 16, 2019, 11:28 AM GMT+2 - info: [main/set-docker-env] Received Docker Machine env. export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.95.100:2376"
export DOCKER_CERT_PATH="C:\Users\Tito\.docker\machine\machines\local-by-flywheel"
export DOCKER_MACHINE_NAME="local-by-flywheel"
export COMPOSE_CONVERT_WINDOWS_PATHS="true"
# Run this command to configure your shell: 
# eval $("C:\Users\Tito\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe" env --shell bash local-by-flywheel)

Aug 16, 2019, 11:28 AM GMT+2 - info: [main/docker-machine] checking IP
Aug 16, 2019, 11:28 AM GMT+2 - info: [main/docker-machine] checked IP 192.168.95.100

thanks and sorry, im beginner.
Regards

4

Hi Tyler

Log is attached.

Thanks ,

Simon
local-by-flywheel.log (112.0 KB)

5

Sorry but i work in windows, not in linux

6

I have the same problem too. Need help please
There is my log file.
local-by-flywheel.log (32.8 KB)

Regards

7

im having the same error as this ever since the 3.3 update.
im even getting an error that host file cannot be updatesimage
image

i’ve already tried uninstalling and doing a fresh install
cleaned registry keys but still no luck

8

Hey @jjlim, @Luciuz, @vicentedb, and @letooth

Could you try disabling your anti-virus, and then reinstall Local? The node-x64.exe file may have been quarantined during an update or install.

Let us know if that works!

9

Hey there, wanted to share another possible solution from another thread. If this works for you let us know and we can pass this along to others who might have the same issue!

10

I’ve got the problem on Windows 7 so this won’t help I’m afraid

11

Hi @jkiley,
The node-x54.exe file isn’t quarantined. Anyway, I tried uninstalling, disabling anti-virus and reinstalling but the problem persists.

12

The above suggested method doesn’t help me either. and if it was the anti virus i should have gotten a pop up notification even during the installation if it quarantined a file or an infected file but that wasn’t the case. Im not sure either, but i think its something else. I even tried installing node.js from nodejs(dot)org but still no luck

13

i turned off my antivirus, uninstall flywheel, uninstaleld virtual box using ccleaner. and clean the reg keys that might also been left. but now it cant even install virtual box, i still have to download it and install separately and creating the host machine just keeps on spinning.

bu
bu1244×709 57.9 KB

bu2
bu21006×658 46.1 KB

bu3
bu31010×664 25.5 KB

bit1
bit1976×588 50.1 KB

bit2
bit2966×614 48 KB

im not sure but i feel like w/o proper support the rest of us still experiencing this problem will just get an “upgrade your account to local pro” to fix the problem :face_with_hand_over_mouth:

14

That is an interesting part about Windows 7 @letooth

@jjlim @Luciuz @vicentedb – are you also running Windows 7 when you get this error?

15

Yes Ben. I’ve got it working on a Windows 10 machine without issue. However, the Windows 7 box is my main machine and I just don’t have time to update it at the moment.

I’ve been suspecting that when the Windows 7 machine was domain joined in the past it had a policy to prevent exe files running in the AppData folders (an anti-ransomware measure). However, I have checked the GPO and no such policy is in place. I’ve also tried explicitly allowing the node-x64.exe run permissions in a GPO with no success.

16

Hi, any fix on this? I’m having the same issue, also working on windows 7

17

Same issue here, FYI. None of these solutions work.

DG

18

Checking in again. Anybody find a solution to this on a Windows 7 machine?

19

Alright, so I take it there will be no Flywheel solution for this is for Win7 OS?

DG

20

Hey All,
I spent hours trying to fix this ‘windows can not find node .x64’, and the VM issue mentioned above and I’m excited to share a solution that finally worked for me:

I downloaded an old version of FlyWheel, 3.0.2 and everything works fine for me now.
Didn’t need to change admin permissions.

My stack:
Windows 7,
VB: 5.2.26,
FlyWheel: 3.0.2
Node: 12.13.0