Opened 9 years ago
Last modified 9 years ago
#14897 new defect
Windows 10 handles VBoxManage.exe incorrectly when importing and listing — at Initial Version
| Reported by: | dylanh724 | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.0.10 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
I was able to reproduce this with 2 PC's, both Windows 10, trying both an older version (4.3.20) and latest version (5.0.10):
When using VBoxManage.exe to import or list vms (possibly others), the following happens:
1) The item is reported to be imported successfully 2) The .vbox file shows in \VirtualBox VMs\xx.vbox 3) The new VM is NOT added to the GUI 4) Typing
vboxmanage.exe list vms
shows 0 vms
5) Trying to manage the VM using vboxmanage.exe fails since the VM isn't detected 6) However, if I were to elevate my prompt and type
vboxmanage list vms
, the vm shows up. 7) As a workaround, if I were to double click the \VirtualBox VMs\xx.vbox file, it would add it successfully to the GUI and
vboxmanage.exe list vms
would then list them successfully in non-elevated prompt.
This blocker bug breaks all batch files that use vboxmanage to import a VM and configure it. The only workaround is to launch the .vbox file directly, but that will launch the GUI and is very unprofessional when using scripting.

