C:WindowsSystem32
λ vagrant global-status
id       name    provider   state    directory
----------------------------------------------------------------------------------
dad11cb  default virtualbox poweroff C:/WINDOWS/System32
719fc74  default virtualbox saved    C:/Users/vivek/Desktop/Vagrant_VMs/Ubuntu

The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date (use "vagrant global-status --prune" to prune invalid
entries). To interact with any of the machines, you can go to that
directory and run Vagrant, or you can use the ID directly with
Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"


C:WindowsSystem32
λ vagrant destroy dad11cb
    default: Are you sure you want to destroy the 'default' VM? [y/N] y
==> default: Destroying VM and associated drives...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["unregistervm", "a23f2f0f-fc67-47b6-abcc-c81ee55cb9ab", "--delete"]

Stderr: VBoxManage.exe: error: Could not find a registered machine with UUID {a23f2f0f-fc67-47b6-abcc-c81ee55cb9ab}
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown
VBoxManage.exe: error: Context: "FindMachine(Bstr(VMName).raw(), machine.asOutParam())" at line 153 of file VBoxManageMisc.cpp