Laravel "Homestead Up" doesn't boot vm after updating VirtualBox and Vagrant says it already exists

I was having a few issues with Homestead 2.x suddenly for reasons I don't understand. So I reinstalled Vagrant and VirtualBox from a suggestion off Laravel's forum, and now it seems to want to boot, but it says:

$ homestead up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'laravel/homestead'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'laravel/homestead' is up to date...
A VirtualBox machine with the name 'homestead' already exists.
Please use another name or delete the machine with the existing
name, and try again.

I'm not sure why it is sayng laravel/homestead already exists as I haven't installed a new version. I'm a bit afraid to play around with this now as I don't want to delete anything by accident. I looked at the VirtualBox GUI and it only has one Homestead box, and a settler_default_12314848585938 box (which I don't know what that is, but it doesn't have any shared folders).

What should I be doing to be able to boot up the vm so I can continue working?

via Chebli Mohamed