Page 1 of 1

Install failed on Yosemite 10.10.1

Posted: 25. Nov 2014, 15:36
by RadlyEel
I launched VirtualBox this morning and got a message about an update. I am pretty quick to keep updated, so I downloaded it and tried to install it, but the update failed. No big deal, I thought, I'll try again later. But the failed update broke the current VB app, so it wouldn't run at all. I deleted it entirely, re-downloaded the 4.3.20 version and tried to reinstall, but the installation fails utterly, with only a message to contact the manufacturer for assistance. Does anyone have any idea how to get going again?

Re: Install failed on Yosemite 10.10.1

Posted: 25. Nov 2014, 16:21
by loukingjr
Without knowing the exact error message you had when it first failed or the second it's hard to know what the problem was. The first thing to try is use the VirtualBox_Uninstall.tool. Then try installing it again. If you get another error post the entire error message.

Re: Install failed on Yosemite 10.10.1

Posted: 15. Jan 2015, 22:42
by zeisler
I am having the same issue. I have used the uninstaller. This is the message in the console: 1/15/15 12:40:06.493 PM Installer[1282]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.

Also have restarted my computer

Re: Install failed on Yosemite 10.10.1

Posted: 16. Jan 2015, 04:30
by loukingjr
run Disk Utility>Repair DIsk Permissions. Try installing again.

Re: Install failed on Yosemite 10.10.1

Posted: 16. Jan 2015, 19:44
by zeisler
I also found this in the log:

install:didFailWithError:Error Domain=NSPOSIXErrorDomain Code=2 "The operation couldn’t be completed. No such file or directory" UserInfo=0x61000046a440 {NSFilePath=/private/tmp/PKInstallSandbox.XXXXXX}

I checked if /private/tmp existed and it didn't so I created it. I then reran the install and worked.

Re: Install failed on Yosemite 10.10.1

Posted: 16. Jan 2015, 20:39
by loukingjr
Not sure why "/private/temp" did not exist. I certainly should exist. If you haven't already I would try repair disk permission and even verify disk.