Ah yes - are you using hyperV? You need to enable that and reboot I believe (which will prevent VirtualBox from working). There's information in the Vagrant docs about this issue and a few workarounds.
Best, Seth > On Nov 4, 2014, at 8:04 PM, Neil Strange <[email protected]> > wrote: > > Thanks for your help - but still getting the same result. I'd have thought > eset would tell me if there was a problem - but it hasn't. > > Could it be a hyper V setting conflicting with virtual box? > > Neil. > > > > > > On Monday, 3 November 2014 22:09:17 UTC, Neil Strange wrote: > No matter how I try I can't get Vagrant to run on my desktop (AMD Opteron) > under Windows 8.1. I have Vagrant 1.6.5 installed and Virtual Box 4.3.18 > (which runs quite fine on its own). The path looks OK too. > > When I run vagrant I get an error box popup saying "vagrant.exe has stopped > working". > > I have tried uninstalling ruby, reinstalling Vagrant, etc. > > Any suggestions welcome! > > Neil. > > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>.
smime.p7s
Description: S/MIME cryptographic signature
