virtualbox.org

Hi guys.
Tell me how you can solve this problem?
I cannot add virtual machine to "VirtualBox"
Thanks.

Failed to open virtual machine located in C:/123/123.vbox.

Error in C:\123\123.vbox (line 2) -- Root element in VirtualBox settings files must be "VirtualBox".

C:\Devel\Antidetect523\src\VBox\Main\src-server\MachineImpl.cpp[500] (long __cdecl Machine::initFromSettings(class VirtualBox *,const class com::Utf8Str &,const class com::Guid *)).

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}

It appears that the 123.vbox file is corrupted. If there is a '123.vbox-prev', you could try renaming '123.vbox' to '123.vbox-bad', then rename '123.vbox-prev' to '123.vbox' then try registering the new '123.vbox'

scottgus1 wrote:It appears that the 123.vbox file is corrupted. If there is a '123.vbox-prev', you could try renaming '123.vbox' to '123.vbox-bad', then rename '123.vbox-prev' to '123.vbox' then try registering the new '123.vbox'

Unfortunately your adevice did not help. But thanks anyway.

Start tag expected, '<' not found.

Location: 'C:\123\123.vbox', line 1 (0), column 1.

C:\Devel\Antidetect523\src\VBox\Main\src-server\MachineImpl.cpp[500] (long __cdecl Machine::initFromSettings(class VirtualBox *,const class com::Utf8Str &,const class com::Guid *)).

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Callee: IVirtualBox {9570b9d5-f1a1-448a-10c5-e12f5285adad}

That means they are both damaged. Do you have a backup copy of either of these files? If not, you'll need to build a new VM with as close to the original settings as you can remember and attach the existing disk file as the VM's disk. If the old VM had snapshots let us know before starting the VM. Otherwise, fire it up and hope for the best. Software in the VM may nee to be reactivated.

scottgus1 wrote:That means they are both damaged. Do you have a backup copy of either of these files? If not, you'll need to build a new VM with as close to the original settings as you can remember and attach the existing disk file as the VM's disk. If the old VM had snapshots let us know before starting the VM. Otherwise, fire it up and hope for the best. Software in the VM may nee to be reactivated.

Thanks for your reply. Yes, of course I have a backup copy of the files, but when loading them, the same problem arises as I described at the very beginning. These files could not be damaged, they were located on another medium. I made several backups on hard drives.

Error in C: \ 123 \ 123.vbox (line 2) - Root element in VirtualBox settings files must be & quot; VirtualBox & quot ;.

Seeing the Antidetect path, I'm wondering if you built VirtualBox yourself, or what version of VirtualBox you are using. Additionally, you could post the 123.vbox file of which you think it's the correct one.

fth0 wrote:Seeing the Antidetect path, I'm wondering if you built VirtualBox yourself, or what version of VirtualBox you are using. Additionally, you could post the 123.vbox file of which you think it's the correct one.

Thanks for your reply. I created this machine myself, before it worked without problems, but recently an error began to appear.

Interface Version 5.2.2 r119230
Below I am attaching 123.vbox file

That .vbox file is clearly snafu'd. Here is a working .vbox file. You can open each in Wordpad, and you'll easily see the difference.

scottgus1 wrote:That .vbox file is clearly snafu'd. Here is a working .vbox file. You can open each in Wordpad, and you'll easily see the difference.

Thanks. Unfortunately, I have not solved my problem.

With what you have, your problem cannot be solved. You will need to build a new VM as close as possible to the old VM's settings and use the existing virtual disk file as the new VM's disk, and hope for the best.

scottgus1 wrote:With what you have, your problem cannot be solved. You will need to build a new VM as close as possible to the old VM's settings and use the existing virtual disk file as the new VM's disk, and hope for the best.

Ok. thank you very much.

One other thought, check your backups. If you find a .vbox file that starts like the .vbox file I posted, with the warning not to edit the file and mention of Virtualbox, it might be a good .vbox file. If the backup file looks like yours, with all that stuff about Microsoft in it, then it's bad.

It appears that something overwrote the beginning of your .vbox file with data from another program. As a rough guess this .vbox file was from an undelete of the disk, and the undelete process confused the .vbox file with a Microsoft Windows Language Pack file.