Opened 6 years ago
Last modified 6 years ago
#17890 new defect
Double Clicking or Open of .vbox File or Alias Error
| Reported by: | McTTRS | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.16 |
| Keywords: | Guest start | Cc: | |
| Guest type: | Windows | Host type: | Mac OS X |
Description
Double Clicking or Open of .vbox File or Alias produces the error: "Failed to open virtual machine located in /Users/mike/VirtualBox VMs/Windows 10/Windows 10.vbox.
Trying to open a VM config '/Users/mike/VirtualBox VMs/Windows 10/Windows 10.vbox' which has the same UUID as an existing virtual machine.
Result Code: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89} Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}"
Have changed the UUID withe command line " /Applications/VirtualBox.app/Contents/MacOS/VBoxManage internalcommands sethduuid '/Users/mike/VirtualBox VMs/Widows 10/Windows 10.vdi'" but get the same error.
Attachments (1)
Change History (2)
by , 6 years ago
| Attachment: | Windows 10-2018-07-24-13-05-58.log added |
|---|
comment:1 by , 6 years ago
Just because you're getting an error message, that doesn't make it a bug...
It's usually better and faster, if issues get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
Log File