virtualbox.org

When trying to start VB, it displays the following message

Falha ao carregar o objeto COM do VirtualBox.

A aplicação será finalizada.


Failed to instantiate CLSID_VirtualBox w/ IVirtualBox, CLSID_VirtualBox w/ IUnknown works.

PSDispatch looks broken by some installer featuring the broken oleaut32.msm module as a component.



Código de Resultado: E_NOINTERFACE (0x80004002)
Componente: VirtualBoxClientWrap
Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

Uninstall Virtualbox, reboot, then disable real-time antivirus scanning, then Reinstall Virtualbox by right-clicking the installer and choose Run As Administrator.

That dialog box looks ancient. What is the host OS? Version and 32bit/64bit flavor please.

Greetings!

I appreciate the help.

I reinstalled it a few times. I have no active antivirus, they hinder more than they help.

My operating system is Windows 7, 64 bits. I like to use the XP theme.

In the Event Viewer, the system displays an internal driver error in \ Device \ VBoxNetLwf

In addition, I could see that the error is directly related to the "VirtualBox Interface"

I even installed 6.1.14 and 6.1.16

Both have the same error

We need details on how you reinstalled. The error message says that it was not done properly. Even if you have no AV installed, Windows may still block attempts to install drivers or modify certain sections of the registry, if that is what Windows is configured to do.

Also, VirtualBox has to be installed for the correct user, i.e. NOT the admin user.

Finally, note that Windows 7 is no longer a supported host OS for 6.1.x, so I don't know for certain that the installer works there.

I already deleted the ".VirtualBox" folder and reinstalled it.

After reinstalling, I changed the compatibility settings. I enabled the option "Run this program in compatibility mode".

I also enabled "Run this program as an administrator" on the "Privilege Level" tab.

Nothing solved the problem.

mpack wrote:We need details on how you reinstalled. The error message says that it was not done properly. Even if you have no AV installed, Windows may still block attempts to install drivers or modify certain sections of the registry, if that is what Windows is configured to do.

Also, VirtualBox has to be installed for the correct user, i.e. NOT the admin user.

Finally, note that Windows 7 is no longer a supported host OS for 6.1.x, so I don't know for certain that the installer works there.

The reinstallation was done in a simple way. I opened the executable and went ahead.

I have on my computer only 1 administrator user and 1 guest.

It must be the point that Win 7 does not support version 6.1.x.

Charles_Designer wrote: It must be the point that Win 7 does not support version 6.1.x.

Not necessarily. XP worked as a host long after it stopped being supported. Unfortunately I was an early adopter of Win10 after XP, barely touching intermediate Windows versions, so I'm not in a position to say for sure what still works. The only thing I do know is that we're not seeing a lot of complaints from people being unable to install on Win7. Admittedly that could be because few have Win7 hosts any more.

As a test you could always try installing the final release from the 6.0.x branch, which did support Win7. That would be 6.0.24, released last July.

If that doesn't work then try running the installer using "Run as administrator". Do this even if you have admin rights.

Ok, I got it. I will try

I installed 6.0.24. As an administrator.

Unfortunately it didn't work.

Displays the same message. I believe that this file mentioned in the message has some influence: "oleaut32.msm".

"PSDispatch appears to be broken by an installer featuring the broken oleaut32.msm module as a component."

There is a file somewhere with some configuration that is getting in the way all.

Last year, I used VirtualBox normally, then uninstalled it.

So, I went to reuse it now. And this problem came up.

Web-searching: "oleaut32.msm virtualbox" brings up interesting results. This issue appears to be caused by another program that damaged either a file or the registry in the host OS. In one result the error message fingered a particular program. In other results the causing program could not be identified, as yours cannot.

The error appeared with a 5.2.22 Virtualbox also, so the version may not be important, though minding the lack of Windows 7 support for 6.1.x is important.

One result had a fix by editing the registry: https://www.programmersought.com/article/93691800344/ (Mind that this is not a Virtualbox site, YMMV, however another result from the Virtualbox Bugtracker mentions this same fix https://www.virtualbox.org/ticket/12087 ... um_hist=10) Be very careful implementing this. Take a full restorable disk image and export the registry key as backups if you try this fix.

Virtualbox never needs to be run in compatibility mode on a properly-working host PC.

scottgus1 wrote:Web-searching: "oleaut32.msm virtualbox" brings up interesting results. This issue appears to be caused by another program that damaged either a file or the registry in the host OS. In one result the error message fingered a particular program. In other results the causing program could not be identified, as yours cannot.

The error appeared with a 5.2.22 Virtualbox also, so the version may not be important, though minding the lack of Windows 7 support for 6.1.x is important.

[...]

It worked!

Thank you all very much for your attention and help.

Saved my life!

I will be forever grateful. May the force be with you.

Did you try the registry edit? Or something else?