virtualbox.org

I just uninstalled the previous version (2.0.6?) and installed 2.1.0 and when I tried to run VirtualBox for the first time, I get the error message: "Failed to create the VirtualBox COM object."

The Result Code is VBOX_E_XML_ERROR (0x80BB000A). The component is VirtualBox. The interface is IVirtualBox {339abca2-f47a-4302-87f5-7bc324e6bbde}.

The text of the error has three paragraphs:

Could not load the settings file 'C:\\.VirtualBox\VirtualBox.xml'.

Element '{http://www.innotek.de/VirtualBox-settin ... Properties', attribute 'defaultHardDiskFolder
" [facet 'pattern'] The value '' is not accepted by the pattern '.+'.

Element '{http://www.innotek.de/VirtualBox-seting ... mPoperties', attribute 'defaultHardDiskFolder': '' is not a valid value of the atomic type '{http://www.innotek.de/VirtualBox-settings}TLocalFile'.

I would really like to be able to use VirtualBox to begin virtualizing, but this is really a disappointment. Thanks for any help that I can get.

Remove the whole .VirtualBox folder in your userprofile. If you have any VMs there, copy/move them to another location as backup. Now start VB again.

Sasquatch wrote:Remove the whole .VirtualBox folder in your userprofile. If you have any VMs there, copy/move them to another location as backup. Now start VB again.

I got into the like problem while trying to execute VirtualBox 2.1.0 on Windows XP pro SP3. The message I got is following.

"Cannot create COM-object. Error code: Unknown status 0x800706BA"

Shall I follow to your advice or there is something else to it?

You can try a reinstall of VB, or use my other solution.

Sasquatch wrote:You can try a reinstall of VB, or use my other solution.

Sorry, but your other solution doesn't work as I fon't have such a folder.
Reinstalling VB doesn't help either. What else can be done? Maybe some older version is more stable?

You don't have DCOM Service running.

Enable it in cpanel->adminstuffs->services. then re-run VB.

RagnaBaby wrote:You don't have DCOM Service running.

Enable it in cpanel->adminstuffs->services. then re-run VB.

Thanks! I've done it.