After VB Crash: The given path '{....}' is not fully qualified.

[kraeMit]

Hi,

after having a VirtualBox crash (6.1.4 @ WIN10) one of my virtual machines (Ubuntu 18.04) can't be started anymore, but Murphy holds 2 important files in it :-/

Error message:

Das Medium konnte nicht mit folgender ID geöffnet werden: {e6d81412-184a-479e-bdea-d3b032a99e63}.

The given path '{e6d81412-184a-479e-bdea-d3b032a99e63}' is not fully qualified.

Fehlercode: VBOX_E_FILE_ERROR (0x80BB0004)
Komponente: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)

e6d81412-184a-479e-bdea-d3b032a99e63 is my VDI image.

System is a 3 month old Lenovo notebook running WIN10.

Which possibilities do I have to repair the VDI image?

I have only a 2 month old clone of the VM and unfortunately no snapshot :-/


Thanks for a tip!

kraeMit

[scottgus1]

According to Google Translate, the German in that error message is:

The medium could not be opened with the following ID

Googling this:

the given path is not fully qualified site:forums.virtualbox.org

shows that whatever was being tried received the long string of hex numbers (a UUID) instead of an expected "drive:\path\to\file.ext".

Since Virtualbox "crashed", I would guess the VM's .vbox file got corrupted. If you did absolutely nothing to this guest before the crash except start it and run it (no new snapshots, settings changes in Virtualbox, etc.) then you can try this:

Open the guest's folder with the .vbox file. There should be a .vbox-prev file too. Rename the .vbox file extension to .vbox-crash, then copy the .vbox-prev file and rename the copy's extension to .vbox

Try the guest.

[mpack]

Note that Windows has a habit of hiding the extension of registered file types. A VDI is a registered file type, therefore a snapshot filename would appear as nothing more than a strong of hex digits and dashes wrapped { in braces }.

I suspect that the user has been trying console commands and/or manually modifying a .vbox file, using filenames as they appear in a Windows file browser. This will of course fail, because the filename is not complete without the extension.

The simplest solution is to tell Windows to stop lying about filenames. Get into folder options and tick the "View|File name extensions" checkbox.