VirtualBox 4.1.20 Installation Failed

[ChaseLivingston]

Installation is failing when I'm attempting to update from 4.1.18. I'm running OS X 10.8. Any help would be much appreciated.

Thanks,

Chase

[ChaseLivingston]

Reboot fixed the issue.

[tedroberts]

I too have noticed that you have to un-install the previous version, then reboot to clear out any background tasks using the previous libraries, and then install the new version.

If I recall correctly, I don't think I needed to un-install previous versions before installing the new one (back in the days of version 3). I think I just installed the new version 'over' the old one.

Ted

[michaln]

I too have noticed that you have to un-install the previous version, then reboot to clear out any background tasks using the previous libraries, and then install the new version.

Uninstallation is not required. If you had to uninstall before the newer version installed, you must have been doing something unusual.

[tedroberts]

Hi,

Not sure what you meant by

Uninstallation is not required. If you had to uninstall before the newer version installed, you must have been doing something unusual.

I agree that uninstallation should not be required, but I'm running a pretty vanilla installation. When I just run the installer, it finishes saying there was a problem, but nothing helpful in terms of diagnostics, and usually 'breaking' the previous installation. This has happened on each release for quite a while, at least since version 4 came out.

So I have gotten into the habit of uninstalling the old version, re-booting then installing the new version.

If you have any suggestions to what might be unusual, that persists between updates, I would appreciate them. I have tried repairing permissions in case the installer cannot write to everywhere it needs to. I usually install logged on as an administrator.

I would note others have reported similar problems with no solutions being posted on the board.

I am now running Mountain Lion, but these problems existed under Lion.

Thank you in anticipation.

Ted

Just noticed this post on the using VirtualBox board: viewtopic.php?f=1&t=51055

T

[michaln]

Unfortunately, because the installation works fine on our Macs, we can't tell you what it is that we don't have on our systems that causes it to fail on yours...

Use the tools Apple gave you, such as the Console app. There may be something useful in install.log or elsewhere. But we can't tell you what to look for.

[loukingjr]

I had no issue installing VB 4.1.20 on OSX 10.8 and I have never uninstalled a previous version before installing the new version. I don't know if it will help but you could try changing your security settings to allow applications to be installed from anywhere. you can always change it back afterwords.

[michaln]

The 4.1.20 installer is signed and does not require changing the security settings on Mountain Lion.

[loukingjr]

The 4.1.20 installer is signed and does not require changing the security settings on Mountain Lion.

I think the default security setting for 10.8 was to allow Mac App Store only so it would have to be changed to at least Mac App Store and identified developers. I could be wrong but I think it defaults to Mac App Store only.

[tedroberts]

Thank you for your suggestions.

I would point out that I was having these problems with Lion, so I am note sure if it is a security/signature problem.

[michaln]

I think the default security setting for 10.8 was to allow Mac App Store only so it would have to be changed to at least Mac App Store and identified developers. I could be wrong but I think it defaults to Mac App Store only.

Indeed you're wrong The default is App Store + identified developers.

FYI (before someone asks), due to the restrictions on App Store apps, there is no chance of VirtualBox being available there. Among other things, it needs to install kernel extensions, which App Store applications aren't allowed to do. For that reason you won't find Parallels or VMware Fusion on the App Store either.

[loukingjr]

I think the default security setting for 10.8 was to allow Mac App Store only so it would have to be changed to at least Mac App Store and identified developers. I could be wrong but I think it defaults to Mac App Store only.

Indeed you're wrong The default is App Store + identified developers.

FYI (before someone asks), due to the restrictions on App Store apps, there is no chance of VirtualBox being available there. Among other things, it needs to install kernel extensions, which App Store applications aren't allowed to do. For that reason you won't find Parallels or VMware Fusion on the App Store either.

Well I believe you. Like I said I could be wrong. I haven't run into install issues with VB since it became available on the Mac so I was just guessing. Also early on, when I first updated to 10.8 I could of sworn I had to change the settings to get a different signed app installed. probably my age

[MikeManes]

I had similar problems loading the 4.1.20 update on my OS X 10.5.8 Mac Mini. But today, I got the notice re the 4.1.22 update, and it loaded and ran just fine. Thanks for the fix!

[tedroberts]

Hi guys,

Last night, on Mountain Lin 10.8.1, installing 4.1.22 over my copy of 4.1.20 it failed at the last step, suggesting I contact the software supplier.

I therefore uninstalled the current version, where the Terminal window told me to restart as there were instances of classes,or something like that.

After restarting, I successfully installed 4.1.22 and loaded the extension pack.

So maybe the installation problem has not been fixed (completely) for Lion/Mountain Lion users.

Regards

Ted

[Synchro]

Indeed it has not been fixed, I have 4.1.20 installed, and I get the same error from both 4.1.22 and 4.2.0 installers on 10.8.1. Unlike other posters though , I looked in my logs and can see what the problem is, though I don't have a fix for it:

Code: Select all

Sep 17 11:17:21 oc kernel[0]: Can't remove kext org.virtualbox.kext.VBoxDrv; services failed to terminate - 0xe00002c7.
Sep 17 11:17:23 oc kernel[0]: Refusing new kext org.virtualbox.kext.VBoxDrv, v4.2: already have loaded v4.1.20.
Sep 17 11:17:23 oc kernel[0]: Kext org.virtualbox.kext.VBoxUSB - library kext org.virtualbox.kext.VBoxDrv not compatible with requested version 4.2.0.
Sep 17 11:17:23 oc kernel[0]: Can't load kext org.virtualbox.kext.VBoxUSB - failed to resolve library dependencies.
Sep 17 11:17:23 oc kernel[0]: Kext org.virtualbox.kext.VBoxUSB failed to load (0xdc00800e).
Sep 17 11:17:23 oc kernel[0]: Failed to load kext org.virtualbox.kext.VBoxUSB (error 0xdc00800e).
Sep 17 11:17:23 oc kernel[0]: Kext load request buffer from user space still retained by a kext; probable memory leak.
Sep 17 11:17:23 oc kernel[0]: Refusing new kext org.virtualbox.kext.VBoxDrv, v4.2: already have loaded v4.1.20.
Sep 17 11:17:23 oc kernel[0]: Kext org.virtualbox.kext.VBoxNetFlt - library kext org.virtualbox.kext.VBoxDrv not compatible with requested version 4.2.0.
Sep 17 11:17:23 oc kernel[0]: Can't load kext org.virtualbox.kext.VBoxNetFlt - failed to resolve library dependencies.
Sep 17 11:17:23 oc kernel[0]: Kext org.virtualbox.kext.VBoxNetFlt failed to load (0xdc00800e).
Sep 17 11:17:23 oc kernel[0]: Failed to load kext org.virtualbox.kext.VBoxNetFlt (error 0xdc00800e).
Sep 17 11:17:23 oc kernel[0]: Kext load request buffer from user space still retained by a kext; probable memory leak.
Sep 17 11:17:24 oc kernel[0]: Refusing new kext org.virtualbox.kext.VBoxDrv, v4.2: already have loaded v4.1.20.
Sep 17 11:17:24 oc kernel[0]: Kext org.virtualbox.kext.VBoxNetAdp - library kext org.virtualbox.kext.VBoxDrv not compatible with requested version 4.2.0.
Sep 17 11:17:24 oc kernel[0]: Can't load kext org.virtualbox.kext.VBoxNetAdp - failed to resolve library dependencies.
Sep 17 11:17:24 oc kernel[0]: Kext org.virtualbox.kext.VBoxNetAdp failed to load (0xdc00800e).
Sep 17 11:17:24 oc kernel[0]: Failed to load kext org.virtualbox.kext.VBoxNetAdp (error 0xdc00800e).
Sep 17 11:17:24 oc kernel[0]: Kext load request buffer from user space still retained by a kext; probable memory leak.

VB is not currently running. I've not tried rebooting (I hate rebooting!), but even if that does work, it's a workaround, not a fix.