"Cannot access the kernel driver" after installing 2.2.4

[abcuser]

Hi,
on Windows XP SP3 host and Ubuntu 9.04 I had VirtualBox 2.2.2 working well without any problem.

Then I did the following:
1. shutdown virtual guest
2. installed VirtualBox 2.2.4 over the existing installation.
3. rebooted Windows host
4. opened VirtualBox GUI
5. deleted all VirtualBox log files to make sure there is no errors in logs.
6. selected Ubuntu guest and clicked Start button from tools bar menu.
The error displayed: "Cannot access the kernel driver! Make sure the kernel module has been loaded successfully." Then only Abort button available and click on it displayed error: "Failed to open a session for the virtual machine..."

See attached pictures.

I have checked the log files but there was no log file created! Very strange.

Has anyone got the same problem?
Regards

01_vb.JPG (69.58 KiB) Viewed 30264 times

02_vb.JPG (75.32 KiB) Viewed 30195 times

[timbosteron]

Same here. No idea why this is happening.

[Lord_Phoenix]

Mine is loading and even shows me logon screen, but after I enter my credentials it shows Desktop picture and if I'm lucky also a toolbar, but then it freezes Xubuntu and Kubuntu works fine, no problem with XP as well

[wesley]

just upgraded to 2.2.4 from 2.1.something on my work machine, got exactly same problem

restarted the machine didnt help as well

[Perryg]

Try re-installing by right clicking on the install icon and left clicking on run as admin.
Select repair and after the install reboot before trying to use the VBox program.
This is especially necessary when updating from a release older than 2.2.0

[wesley]

that didnt work for me, however, i uninstalled 2.2.4 and install 2.2.0, it's working now

[Perryg]

that didnt work for me, however, i uninstalled 2.2.4 and install 2.2.0, it's working now

There were a lot of reported problems when updating from version 2.1.* to 2.2.* due to the fact that it was such a major update. I fell into that loop as well because I did not uninstall before I ran the new release. I found that I needed to re-install to replace the drivers that were not replaced properly. Since you have it working in 2.2.0 now it would probably go ahead and update properly to the newer release.

[wesley]

that didnt work for me, however, i uninstalled 2.2.4 and install 2.2.0, it's working now

There were a lot of reported problems when updating from version 2.1.* to 2.2.* due to the fact that it was such a major update. I fell into that loop as well because I did not uninstall before I ran the new release. I found that I needed to re-install to replace the drivers that were not replaced properly. Since you have it working in 2.2.0 now it would probably go ahead and update properly to the newer release.

just updated to 2.2.4 and it's working now thanks Perryg

[timbosteron]

Try re-installing by right clicking on the install icon and left clicking on run as admin.
Select repair and after the install reboot before trying to use the VBox program.
This is especially necessary when updating from a release older than 2.2.0

That helped. Thank you.

[abcuser]

Try re-installing by right clicking on the install icon and left clicking on run as admin.
Select repair and after the install reboot before trying to use the VBox program.
This is especially necessary when updating from a release older than 2.2.0

Perryg, thanks a lot. It also works on Windows XP host. I double click install program with user that has Administrator rights. Repair. Reboot before first starting VM guest. Start VM guest and now works fine.

By the way, I have submitted bug report: http://www.virtualbox.org/ticket/4140
Thanks a lot.
Abcuser

[Perryg]

You might want to update you report with the process of what you did to get this going. Also when submitting a bug report they state that you must submit the VBox log file as well. They are really strict about this and may even let you know about it.

[abcuser]

You might want to update you report with the process of what you did to get this going. Also when submitting a bug report they state that you must submit the VBox log file as well. They are really strict about this and may even let you know about it.

Perryg, I know that. I updated report yesterday and wrote about how I solved a problem (your workaround). I know I have to attach vbox log file, but in this case no log file was created!

I think it is some kind of bug in install procedure, that does not copy correct files or something like that... And it looks many many people have the same problem, so it should not be to difficult to reproduce.

[coolbiker]

seems like last few installs all require a repair to function properly. Is another install program an option or just force a repair on install?

[Perryg]

I think the real problem is Windows UAC and the fact that it requires everything to be elevated to install. Windows is supposed to ask if you want to run this install program but for some reason it fails to do so for VirtualBox. I just tell Windows to run as admin to begin with and I have no problems.

[coolbiker]

o.k when 2.3 comes out I'll force the run as admin and see what happens. BTW did anyone notice there was a heck of allot more things being installed for 2.2.4 yet in repair only about 2.