`vagrant destroy` leaves "artifacts"... because VBox leaves them

Vagrant
1 
# vagrant version
Installed Version: 2.4.3
# vboxmanage --version
7.1.4r165100

After a vagrant destroy when I’ve done a vagrant up it failed with

Could not rename the directory '<some_tmp_folder>' to '<vm_dest_folder>' to save the settings file (VERR_ALREADY_EXISTS)

that’s because in the ‘<vm_dest_folder>’ there where still some files left

VRDEAutoGeneratedCert.pem
VRDEAutoGeneratedPrivateKey.pem

Later I’ve found that even when doing a delete (with “delete all files”) from the VirtualBox GUI those files remained there, so the problem is on their side, but I haven’t manged to find a way to open a ticket on their system. So maybe someone reading here can “tell” it to them

2

Yes, sometimes it happens. Especially when you edit Vagrantfile between up and destroy at least this was my experience. Anyway, you can clean up that folder manually. During normal operation Vagrant usually is able to clean up its belongings.