VBox-VM with Vagrant stopped working

I’ve been having a problem with a Vagrant machine since today. I have the current version 7 of VBox and the current Vagrant version 2.3.2 installed. The normal VMs all run fine. One of two Vagrant machines also runs normally, only one causes problems when starting. After vagrant up I get the following error message, with which I couldn’t get any further even after hours of research on the net:

Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Checking if box ‘debian/contrib-jessie64’ version ‘8.11.1’ 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”, “556374d1-b36d-4f85-ae45-a455cd2739c3”, “–natpf1”, “delete”, “127.0.0.1tcp8080”, “–natpf1”, “delete”, “ssh”, “–natpf1”, “delete”, “127.0.0.1tcp8080”, “–natpf1”, “delete”, “ssh”, “–natpf1”, “delete”, “127.0.0.1tcp8080”, “–natpf1”, “delete”, “ssh”, “–natpf1”, “delete”, “127.0.0.1tcp8080”, “–natpf1”, “delete”, “ssh”, “–natpf1”, “delete”, “127.0.0.1tcp8090”, “–natpf1”, “delete”, “ssh”]

Stderr: VBoxManage.exe: error: Code E_INVALIDARG (0x80070057) (extended info not available)
VBoxManage.exe: error: Context: “RemoveRedirect(Bstr(ValueUnion.psz).raw())” at line 2108 of file VBoxManageModifyVM.cpp

Does anyone have an idea where the problem could lie? I had the VM running normally last week and haven’t changed anything since then. The VM can be started normally in the VBox interface, just not with the help of vagrant.