Page 1 of 1
VB no run on Win7x64
Posted: 27. Jun 2014, 17:28
by Carlos Pizzi
Hello
Run VirtualBox in Win7x64 Ultimate SP1 and the following error and closes
Fallo al crear el objeto COM de VirtualBox.
La aplicación se cerrará.
Receptor RC: E_NOINTERFACE (0x80004002)
Any idea why it fails?
thanks
Re: VB no run on Win7x64
Posted: 28. Jun 2014, 22:21
by noteirak
This has been answered many times over. In your favorite search engine, search for :
site:forums.virtualbox.org failed to create COM
Re: VB no run on Win7x64
Posted: 3. Oct 2014, 20:26
by jmdavidson
noteirak wrote:This has been answered many times over. In your favorite search engine, search for:
site:forumsdotvirtualboxdotorg failed to create COM
I think it's unfair to say it "has been answered many times over." I'm already doing that search and so far all I see is people suggesting the same knee-jerk responses that don't actually fix the problem (and which I at least have already tried anyway.) not to mention that if there was a known problem with a reliable fix, presumably it would be corrected in the application's installer sometime between 4.2.17 and 4.3.16.
I have deleted every single trace of VBox I can track down, and rebooted repeatedly. I have reinstalled (after uninstall and reboot) using "Run as Administrator" on the installer. I have tried running VBox with and without "Run as Administrator" and in all scenarios I get the same dialog as above, with the same entry in VBoxSVC.log:
Code: Select all
VirtualBox COM Server 4.3.16 r95972 windotx86 (Sep 9 2014 18:27:29) release log
00:00:00.002000 main Log opened 2014-10-03T17:34:51.282507200Z
00:00:00.002000 main Build Type: release
00:00:00.002000 main OS Product: Windows 7
00:00:00.002000 main OS Release: 6.1.7601
00:00:00.002000 main OS Service Pack: 1
00:00:00.047002 main DMI Product Name: 3227GQ9
00:00:00.054003 main DMI Product Version: ThinkCentre M92P
00:00:00.054003 main Host RAM: 3398MB total, 1400MB available
00:00:00.054003 main Executable: C:-Program Files-Oracle-VirtualBox-VBoxSVC.exe
00:00:00.054003 main Process ID: 6000
00:00:00.054003 main Package type: WINDOWS_32BITS_GENERIC
00:00:00.341019 HostDnsMonitorProxy: Host's DNS information updated:
00:00:00.341019 DNS server 1: 192dotdot18
00:00:00.341019 DNS server 2: 192dotdot14
00:00:00.341019 DNS server 3: 192dotdot19
00:00:00.341019 DNS domain: foodotnet
00:00:00.391022 VDInit finished
00:00:05.494314 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={fafa4e17-1ee2-4905-a10e-fe7c18bf5554} aComponent={VirtualBox} aText={The object is not ready}, preserve=false
EDIT: Apparently I'm still too much of a noob to post "URLs" so I've intentionally broken the URLs and IPs in the log above.
EDIT 2: Apparently I can't even quote a U-R-L from someone else's post.
EDIT 3: Whisky Tango Foxtrot, guys? Apparently even just the word "ewe are ell" is banned 
Re: VB no run on Win7x64
Posted: 6. Oct 2014, 01:33
by BillG
Apart from anything else, this is not strictly a VirtualBox problem. It is Windows problem. VirtualBox has not even loaded yet. The installer is a Windows program, not part of VirtualBox. The problem is with Windows permissions.
Were you trying to run the installer as Administrator?
Re: VB no run on Win7x64
Posted: 6. Oct 2014, 16:47
by jmdavidson
Thank you, Bill, I appreciate you taking the time to reply.
BillG wrote:Apart from anything else, this is not strictly a VirtualBox problem. It is Windows problem. VirtualBox has not even loaded yet. The installer is a Windows program, not part of VirtualBox. The problem is with Windows permissions.
Even if that's true, the installer ran with no error messages. The log I posted is generated anew each time I run the VirtualBox GUI. The "
RC: E_NOINTERFACE (0x80004002)" problem is reported all over these forums and hasn't gone away.
Let's presume the problem
is with Windows permissions. It's still a problem introduced by a change in VirtualBox. It's well known that this problem started after 4.2.16. It's also well known that I can go download and install 4.2.16 right now and everything will work fine, with no monkey-business. Except that I'd be missing support for newer OSes, which is the exact reason I'm trying to get past 4.2.16.
BillG wrote:Were you trying to run the installer as Administrator?
jmdavidson wrote:I have reinstalled (after uninstalling and rebooting) using "Run as Administrator" on the installer. I have tried running VBox with and without "Run as Administrator"
To clarify I have run the installer both with and without "Run as Administrator", and I have run the VirtualBox GUI both with and without "Run as Administrator".
Thanks again.