VirtualBox, Vagrant & Laravel Homestead "vagrant up" error

▲
2
▼

I'm currently trying to switch back to Laravel Homestead after using Laragon for a while, after the release of Laravel 5.3. I've followed all of the steps on the guide in the docs, and watched several screencast tutorials but I get this error when running vagrant up:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "977385f5-4aa5-4def-be66-1741ac9b560b", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'homestead-7' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\\VirtualBox VMs\homestead-7\Logs\VBoxHardening.log'

VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

As it says in the error, here is my VBoxHardening.log

Also, I have tried reinstalling VirtualBox and that didn't fix it.

Any help really appreciated.

php
laravel
vagrant
virtualbox
homestead
asked on Stack Overflow Aug 30, 2016 by Sean Whelan • edited Aug 30, 2016 by Nikhil Vaghela

4 Answers

▲
1
▼

I know this post hasn't had any activity in months, but I just wanted to update it as I found out what was causing the problem a few months ago. It was actually MacType, a font smoother I was using. I uninstalled it, and it just worked, no problem at all.

answered on Stack Overflow Feb 25, 2017 by Sean Whelan
▲
0
▼

Try to restart your laptop and just see it's gives you that error? You just follow this steps: 

1. Right click on "This PC" / "My Computer" on windows desktop
2. Select "Properties"
3. Go to "Advanced" tab
4. Click "Environment Variables..." at the bottom
5. Under System Variables click "New..."
6. Set "Variable name" to "VBOX_INSTALL_PATH"
7. Set "Variable value" to "C:\Program Files\Oracle\VirtualBox\"
8. Select "OK" and close all the other settings windows

Hope this helps you!!:)

answered on Stack Overflow Sep 6, 2016 by Hiren Gohel
▲
0
▼

I had this issue after updating Windows 10 and my Nvidia (and Geforce Experience) drivers.

I did a "vagrant box update", but still got the error.

I updated my virtualbox and vagrant said it couldn't use this version of virtualbox.

Then I downloaded the latest vagrant (1.8.6) and it solved the problem.

https://www.vagrantup.com/downloads.html

Hope this helps.

answered on Stack Overflow Sep 28, 2016 by Jerome
▲
0
▼

I had the same issue and none of the answers on this question or others in Stack Overflow helped me. Problem appeared to go away if I uninstalled virtualbox and reinstall. But then if I reboot the host machine, the issue came back and had to repeat. Very frustrating.

I came across this post and it turns out that Trusteer Rapport was causing the issue. No idea why, but it seems the problem came after an update in June 2018. I uninstalled Trusteer Rapport, reinstalled virtualbox and everything is working!

answered on Stack Overflow Sep 6, 2018 by kiki

User contributions licensed under CC BY-SA 3.0