Virtual Disks missing first character and cannot be loaded

[stevmark61]

Hi.

Whenever I add a disk and then leave Virtualbox and run it again the programme cannot load the drives because it is looking for the name MINUS the first character.

For example : I have a disk called "install.iso" and another called "windows.vhd". When I run Virtualbox it says that the drives are not avaible. It looks for "nstall.iso" and "indows.vhd", which of course do not exist.

I saw on this forum that someone else had the same problem but was it resolved ?

Thanks.

Mark.

[mpack]

Provide a more useful description of your problem, like version numbers and where exactly you see it, then you might get a useful answer.

[stevmark61]

Coming up...

[stevmark61]

Posting some screenshots which I hope are self-explanatory..

Version of the Software is 4.2.8 r83876

The Disks should be called windows.vhd, install.iso and private.iso.

Posting the logfile too.

3.jpg (31.27 KiB) Viewed 2947 times

4.jpg (54.94 KiB) Viewed 2947 times

5.jpg (50.07 KiB) Viewed 2947 times

[stevmark61]

6.jpg (118.38 KiB) Viewed 2947 times

Mark's Environment-2013-03-02-10-57-09.log

(96.34 KiB) Downloaded 19 times

[mpack]

Ah, I see.

You seem to be storing files in a root folder. Don't do that. Create a folder to put the VM files inside (meaning the .vbox file and all media files). You may need to unregister existing VMs and disks in order to fix this. Use Machine|Add to register them again later.

[stevmark61]

LOL. I have the Phrases "How the Hell was I to know ?" and "Was it as simple as THAT ?" echoing in my head

Oh well, Case SOLVED and thanks a lot for your patience with a retard such as me

BTW, VERY cool Product, I must say.

Mark.

[mpack]

You weren't supposed to know. It's definitely a bug, it's just one that people don't hit very often because it only arises on Windows hosts, and then only if you access files in a root folder, which people generally don't. And of course in the meantime the workaround is - don't.

I was going to provide a link to the bugtracker ticket that describes this bug, only I couldn't find one using the keywords I could think of. Strange because I'm sure I remember either Michaln or Klaus mentioning this issue, but don't recall where. Anyway I decided to create the bug ticket myself, here.