How to remove cached non-existing Virtualbox machines, when using Hyper-V as provider?

I was using Vagrant under Windows 10 Pro first with Virtualbox provider and created a few boxes.
Then because I wanted to test Docker for Win, I had to switch to Hyper V and uninstall Virtualbox.
After some time I manually deleted some Virtualbox machines or re-purposed the folders so they don't have Vagrantfile anymore in them.

When I try to run either
vagrant global-status --prune
or
vagrant destroy -f XXXYYYZZZ
I get this error:
The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below:
Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires this to be available on the PATH. If VirtualBox is installed, please find the `VBoxManage` binary and add it to the PATH environmental variable.

I understand what Vagrant is trying to say: Install virtualbox binary so it can manage the boxes. But actually there are no VMs to begin with so it should be enough to delete it from registry and for that no Virtualbox is necessary.
Is there a way how to remove cached boxes from registry in my case?

edit
asked same question at stackoverflow: https://stackoverflow.com/questions/45857206/how-to-remove-cached-non-existing-virtualbox-machines-using-hyper-v-as-provider

Leave a Comment