Unable to Install Local by Flywheel on a new desktop windows PC

It looks like only part of the installation took place. When I go to open local I receive this error message (screenshot)

Capture

Here is the log:

Mar 1, 2018, 12:21 PM GMT - info: [main/index] Existing Pressmatic data does not exist.
Mar 1, 2018, 12:21 PM GMT - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘’,
stderr: ‘Host does not exist: “local-by-flywheel”\n’ }
Mar 1, 2018, 12:22 PM GMT - info: [renderer/CheckEnvPage] Check system promise response:
[ ‘virtualbox-not-ready’, ‘machine-does-not-exist’ ]
Mar 1, 2018, 12:28 PM GMT - info: [main/virtualbox-installer-windows] Starting VirtualBox Install…
Mar 1, 2018, 12:29 PM GMT - info: [main/virtualbox-installer-windows] VirtualBox installed!
Mar 1, 2018, 12:29 PM GMT - info: [main/docker-create-machine] Starting Docker Machine Creation…
Mar 1, 2018, 12:29 PM GMT - info: [main/docker-create-machine] USING IP: 192.168.95.1/24
Mar 1, 2018, 12:29 PM GMT - info: [main/docker-create-machine] Removing existing Docker Machine
Mar 1, 2018, 12:29 PM GMT - info: [main/docker-create-machine] null ‘About to remove local-by-flywheel\nWARNING: This action will delete both local reference and remote instance.\n’ ‘Error removing host “local-by-flywheel”: Host does not exist: “local-by-flywheel”\nCan’t remove “local-by-flywheel”\n’
Mar 1, 2018, 12:29 PM GMT - info: [main/docker-create-machine] Creating Docker Machine… --virtualbox-boot2docker-url=file://C:\Users\Dr Roderick Fahey\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\boot2docker.iso
Mar 1, 2018, 12:29 PM GMT - info: [main/docker-create-machine] Creating machine with
[ ‘create’,
‘–driver=virtualbox’,
‘–virtualbox-hostonly-cidr’,
‘192.168.95.1/24’,
‘–virtualbox-boot2docker-url=file://C:/Users/Dr Roderick Fahey/AppData/Local/Programs/local-by-flywheel/resources/extraResources/virtual-machine/vendor/docker/boot2docker.iso’,
‘–virtualbox-disk-size’,
‘120000’,
‘local-by-flywheel’ ]
Mar 1, 2018, 12:29 PM GMT - info: [main/docker-create-machine] Creating CA: C:\Users\Dr Roderick Fahey.docker\machine\certs\ca.pem
Mar 1, 2018, 12:29 PM GMT - info: [main/docker-create-machine] Creating client certificate: C:\Users\Dr Roderick Fahey.docker\machine\certs\cert.pem
Mar 1, 2018, 12:29 PM GMT - info: [main/docker-create-machine] Running pre-create checks…
Mar 1, 2018, 12:29 PM GMT - error: [main/docker-create-machine] Error with pre-create check: “This computer doesn’t have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory”
Mar 1, 2018, 1:46 PM GMT - info: [main/docker-create-machine] You can further specify your shell with either ‘cmd’ or ‘powershell’ with the --shell flag.
Mar 1, 2018, 1:46 PM GMT - info: [main/docker-create-machine]
Mar 1, 2018, 1:46 PM GMT - info: [main/docker-create-machine] Unable to create Docker Machine.
May 8, 2018, 9:04 AM GMT+1 - info: [main/index] Existing Pressmatic data does not exist.
May 8, 2018, 9:04 AM GMT+1 - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘’,
stderr: ‘Host does not exist: “local-by-flywheel”\n’ }
May 8, 2018, 9:04 AM GMT+1 - info: [renderer/CheckEnvPage] Check system promise response:
[ undefined, ‘machine-does-not-exist’ ]
May 8, 2018, 9:20 AM GMT+1 - info: [main/docker-create-machine] Starting Docker Machine Creation…
May 8, 2018, 9:20 AM GMT+1 - info: [main/docker-create-machine] USING IP: 192.168.95.1/24
May 8, 2018, 9:20 AM GMT+1 - info: [main/docker-create-machine] Removing existing Docker Machine
May 8, 2018, 9:20 AM GMT+1 - info: [main/docker-create-machine] null ‘About to remove local-by-flywheel\nWARNING: This action will delete both local reference and remote instance.\n’ ‘Error removing host “local-by-flywheel”: Host does not exist: “local-by-flywheel”\nCan’t remove “local-by-flywheel”\n’
May 8, 2018, 9:20 AM GMT+1 - info: [main/docker-create-machine] Creating Docker Machine… --virtualbox-boot2docker-url=file://C:\Users\Dr Roderick Fahey\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\boot2docker.iso
May 8, 2018, 9:20 AM GMT+1 - info: [main/docker-create-machine] Creating machine with
[ ‘create’,
‘–driver=virtualbox’,
‘–virtualbox-hostonly-cidr’,
‘192.168.95.1/24’,
‘–virtualbox-boot2docker-url=file://C:/Users/Dr Roderick Fahey/AppData/Local/Programs/local-by-flywheel/resources/extraResources/virtual-machine/vendor/docker/boot2docker.iso’,
‘–virtualbox-disk-size’,
‘120000’,
‘local-by-flywheel’ ]
May 8, 2018, 9:21 AM GMT+1 - info: [main/docker-create-machine] Running pre-create checks…
May 8, 2018, 9:21 AM GMT+1 - error: [main/docker-create-machine] Error with pre-create check: “This computer doesn’t have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory”
May 8, 2018, 9:22 AM GMT+1 - info: [main/docker-create-machine] You can further specify your shell with either ‘cmd’ or ‘powershell’ with the --shell flag.
May 8, 2018, 9:22 AM GMT+1 - info: [main/docker-create-machine]
May 8, 2018, 9:22 AM GMT+1 - info: [main/docker-create-machine] Unable to create Docker Machine.
May 8, 2018, 6:58 PM GMT+1 - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘’,
stderr: ‘Host does not exist: “local-by-flywheel”\n’ }
May 8, 2018, 6:58 PM GMT+1 - info: [main/index] Existing Pressmatic data does not exist.
May 8, 2018, 6:58 PM GMT+1 - info: [renderer/CheckEnvPage] Check system promise response:
[ undefined, ‘machine-does-not-exist’ ]

Capture
Lastly this is the other error message I receive (screen shot)

Please see [Windows] Help! I'm getting a BIOS error about VT-X/AMD-v during installation regarding the VT-X/AMV-v error.

As far as the other error goes, is there any type of anti-virus running other than Windows Defender? It may be blocking the VBS script.

Hi!

I’m having the same error during the installation of the program. Could you help me if you fixed the error already?

@YeralH9,

See my reply here: Can't install the program. Stuck on checking system

These are my problems
1 firewall blocked
2 404 not found
3 403 forbidden
4 no connection could be made because the target machine actively refused it