There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. windows 10

Question

I just got laravel homestead to run yesterday using powershell. Now, it won't even run. I just suspended vagrant and turned off my pc. Now it's just giving me this error:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'laravel/homestead' is up to date...
==> default: Clearing any previously set forwarded ports...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "b21f2dd0-7f73-4d0f-b1e0-0f82ecdda1fe",    
"--natpf1", "delete", "ssh", "--natpf1", "delete", "tcp33060", 
"--natpf1", "delete", "tcp44300", "--natpf1", "delete", "tcp54320", 
"--natpf1", "delete", "tcp8000"]

Stderr: VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified   
error (extended info not available)
VBoxManage.exe: error: Context: "LockMachine(a->session,  
LockType_Write)" at line 493 of file VBoxManageModifyVM.cpp

Solution 1

Ok, so I finally fixed the problem. Tried restarting my laptop and it's not giving me that error anymore. Here's what I did:

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

source: https://github.com/mitchellh/vagrant/issues/3852

Solution 2

I had the same problem and the previous answer didn't work for me. I opened the VirtualBox GUI and saw that the virtual machine was running. I stopped it and then I executed "vagrant up". All worked well.

Solution 3

For Mac OS, close all the running VMs and restart the virtual box using following command:

sudo "/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh" restart

Solution 4

Just enable permission for VirtualBox in Security & Privacy

Solution 5

1. First of all destroy the virtual box with vagrant destroy.
2. Navigate to C:\Users\Justice replace justice by username.
3. Delete the .vagrant.d folder.
4. Go into VirtualBox VMs folder and delete everything inside it.
5. Start it again with vagrant up.

It should work fine.

View more solutions