I´m running OSX 10.8.2 and cannot install the new release of VB: VirtualBox-4.2.4-81684-OSX-1.dmg
My previous version got corrupt. What can I do to solve the problem?
Cannot install new version
Re: Cannot install new version
I'm running Mac OS 10.7.4 and have encountered the same thing. I installed the new version, but right at the end I got a message that the install failed. Now my previous virtualbox won't open. It says it's corrupted or incomplete. How do we fix this issue? Do I need to do a full uninstall with the uninstaller and start over? (If I do that, can I save my VM image so I don't have to build it all over?)
-
rpmurray
- Volunteer
- Posts: 918
- Joined: 3. Mar 2009, 00:29
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 7, Mac OS X (various flavors)
- Location: Between Heaven and Hell
Re: Cannot install new version
Using the uninstall tool does not remove the VM guest you've created or the settings, just the VirtualBox app and the drivers. Having said that, I still always make a backup of the VM guest vdi file and the settings before doing any updates because you never know and it's good to play it safe.
Re: Cannot install new version
Thanks! So I ran the uninstall tool. I got this:
(kernel) Can't unload kext org.virtualbox.kext.VBoxUSB; classes have instances:
(kernel) Kext org.virtualbox.kext.VBoxUSB class org_virtualbox_VBoxUSB has 1 instance.
(kernel) Kext org.virtualbox.kext.VBoxUSB class org_virtualbox_VBoxUSBClient has 1 instance.
Failed to unload org.virtualbox.kext.VBoxUSB - (libkern/kext) kext is in use or retained (cannot unload).
An error occurred durning 'sudo /sbin/kextunload -m org.virtualbox.kext.VBoxUSB', there should be a message above. (rc=3)
unloading org.virtualbox.kext.VBoxDrv
(kernel) Can't remove kext org.virtualbox.kext.VBoxDrv; services failed to terminate - 0xdc008018.
Failed to unload org.virtualbox.kext.VBoxDrv - (libkern/kext) kext is in use or retained (cannot unload).
An error occurred durning 'sudo /sbin/kextunload -m org.virtualbox.kext.VBoxDrv', there should be a message above. (rc=3)
Failed to unload on or more KEXTs, please reboot the machine to complete the uninstall.
Done.
logout
---
However, after completing it, if I try to open VB from my dock, it definitely says it's gone. So I tried to reinstall. Got the same error as before. And got the same error when trying to open VB after the failed install.
Uninstalling then throws the same error as above, yet trying to open VB from my dock shows that it doesn't exist. I guess I'll try to go back to a previous release.
(kernel) Can't unload kext org.virtualbox.kext.VBoxUSB; classes have instances:
(kernel) Kext org.virtualbox.kext.VBoxUSB class org_virtualbox_VBoxUSB has 1 instance.
(kernel) Kext org.virtualbox.kext.VBoxUSB class org_virtualbox_VBoxUSBClient has 1 instance.
Failed to unload org.virtualbox.kext.VBoxUSB - (libkern/kext) kext is in use or retained (cannot unload).
An error occurred durning 'sudo /sbin/kextunload -m org.virtualbox.kext.VBoxUSB', there should be a message above. (rc=3)
unloading org.virtualbox.kext.VBoxDrv
(kernel) Can't remove kext org.virtualbox.kext.VBoxDrv; services failed to terminate - 0xdc008018.
Failed to unload org.virtualbox.kext.VBoxDrv - (libkern/kext) kext is in use or retained (cannot unload).
An error occurred durning 'sudo /sbin/kextunload -m org.virtualbox.kext.VBoxDrv', there should be a message above. (rc=3)
Failed to unload on or more KEXTs, please reboot the machine to complete the uninstall.
Done.
logout
---
However, after completing it, if I try to open VB from my dock, it definitely says it's gone. So I tried to reinstall. Got the same error as before. And got the same error when trying to open VB after the failed install.
Uninstalling then throws the same error as above, yet trying to open VB from my dock shows that it doesn't exist. I guess I'll try to go back to a previous release.
Re: Cannot install new version
Downloaded the last release. Installed without a hitch.
However, now, my VM won't open. I get this error:
Failed to open a session for the virtual machine mymachinevm_1.
The virtual machine 'mymachinevm_1' has terminated unexpectedly during startup with exit code 1.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Machine
Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}
---
Baffled. How can an upgrade wreck everything?
However, now, my VM won't open. I get this error:
Failed to open a session for the virtual machine mymachinevm_1.
The virtual machine 'mymachinevm_1' has terminated unexpectedly during startup with exit code 1.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Machine
Interface: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}
---
Baffled. How can an upgrade wreck everything?