Opened 11 years ago
Closed 8 years ago
#11542 closed defect (obsolete)
VirtualBox (VBoxSVC?) Corrupts Windows root folder filenames.
| Reported by: | mpack | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.2.8 |
| Keywords: | filename corruption root folder | Cc: | |
| Guest type: | other | Host type: | Windows |
Description
Forum discussion here: https://forums.virtualbox.org/viewtopic.php?f=6&t=54397
This isn't a problem I had, a forum user had the problem and I vaguely remember it being discussed but couldn't find a formal bug ticket for it, so I decided to create one.
Summary: If (say) user registers a VDI file located in a root folder. What seems to happen is that VBox screws up the parsing of the filename - probably not expecting a zero length path - and ends up chopping the first letter off the filename. This gets saved to the xml. Next time VBox starts up it eats another letter and so on.
Yes, user is unwise to locate files in a root folder, but it's still a bug which is probably trivial to fix.
Change History (3)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
I stumbled upon this issue with the version VirtualBox-4.2.16-86992-Win. Virtualbox was chopping the first letter from the registered vdi file. The file name and location was: "E:\TeamCityfilename.vdi". After registering everything worked fine. You need to close VBox GUI (sometimes once, sometimes twice) and then the path changes to: "E:\ \eamCityfilename.vdi" and the machine stops working 'cause it does not see the hard drive.
comment:3 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Hmm, unable to reproduce this problem. Attaching files (vdi, vhd, iso) from root folder, then exit VBox GUI, waiting some time to get it really finished and start again. File names and path are correct.