virtualbox.org

Just installed fresh copy of VBox 64-Bit, i ran the checker and it passed, however i keep getting a critical error, failure to create VBox Com Object.

Fixed the problem, it turns out that having things plugged into the usb while attempting to load VBox caused it to error and fail to load.

More specifically, it turns out whenever there was a usb drive plugged in, I would receive the critical error. And after it was loaded, if I did plug it in then, it would cause the program to crash, though the interface and guest os would continue to run.

Just in case this does happen to anyone, this may be a solution.

Running as administrator was not necessary.

I am getting the same error with a 32 bit installation - and I don't have anything plugged into my USB port when I try to launch VBox 2.02.

Oblong7 wrote:I am getting the same error with a 32 bit installation - and I don't have anything plugged into my USB port when I try to launch VBox 2.02.

Are you sure? Not even an internal card reader?

Have you tried to create a new user account and run VB from there?

Hi all. I have same problem with VirtualBox 2.0.2 on 64bit Vista. Have anybody already had any working solution for this problem?thx

Xgamer wrote:Hi all. I have same problem with VirtualBox 2.0.2 on 64bit Vista. Have anybody already any working solution for this problem?thx

Try installing 2.0.2 without USB support. There are some stability issues with USB on 64 bits windows.

It doesn't work I got same error any other ideas?thx

Sasquatch wrote:

Oblong7 wrote:I am getting the same error with a 32 bit installation - and I don't have anything plugged into my USB port when I try to launch VBox 2.02.

Are you sure? Not even an internal card reader?

Have you tried to create a new user account and run VB from there?

Sasquatch:

The wireless card on this laptop is connected internally via a mini-PCI port. I'm not sure if that causes similar problems as a device plugged into a USB port. In any event, it's not something I can easily disconnect, nor would I want to.

I didn't create a new user account.

In another thread, I reported that falling back from Ver. 2.0.2 to 2.0.0 solved this problem for me. I intend to issue a bug report.

Thanks!

A mini-PCI is just what is says, PCI and not USB. Shouldn't give problems like described above with USB devices on 64 bit Windows.

We discourage the downgrade to 2.0 as it's much too instable.

I'm experiencing this problem as well on Windows XP Pro SP3, 32-bit host. I have never seen this error before until this 2.02 release.

I re-ran installation multiple times, for both repair, and the complete uninstallation and then re-installation and still got the error. Backed down to 2.00 solves the problem on my machine as well.

No storage devices on USB, just a USB KVM with keyboard and mouse.

Yes my problem solved when I install 2.0.0 too

I just installed 2.0.2, and I'm getting the same problem. The error comes up when I have my USB WD HDD connected. If i start vbox then connect it, it just causes the Sun xVm interface to stop working...but vbox still runs. However if I try to run a guest os, this error appears:



I don't know if it happens to anyone else, but when I install vbox, a usb module also installs. But, that's jsut the full extent of my problem. Some believe if using vista you should run the program as administrator (and/or disable UAC), but that didn't work for my...drive is actually the problem. Here's my specs if it helps any.


Vista 64-Bit
Intel Core 2 Duo T7300 2.0G
12.1" WXGA
Memory Slots: 2 x DIMM
Memory Speed: DDR2 667
Memory inserted: 4GB DDR2
120GB hdd
DVD Super Multi
Intel GMA X3100
Video Memory-shared
Modem, Gigabit LAN and WLAN (I'm using WLan only)
1 x Type I/II PC Card Slot (Nothing plugged in)
Fingerprint reader (Vista doesn't like this so it's Disabled)
CPU Speed: T7300(2.00GHz)
CPU FSB: 800MHz
CPU L2 Cache: 4MB
Resolution: 1280 x 800
Video Port: 1 x VGA, 1 x S-Video TV-out (Work w/ or w/o monitor plugged in)
Audio Ports: Headphones/speakers/line-out (Doesn't interfere)
Card Reader 5-in-1 reader (Vista doesn't like this so i don't know if it interferes)
Webcam (Integrated-works even if enabled)

I'll add that I have the exact same issue on 32 bit Windows. I never ran into this issue until I installed 2.02. I've tried some of the solutions here and none of them work. The only thing that worked was uninstalling 2.02 and re-installing 2.0.

Anyone??

Check here.

Sander,

I just updated my ticket (2212), and while the new files you provided work to get VirtualBox started (GUI comes up, etc) a lot of functionality is not working, resulting in more failure boxes. This includes starting guests, releasing images, configuring existing VMs, deleting existing VMs.

I've added the details to the ticket.