gistfile1.txt

$ vagrant up
__ __ __ __
\ V\ V\ V / Varying Vagrant Vagrants
 \_/\_/\_/  v3.0.0-git::develop

Platform:   platform-mingw32 windows HasWinAdminPriv vagrant-hostsupdater vagrant-vbguest NoColour shared_db_folder_disabled
Vagrant:    v2.2.4,     VirtualBox: v6.0.8r130520
VVV Path:   "C:/users/snarl/websites-vvv/sites-vvv"

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'varying-vagrant-vagrants/ubuntu-18.04' version '1557101534' is up to date...
==> default: Setting the name of the VM: sites-vvv_33ebf71fcbd
The name of your virtual machine couldn't be set because VirtualBox
is reporting another VM with that name already exists. Most of the
time, this is because of an error with VirtualBox not cleaning up
properly. To fix this, verify that no VMs with that name do exist
(by opening the VirtualBox GUI). If they don't, then look at the
folder in the error message from VirtualBox below and remove it
if there isn't any information you need in there.

VirtualBox error:

VBoxManage.exe: error: Could not rename the directory 'C:\Users\snarl\VirtualBox VMs\sites-vvv_02652ed77c8' to 'C:\Users\snarl\VirtualBox VMs\sites-vvv_33ebf71fcbd' to save the settings file (VERR_ALREADY_EXISTS)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component SessionMachine, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "SaveSettings()" at line 3206 of file VBoxManageModifyVM.cpp