virtualbox.org

Hello All
I need you help,after I upgraded to the new version my guest machine wont start up and give this error:
VIRTUAL BOX ERROR FAILED TO CREATE A NEW SESSION
CALLE RC: REGDB_E_CLASSNOTREG (0X80040154)
Thank in advance for your help.

Reboot the host. If this continues after that then re-install the VBox program and select repair. You might want to right click on the install and then left click on run as.... then select admin. Reboot when complete.

I did all that, I have all my data intact, how can reinstall the virtual machine.
What do you think easy way to put the virtual machine up and run?
Thanks give your steps if you can ...

I looked it up and it is specified as a service that has not been registered. You can try this and see it it helps.

1) Open a standard command line (not as administrator)
2) "cd the the folder that has your VirtualBox program files"
3) issue "VBoxSVC /ReRegServer"
4) issue regsvr32 VBoxC.dll

I've had the same problem and it seems to be repeating itself despite re-installs.

On my part, the behavior I can gather is:

• Had to shut down the computer (manually, i.e. with the power button) because it was completely unresponsive (likely unrelated to VBox)

• After reboot I would have the same error (Failed to create a new session)

• Re-installed VBox, which is a real pain as the installer generally twiddles around for about 5-10 minutes without networking before completing

• Re-install allowed to re-open virtual machines. Rebooting or shutting down virtual machines is fine as well.

• Closed Virtualbox. Problem is back the next time I opened VBox

Similar issues have been regular the past few updates. Re-installing does the job, but involves 20-30 minutes of wasted time.

I can't seem to be able to get any log information on the problem as the VM stops loading before logging events.

@strangeelement,
Can you post you host RAM and processor as well as your memory settings on the guest?
There is really no reason why it should take that long. Also the next time you update try to update by right clicking on the install file and then left click on run as... then select admin. See if this prevents you from needing to reinstall a second time.

I did update trough the virtual box software he did installed, but when try to start from the desktop he wont start based on that error.
i look inside the vb main folder and discovered was 2 folders one with the old and one with the new install i delete the old and point the shortcut to the new and did worked for me.
Fix

My machine is A DUAL PROCESSOR XEON AND 8 GB MEMORY INSTALLED IM USING XP IS THE HOST AND HOME SERVER AS THE GUEST HOME SERVER IS BASED ON W2003.

Thanks for all the help.

Perryg wrote:@strangeelement,
Can you post you host RAM and processor as well as your memory settings on the guest?
There is really no reason why it should take that long. Also the next time you update try to update by right clicking on the install file and then left click on run as... then select admin. See if this prevents you from needing to reinstall a second time.

My host is a AMD Athlon 64 X2 Dual 2.19 GHz with 3G RAM on Windows XP MCE SP3.

My guest is a Ubuntu server 9.04 with 256M RAM.

I'll definitely try running as admin on the next install.

Perryg wrote:I looked it up and it is specified as a service that has not been registered. You can try this and see it it helps.

1) Open a standard command line (not as administrator)
2) "cd the the folder that has your VirtualBox program files"
3) issue "VBoxSVC /ReRegServer"
4) issue regsvr32 VBoxC.dll

This fixed it for me thanks. Perhaps some considering for the next new version to ensure this doesn't happen again please?

Ryster wrote:

Perryg wrote:I looked it up and it is specified as a service that has not been registered. You can try this and see it it helps.

1) Open a standard command line (not as administrator)
2) "cd the the folder that has your VirtualBox program files"
3) issue "VBoxSVC /ReRegServer"
4) issue regsvr32 VBoxC.dll

This fixed it for me thanks. Perhaps some considering for the next new version to ensure this doesn't happen again please?

I agreed 100% !!!