Page 1 of 1
error on latest version of vbox in xp pro sp3
Posted: 27. Jul 2009, 17:30
by trenos2
Hello, everyone.
I have a problem after i reboot my laptop with vb. I'm running a aspire 5050 with 4 gigs of ram. I am also running xp pro sp3. It sees 2.25 gigs of ram.
What is going on is, i install vbox and everything runs fine. but if i reboot my comp, i get this when i try to run vbox:
VirtualBox-Critical Error
Failed to create Virtualbox Com Object
The application will now terminate
And then for details:
Callee RC: REGDB_E_Class notreg (0x80040154)
If anyone could be of any help, it would be appreciated.
-Matt
Re: error on latest version of vbox in xp pro sp3
Posted: 27. Jul 2009, 18:25
by Perryg
trenos2,
This problem usually indicates a failed install IMHO. and can be fixed by re-installing. Right clicking the install program and then left click on run as admin.
When presented with a choice select repair.
Re: error on latest version of vbox in xp pro sp3
Posted: 27. Jul 2009, 19:55
by trenos2
Do I have to repair every time i try to use the program? that seems the case. It asks me to reboot, and when I do, I get a similar dialog box.
Help.
-Matt
Re: error on latest version of vbox in xp pro sp3
Posted: 27. Jul 2009, 20:05
by Perryg
No not if it installs correctly. Did you try to install by right clicking on the install file and selecting run as admin?
Re: error on latest version of vbox in xp pro sp3
Posted: 28. Jul 2009, 14:28
by trenos2
That's just the problem, i am the admin on this computer. I've tried running it and it won't let me.
Re: error on latest version of vbox in xp pro sp3
Posted: 28. Jul 2009, 15:42
by Perryg
I have seen this before when someone was running the machine as admin. and the solution was to run as normal user and then elevate the install (if needed) by right clicking and then install as administrator. I believe this has to do with Windows UAC and the way it works. What I believe happens (and of course can be wrong) is Windows creates the install with the permissions of the installer and writes the registry events, file structure, and permissions accordingly. Now when you reboot and login you do not have what Windows requires to run the program, more than likely permissions and it can not load the program that controls the COM server. This is because something was not registered correctly, here again by placement and permission.
"Callee RC: REGDB_E_Class notreg (0x80040154)" Looks to me like this means not registered properly.
Most of the time I see this in Windows the user has disabled UAC and set their login to Admin, which (I believe) makes Windows go stupid. Since it was not really meant to run this way it throws off how it controls the install and placement. But hey this is all speculation and theory.