How to fix "detached" Vagrant Virtualbox Virtual Machine

I am running the latest Vagrant on Windows 10 with Laravel Homestead as my base box and have encountered a problem - whenever I try to vagrant up, vagrant will attempt to re-import the base box (homestead-7) and then complain that it cannot rename the .vmdk file because one already exists.

The exact error I get is:

VirtualBox error:

VBoxManage.exe: error: Could not rename the directory 'C:\Users\Joseph\VirtualBox VMs\ubuntu-18.04-amd64_1556050376209_55420' to 'C:\Users\Joseph\VirtualBox VMs\homestead-7' 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 3123 of file VBoxManageModifyVM.cpp

I do not have a packaged version of my box, I only have the Virtual Machine directory with the .vbox and .vmdk files. Destroying the box and setting up anew is not an option - the box contains working databases and software.

How can I get VirtualBox to recognize the existing "homestead-7" folder as the correct directory for the Virtual Machine?