virtualbox.org

Hi all,

I tried to install VB 5.0.8 but i got the error : Failed to create the VirtualBoxClient COM object when i launch the application.

Then i uninstalled the 5.0.8 version and tried installing an older version (4.3) but got a different returned error code: ERROR_FILE_NOT_FOUND 0x80070002 (0x80070002).

I searched a lot on the web but every solution i found didn't make it.

I really need VirtualBox so please if someone can get me out of this unsolved problem, i would be gratefull for eternity.

Thanks in advance.

Shigu

Install VirtualBox while logged into your PC as the correct user, and run the installer using "Run as administrator".

A common mistake is to run the installer while logged in as the "Admin" or "Administrator" user, which is not correct.

Thanks for your reply but I already did this and nothing changed.
I also erase the .virtualbox folder, but same result.

Is there a way to solve this problem ?

I am running Windows 10 and VB 4.3 right now but it's the same error with latest version.

Already did what? Please be precise. What should erasing the .VirtualBox folder achieve? There is no software installed in there.

AFAIK, the error message quoted always means that the software was not installed properly. Besides incorrect permissions or wrong user, installation problems can also (rarely) be caused by having a forked version of VirtualBox previously installed on the PC, e.g. the Genymotion Android fork, or the Portable-VirtualBox fork. In those cases the originator of the fork would have to advise you on the best way to completely remove it.

Thank you a lot for your time, mpack.

Sorry for my lack of explanation.
I tried installing the latest version (5.0. 8 ) with admin rights but same error problem.
The returned code change again to : REGDB_E_CLASSNOTREG (0x80040154).

I am the only one using my laptop so the problem should not come from here, i think.

Thank you again for your patience and if you know how to solve this, please tell me.

Shigu

Unless somebody here has had exactly the same problem and remembers what they did to fix it, it is unlikely that you will get a resolution in this forum.

You might have more success is a Windows forum, as it is apparently a Windows registry problem. You will see lots of references if you Google that error message.