Page 1 of 1
Failed to create Virtual Box Com Object
Posted: 28. Sep 2013, 17:24
by Oldster
Having installed VB 4.2.8 on Windows 7 Ultimate 32bit, the above message occurs when starting VB.
There is a sub message:
E_NOINTERFACE (0x80004002)
Note that version 4.2.16 of VB works perfectly OK on my machine, so I have reverted to that version.
I have tried the installation several times including making sure I run with admin permissions.
I'm not sure where to get extra information to supply to you about the failure.
Note again that I have no problems on a similar system but running windows 7 64bit.
Re: Failed to create Virtual Box Com Object
Posted: 28. Sep 2013, 19:05
by noteirak
This kind of message is generated when an installation didn't succeed fully, and that you tried to install/run virtualbox as the wrong user.
Uninstall Virtualbox, reboot your host, then install with admin priviledges but with YOUR USER, then reboot again.
Finally, run Virtualbox with YOUR USER.
The key here is to always run it with your user, while having admin priviledges (accept the UAC prompt)
ps : moved to windows hosts.
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 10:20
by Oldster
There is only one user on my machine.
Anyway. I uninstalled the 4.2.16 version of VB. Reloaded the machine. Installed 4.2.18 VB running as administrator. Reloaded the machine, but I still get the above error.
Any other suggestions?
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 11:50
by noteirak
Did you install as Administrator or with administrator priviledges on your user? It matters...
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 13:02
by Oldster
As far as I'm concerned it was both. My user is as an administrator, and I also ran the install having selected "Run as Administrator"
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 13:25
by mpack
"Admin" or "Administrator" is a default user account name in some systems. As the name implies, this user account has admin rights.
A common mistake is to install the software for user "Admin" instead of your own user account. That's what Noteirak asked you about, i.e. did you install it in the same user account you're now trying to run it from, and if so, did you have admin rights to enable that installation.
I believe the error message means that the service interface normally installed by VirtualBox is not available, so there's obviously something cooky about the installation. It would be up to you to give us some hints as to what that might be.
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 14:35
by ShellVPower
I have the same issue as Oldster. I made the same comment on another post. I am running Win7 32Bit host, installed it with my userid with Admin rights and issue still persists. I checked the registry as well and it appears to be fine. The registry value shows as:
[HKEY_CLASSES_ROOT\TypeLib\{46137EEC-703B-4FE5-AFD4-7C9BBBBA0259}\1.3\0\win32] @="c:\Program Files\Oracle\VirtualBox\VBoxC.dll"
and problem still persists so I changed it to:
[HKEY_CLASSES_ROOT\TypeLib\{46137EEC-703B-4FE5-AFD4-7C9BBBBA0259}\1.3\0\win32] "C:\Program Files\Oracle\VirtualBox\VBoxC.dll"
and problem still persists as well.
... still googling to find solution.
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 14:52
by noteirak
Oldster wrote:I also ran the install having selected "Run as Administrator"
And what happens if you don't select "Run as Administrator", but simply run the installer?
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 15:56
by ShellVPower
I get the same issue when not running as Administrator. I've got the logging enable for the Driver Installation during the install of VirtualBox.
I'm seeing this in the log:
flq: CopyFile: 'C:\Windows\system32\VBoxNetFltNobj.dll'
flq: to: 'C:\Windows\Temp\OLDE0DF.tmp'
flq: DeleteFile: 'C:\Windows\system32\VBoxNetFltNobj.dll'
flq: DeleteFile: 'C:\Windows\system32\VBoxNetFltNobj.dll'
flq: DeleteFile: success
flq: DeleteFile: 'C:\Windows\system32\DRIVERS\VBoxNetFlt.sys'
flq: DeleteFile: 'C:\Windows\system32\DRIVERS\VBoxNetFlt.sys'
! flq: DeleteFile: FAILED!
! flq: Error 2: The system cannot find the file specified.
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 16:00
by Oldster
I think the point I should strenuously make is that I can install version 4.2.16 of VB and it works perfectly OK. However when changing/installing version 4.2.18 (by what ever method) I get the above result. This is all on the same lap-top running windows 7 Ultimate 32bit. Something has changed with the installation of 4.2.18 that seems to be messing me up. I also note that the same installation file for 4.2.18 works perfectly well of a 64bit machine.
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 16:01
by ShellVPower
In the VBoxSC file I see the following :
VirtualBox COM Server 4.2.18 r88780 win.x86 (Sep 6 2013 15:38:42) release log
00:00:00.016000 main Log opened 2013-09-29T13:48:29.857492200Z
00:00:00.016000 main OS Product: Windows 7
00:00:00.016000 main OS Release: 6.1.7601
00:00:00.016000 main OS Service Pack: 1
00:00:00.063000 main DMI Product Name: VGN-FZ348E
00:00:00.094000 main DMI Product Version: C6007VEK
00:00:00.094000 main Host RAM: 3070MB total, 1376MB available
00:00:00.094000 main Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.094000 main Process ID: 6344
00:00:00.094000 main Package type: WINDOWS_32BITS_GENERIC
00:00:00.344000 usbLibDevCfgDrGet: DeviceIoControl 1 fail winEr (31)
00:00:01.077000 VDInit finished
00:00:06.178000 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={3b2f08eb-b810-4715-bee0-bb06b9880ad2} aComponent={VirtualBox} aText={The object is not ready}, preserve=false
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 16:11
by ShellVPower
I agree with Oldster. The latest version of VirtualBox 4.2.18 works fine with 64bit Windows 8/7. It is failing on 32bit. Would this be consider a valid bug and need a fix ? I took your advice, Oldster, and install VirtualBox 4.2.16 on my 32Bit Win 7 Host and it installed and opened the program fine with no issue.
Re: Failed to create Virtual Box Com Object
Posted: 29. Sep 2013, 17:46
by Perryg
ShellVPower wrote:I agree with Oldster. The latest version of VirtualBox 4.2.18 works fine with 64bit Windows 8/7. It is failing on 32bit. Would this be consider a valid bug and need a fix ? I took your advice, Oldster, and install VirtualBox 4.2.16 on my 32Bit Win 7 Host and it installed and opened the program fine with no issue.
Actually the first place to discuss regressions with 4.2.18 is
HERE
Re: Failed to create Virtual Box Com Object
Posted: 24. Nov 2013, 18:09
by tinkeringDad
I am also having this exact issue. Same error and everything.
I am running 32bit Windows 7.
Confirmed after this post that version 4.2.16 works fine when re-installed with zero manual cleanup.
Log dump - errors only:
Code: Select all
00:00:08.814000 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium 'C:\Users\David\VirtualBox VMs\UbuntuServer\UbuntuServer1.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={22781af3-1c96-4126-9edf-67a020e0e858} aComponent={Machine} aText={The object is not ready}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium 'C:\Users\David\VirtualBox VMs\WindowsXP-pxe\NewVirtualDisk1.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={22781af3-1c96-4126-9edf-67a020e0e858} aComponent={Machine} aText={The object is not ready}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={22781af3-1c96-4126-9edf-67a020e0e858} aComponent={Machine} aText={The object is not ready}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium 'C:\Users\David\VirtualBox VMs\HBCD\DadsXP.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium 'C:\Users\David\VirtualBox VMs\Ubuntu_PXE\Ubuntu_PXE.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium 'C:\Users\David\VirtualBox VMs\Xen\Xen.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium 'J:\Backups\DadsDrive40gb.VHD' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium 'C:\Users\David\VirtualBox VMs\DRBL\DRBL.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:08.845000 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={29989373-b111-4654-8493-2e1176cba890} aComponent={Medium} aText={Medium 'C:\Users\David\VirtualBox VMs\Mine OS (turnkey.x86)\Mine OS (turnkey.x86).vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false
00:00:08.845000 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={3b2f08eb-b810-4715-bee0-bb06b9880ad2} aComponent={VirtualBox} aText={The object is not ready}, preserve=false