virtualbox.org

I made a fresh xp pro install on my pc, installed the newest VB, when I go to File/Preferences and make changes like the machine folder location and install the extensions pack, after I close the window it states:

VirtualBox Critical Error (windowbox)

Failed to set global VirtualBox properties

Details:
Callee RC:
CO_E_NOTINITIALIZED (0x800401F0)

I have never had a problem like this before in the past, and dont know what to do now.
Cant do anything until I get past this issue. I apologize if this has been covered, I'm a bit lost.

Also, after I close the error box, anything I changed resets, nothing gets saved and the extension pack is no longer installed either.

Sounds like your <userdocuments>/.VirtualBox/VirtualBox.xml file is write protected, or else you don't have write access to the folder.

Either that or VirtualBox has not been installed properly (i.e. with admin rights).

I have complete admin rights to my entire system, and the pc is completely up to date. I cannot change the Machine folder location and the extension pack wont stay installed.

Really wierd. I'm lost.

Also, I have always had my machines stored on a different drive, which was never an issue in the past. Always worked fine. Now I cant get anything to work. Reinstalled it clean 4x already.
?

These kinds of problems that are reproducible should be reported to bugtracker. If you have not signed on to Bugtracker before you will need to select a new Nickname to be able to report issues.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.

I figured it out. Before I was able to setup locations before doing anything else. With this version I now have to first setup a machine using the defaults, then after I set it up, then I must go and change the location of my machine folder. Once I did it that way, everything worked just as it should have.
all good now,.
thanks.

In other words, after install, install extension pack, dont change anything else, make a New Machine, make its settings changes, then before actually building it, go and change the machines directory first.

This is not the way it should work. If that is what you must do then it is a regression and should be reported.

Possibly this issue? If so, it's reported as fixed in 4.2.2 by a developer, at the end of that thread.

It is a bug, try command line.
VBoxManage setproperty machinefolder <absolute path>

Stephen