We've found the solution yesterday, thanks to this post: https://superuser.com/questions/1153470/vt-x-is-not-available-but-is-enabled-in-bios
Running the Readiness tool, and disabling the Application Guard, the Credential Guard and Device Guard did the trick. https://www.microsoft.com/en-us/download/details.aspx?id=53337 We also disabled the Core Isolation trought a registry edit, since the GUI seems buggy in Windows 10 - 1809: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity Enabled DWORD = 0 HVCIMATRequired DWORD = 0 Locked DWORD = 0 Le mercredi 31 juillet 2019 15:31:57 UTC-4, Jim McGinness a écrit : > > I'm not sure what you mean by a "hardening error". > > One thing I've run into is that the virtualization support is normally > turned off in laptops' BIOS as the factory default. But you say you've > installed vbox and run a VM under it without Vagrant being present, so that > doesn't sound like the issue here. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/52dda06e-3fff-4f62-ae99-0064b146ec4a%40googlegroups.com.
