I’m excited to be apart of your community.
Sadly I can’t seem to get local installed and working on my computer
Here’s the “full story”
Downloaded program
started install
left to use bathroom
came back to error
uninstalled all programs associated (through control panel>program manager)
Attempted to reinstall
local by flywheel stuck on “Starting Local Machine” (no “installation” screen appeared)
Uninstalled program again
removed downloaded program “local-by-flywheel-2-2-4-windows”
Ran disk cleanup
Shut down & started computer
downloaded program
attempted install again
local by flywheel stuck on “Starting Local Machine” (no “installation” screen appeared)
Uninstalled program again
removed downloaded program “local-by-flywheel-2-2-4-windows”
Ran disk cleanup
Shut down for the night
Started computer this morning
downloaded program
attempted install again
local by flywheel stuck on “Starting Local Machine” (no “installation” screen appeared)
Not sure what my next steps are but here are the local’s logs local-by-flywheel.log (14.4 KB)
Would you be able to tell me how I can fix this?
Thank you for your time and I look forward your reply.
Hello Everyone,
I’ve tried a number of different times now and still have yet to successfully install local…
The install fails or pauses every time, I have even tried it on one of my other computers with no luck.
I will upload all the docs below
That error about VT-X/AMD-v not being enabled means that virtualization isn’t available. You can try to reboot your machine and see if there is an option within the BIOS for that. Here is a community forum post detailing that:
If you aren’t able to enable this setting in the BIOS, then you might not be able to run Local on this computer.
Just for a little backstory on why I’m recommending you try that – within the above log there are these warnings:
Mar 14, 2018, 11:48 AM PDT - warn: [main/docker-machine] C:\Program Files\Oracle\VirtualBox\VBoxManage.exe showvminfo local-by-flywheel --machinereadable failed:
Mar 14, 2018, 11:48 AM PDT - warn: [main/docker-machine] VBoxManage.exe: error: Failed to create the VirtualBox object!
Mar 14, 2018, 11:48 AM PDT - warn: [main/docker-machine] VBoxManage.exe: error: Code REGDB_E_CLASSNOTREG (0x80040154) - Class not registered (extended info not available)
Mar 14, 2018, 11:48 AM PDT - warn: [main/docker-machine] VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.
Hey @Ash.svice.ca – That second error still looks like the hardware on your machine isn’t able to run virtualization software.
To give you a better idea of what is happening – Local uses Virtualbox to create a virtual machine where all of your WordPress sites will live during development.
In order for the virtual machine to have access to things like the Processor, RAM, or the network cards, it needs to have a sort of abstraction layer to these things.
Most newer hardware has this abstraction enabled by default, but older hardware didn’t have this abstraction. There’s a sort of “somewhat older” hardware that was able to run this mode, but you have to make changes to the BIOS.