Callee RC: E_NOINTERFACE (0x80004002) Install Error

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Tad
Posts: 9
Joined: 12. Dec 2013, 21:57

Callee RC: E_NOINTERFACE (0x80004002) Install Error

Post by Tad »

Hi All,

This has been bugging me since 4.2.16. I have been unable to install any newer versions since then and am hoping someone has a solution.

Win 7 64bit machine. Tried installing in normal acct (full admin access) and as root admin. Neither made this install successful. Am I stuck with 4.2.16 or is there a fix?

Regards

Andrew
Attachments
2014-09-24_0846.png
2014-09-24_0846.png (26.47 KiB) Viewed 1443 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Callee RC: E_NOINTERFACE (0x80004002) Install Error

Post by Perryg »

Best suggestion I have seen is to uninstall VirtualBox and delete the folder, then install again. Just don't delete the guest folder or the VirtualBox.xml.

Don't forget to reboot between sessions of uninstall and install. You also might want to stop at 4.3.12 until the issues of 4.3.14 and 4.3.16 are sorted out.
Tad
Posts: 9
Joined: 12. Dec 2013, 21:57

Re: Callee RC: E_NOINTERFACE (0x80004002) Install Error

Post by Tad »

Thanks Perry,

Unfortunately your suggestion didn't correct the problem. So guess I'm stuck with 4.2.16.

Regards

Andrew
Tad
Posts: 9
Joined: 12. Dec 2013, 21:57

Re: Callee RC: E_NOINTERFACE (0x80004002) Install Error

Post by Tad »

As a further note, I have tried updating from 4.2.16 in small steps to no avail. The update failed with 4.2.18 so something happened at that point to stop my updates.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Callee RC: E_NOINTERFACE (0x80004002) Install Error

Post by mpack »

I doubt your problem is with VirtualBox at all - people have had an awful long time to report problems installing 4.2.18, and have noticably failed to do so.

I suggest you Google for "Driver Signature Enforcement", make sure the Windows Installer isn't silently discarding drivers it doesn't like. Note that this kicks in on 64bit Windows hosts even if you run with admin rights.

Obviously you should never install into the "Admin" user account, as that would be pointless - unless that's the account you normally use.

Also there was a recent windows update that messed up the MSI installer. Note that MSI is part of Windows, not part of VirtualBox.
Post Reply