Vagrant destroy does not clean the VM directory in virtualbox

I like to use vagrant destroy -f to clean a VM.

I use VirtualBox as provider and Windows 10 as host OS. Recently I upgraded my Windows 10 host build version and also vagrant and virtualbox. I also had to update the guest Ubuntu OS from 16 to 20. But now, when I do a vagrant destroy -f, I cannot do a vagrant up because there’s a left-over directory with a log file (VboxUI.log) until I remove that directory. My guess is that this is changed behavior of the provider, but it would be nice if vagrant could have a flag to actually force a complete clean. Is there such a flag?