This computer doesn’t have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory (...but it is.)

Support
1

Hi.

For the past couple of days, I’ve been trying to install Local and I get the the “Error creating machine: Error in driver during machine creation: This computer doesn’t have VT-X/AMD-v enabled. Enabled it in the BIOS is mandatory” error when I try to install the Host Machine… here’s what’s very frustrating.

  • I’ve updated my computer to the latest Oracle Virtual Box.
  • I’ve went into my BIOS settings and activated the VT and the networking settings.
  • If used both the latest auto update version of Local (2.2.4) and the pre-release version of Local (2.3.1).
  • By the way, I’m installing this on Windows 10 on an ASUS laptop and I’ve been able to install it with no problems previously. I have no idea what’s going on this time.

If I go ahead with the install, I will get a script error message which prevents Local from working (Script: C:\Users\AppData\Local\Programs\local-by-flywheel\resources\extraResources\run-hidden.vbs ; Line 6; Char 1; Error: The system cannot find the file specified; Code 80070002; Source (null) ).

If I remove the Local install from the Virtual Box, I would still get the same “Error when installing…” message.

I’ve even went as far as uninstalling and reinstalling Oracle Virtual Box and starting the Local install separately… and I still get this issue.

I’ve tried looking up the issue in Google and in the forum, but nothing has helped and I’m noticing that this is becoming a big reoccurring problem. How can I fix my issue? Or, better yet, is there a release coming really soon that will fix this problem?

2

Never mind!!! I’ve figured out the issue. Anti-virus software strikes again! I had to disable the anti-virus protection and it installed with no problems.

1 Like
3

Glad you got it! Thanks for the follow-up solution :slight_smile:

4

My version of this same VT-x error (and blocked Local installations) just fixed itself this afternoon after Win10 did its automatic update today–and it was a long, big one, “April 2018.” Prior to this, changing my BIOS on my SONY VAIO, i7, did not get Locals to be happy and install. It seems possible that this update just caused my OS to look at the BIOS on the reboot. I have an all-in-one with battery and it cannot be completely removed from electricity–as far as I know. BTW, Local would complete the first of the three phases (“Virtual Box”) with a nice green check mark, but would hang after that. FYI, this is my first time running any special environments on my computer and first time with Local by Flywheel. My next hurdle was inside the setup of my first site getting my computer to allow a one-time edit of HOSTs file. It was buried in my security software.

1 Like