Failed to create the VirtualBox COM object [Resolved]

[socratis]

OK, your permissions seem correct, so does your installation log as far as I can tell, BUT, I can't actually compare it to an actual installation on 10.10.x because, I don't have 10.10.x, not even in a VM (too slow). If someone else could provide just the installation log on a 10.10.x system, that would definitely help verify that everything went OK.

Next step: post the zipped 'VBoxSVC.log' from /Users/you/Library/VirtualBox.

[loukingjr]

The OP's install log seems to complete successfully however this seems odd…
his:

Feb 1 15:26:44 lass-MacBook-Pro.local Installer
…
…

mine:

Feb 2 08:27:48 Mac-10ddb1bd02d8.home Installer
…
…

I'm wondering if the OP is using Vagrant or running off a server or some other non-standard way.

seems to be the only difference between my log and his.

[socratis]

No, that seems perfectly legal. His username "las", so I'm assuming that "lass-MacBook-Pro" would be the proposed/preferred name of his computer. The .local was added by default by OSX, like for everything that doesn't have a fully qualified DNS name. Compared to you that specifically chose to add .home to your Mac-10ddb1bd02d8 name.

If you remember his initial problem wasn't the installation, it was the launch. I simply wanted to make sure that everything went fine during the install. Now that that's out of the equation, I asked for the VBoxSVC.log...

[loukingjr]

I didn't add .home. OSX 10.10.2 added it as far as I know. I certainly didn't. lol If I had, I wouldn't have mentioned it.

[loukingjr]

for that matter I have no idea where the "Mac-10ddb1bd02d8" name came from. This particular iMac's name is "iMac" lol

[socratis]

So what do you get after doing a "uname -n"? It's not the self-assigned name?

[loukingjr]

I get this… Mac-10ddb1bd02d8.home
but if I do About this Mac, I get… iMac or Get Info etc. Sounds like it's time for some disk utility work lol

[loukingjr]

Repairing Disk Permissions fixed my name problem. Now I just have to track down which app changed the name in the first place.

The OP definately seems to be having a permissions problem.

[las]

OK, your permissions seem correct, so does your installation log as far as I can tell, BUT, I can't actually compare it to an actual installation on 10.10.x because, I don't have 10.10.x, not even in a VM (too slow). If someone else could provide just the installation log on a 10.10.x system, that would definitely help verify that everything went OK.

Next step: post the zipped 'VBoxSVC.log' from /Users/you/Library/VirtualBox.

lass-MacBook-Pro:VirtualBox las$ ls -al
total 64
drwx------ 4 las staff 136 Jan 31 22:18 .
drwx------@ 53 las staff 1802 Jan 31 19:29 ..
-rw------- 1 las staff 1214 Jan 31 22:18 compreg.dat
-rw------- 1 las staff 24597 Jan 31 22:18 xpti.dat

There's no VBoxSVC.log in that location.

[loukingjr]

From the Finder's Go menu, select "Go to Folder", type in /Users/username/Library/VirtualBox

replace username with your login name. las or lass, whichever you use.

[socratis]

Man, you have a tough problem to crack... OK, here are a couple of things to try:
1. Zip and post both those files in the settings folder (compreg.dat, xpti.dat).
2. Rename the settings folder: mv /Users/las/Library/VirtualBox /Users/las/Library/VirtualBox-old
3. If that doesn't work, create a new admin user and log on as him.
4. Promise the gods a virgin goat as a sacrifice.

[loukingjr]

I always try 4 first.

[socratis]

From the Finder's Go menu, select "Go to Folder", type in /Users/username/Library/VirtualBox

I believe he was already there. His permissions and contents match.
BTW, Lou, can you do an exact byte count of the "compreg.dat"? His was 1214, mine 1267, while both of our "xpti.dat" were 24597. Couple that with the fact that his error is only referenced in the XPCOM libraries, I believe it's some component that doesn't get registered.

PS. Next time if 4. doesn't work, try to sacrifice a god to the goats

[loukingjr]

mine's 1267 as well. xpti.dat=24,597 although for some reason my Mac thinks it's a Graphics Converter document.

[las]

Man, you have a tough problem to crack... OK, here are a couple of things to try:
1. Zip and post both those files in the settings folder (compreg.dat, xpti.dat).
2. Rename the settings folder: mv /Users/las/Library/VirtualBox /Users/las/Library/VirtualBox-old
3. If that doesn't work, create a new admin user and log on as him.
4. Promise the gods a virgin goat as a sacrifice.

Attached zip file containing the Dat files.
Renamed the VirtualBox folder and re-ran it, still the same issue.