[Solved] VIRTUAL BOX ERROR - WILL NOT START

[LycoDiane]

I am receiving the following error when running Oracle VM VirtualBox. I have tried to reinstall VirtualBox, but the error persists. Any help would be appreciated!:

Failed to create the VirtualBox COM object.

The application will now terminate.



Start tag expected, '<' not found.

Location: 'C:\Users\salamone/.VirtualBox\VirtualBox.xml', line 1 (0), column 1.

F:\tinderbox\win-4.3\src\VBox\Main\src-server\VirtualBoxImpl.cpp[534] (long __cdecl VirtualBox::init(void)).

Result Code: E_FAIL (0x80004005)
Component: VirtualBox
Interface: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}

[Perryg]

The virtualbox.xml file is corrupt. Either install from backup or look in the folder indicated and see if there is a -prev file and replace the corrupt one with that.

[LycoDiane]

Thank you so much. I renamed the -prev file and that worked!

[Domgodess]

Thank-you so much! I had a similar problem with my system, and have been messing around for a couple months now trying to figure out how to solve the problem. Obviously I should have checked this site sooner. It took a few tries, but after entering the right search terms I found this posting. The problem was similar enough to mine that when I removed the -prev from one file and changed the problem file to .config/VirtualBox/VirtualBox.xml.1, my Virtual Box started right up. So simple. Thanks again.

[shizzledizzleeee]

Do you have a video showing how to solve this issue?

Document is empty.
Location: 'C:\Users\HP\VirtualBox VMs\Win10SSD\Win10SSD.vbox', line 1 (0), column 1.
F:\tinderbox\win-6.1\src\VBox\Main\src-server\MachineImpl.cpp[499] (long __cdecl Machine::initFromSettings(class VirtualBox *,const class com::Utf8Str &,const class com::Guid *)).


Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
Callee:
IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}

[mpack]

We don't do videos here. Just rename the .vbox-prev file as described. Make sure you disable the Windows file explorer option "Hide extensions for known file types" otherwise Windows will obscure some file names and confuse you.

[scottgus1]

The exact steps I'd use are:

Reboot the host so no Virtualbox processes are running.
Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager.
In the folder that opens, find the VM's .vbox file and the .vbox-prev file. (As Mpack pointed out, configure your host OS to show all extensions if the folder that opens does not show a .vbox file.)
Rename "VM name.vbox" to "VM name.vbox-bad"
Rename "VM name.vbox-prev" to "VM name.vbox"
Try Virtualbox again.

[shizzledizzleeee]

There is lack of proper explanation here. Just remove -prev part. and add the virtual machine to virtual box again

[mpack]

There is lack of proper explanation here. Just remove -prev part. and add the virtual machine to virtual box again

You do not add the VM to VirtualBox again. It was never removed.

The rest is exactly what has already been stated.

Note that these are user to user discussion forums. Not a tuition site.

[scottgus1]

There is lack of proper explanation here. Just remove -prev part

Life tutorial for "shizzledizzleeee": When you don't know how to do something, and you ask others for help, don't bash the help you get. If you don't understand or think there is a shortcut, ask polite questions:

Is it OK to only remove the -prev part?

The answer would be:

Yes, if you have already have shut-down all other Virtualbox processes and deleted or renamed the existing damaged file.

The asking of why these prerequisites are necessary is the next step in the life tutorial and is left as an exercise for the student. Satisfactory completion of the exercise will determine the extent of future assistance.

[shizzledizzleeee]

What I mean is that the answer should be clear to people who know nothing about computers.

[scottgus1]

Ah, I see. FWIW only removing the -prev part would also be above those who truly know nothing about computers. Just how does one 'remove the -prev part'? One would have to know how to rename a file, which is beyond those who know nothing. And teaching folks how to use a computer is beyond the scope of this forum.

These instructions have been given to others and they have successfully fixed the problem. If one does not know how to rename a file, one should Google that.

Further, and this is where the 'why' exercise above leads, simply 'removing the -prev part' will possibly fail to fix the problem, depending on what the computer and Virtualbox are doing at the time. Thus the apparently more complicated process, which covers all circumstances for a pebcak-compensated foolproof fix.

[mpack]

What I mean is that the answer should be clear to people who know nothing about computers.

There is no limit to that rabbit-hole.

The instructions above were as simple as it gets.