Page 1 of 1

Can't change default VM folder - Critical Error

Posted: 17. Sep 2012, 12:30
by fabricioz
I installed VB just fine, but I want to change the default folder for VMs. When I go to Preferences and set the folder and click OK, I get this error:

VirtualBox - Critical Error
Failed to set global VirtualBox properties.
Details
Callee RC: CO_E_NOTINITIALIZED (0x800401F0)

I have reinstalled and rebooted the system many times and it happens every time. What should I do?

Thanks!

Re: Can't change default VM folder - Critical Error

Posted: 17. Sep 2012, 14:33
by mpack
VirtualBox version?

Re: Can't change default VM folder - Critical Error

Posted: 17. Sep 2012, 14:48
by fabricioz
4.2.0 r80737

Re: Can't change default VM folder - Critical Error

Posted: 17. Sep 2012, 14:51
by mpack
And how about Windows version?

Basically, it sounds to me like its probably a permissions problem. You must have admin rights to install VirtualBox, because device drivers are involved.

Re: Can't change default VM folder - Critical Error

Posted: 18. Sep 2012, 07:44
by fabricioz
It's Windows 7 Ultimate.
I've given admin rights to install and to execute, it seems to be OK...

Just to be clear, I didn't even install a VM yet because when I try to, it tries to install in the default folder, which I don't have space for it, so that's why I need to change the default folder in the preferences.

Re: Can't change default VM folder - Critical Error

Posted: 18. Sep 2012, 12:16
by Hansiii
Hi,

we have the same error.

Workarround: Create a VM with the default settings. Know you can change erverything what you want.
after that you can delete the first created VM. I think this is a Bug.
In VB 4.1.22 it works fine.

greetings from Germany :)

Hansiii

Re: Can't change default VM folder - Critical Error

Posted: 17. Oct 2012, 07:28
by 史提芬
It is a bug, try command line.
VBoxManage setproperty machinefolder <absolute path>

Stephen

Re: Can't change default VM folder - Critical Error

Posted: 17. Oct 2012, 16:37
by fabricioz
Hansiii wrote:Hi,

we have the same error.

Workarround: Create a VM with the default settings. Know you can change erverything what you want.
after that you can delete the first created VM. I think this is a Bug.
In VB 4.1.22 it works fine.

greetings from Germany :)

Hansiii
Thank you Hansii, it worked for me :)