virtualbox.org

I am having trouble with my VirtualBox - keep getting errors that the *.exe cannot be located. After repair I get report that says the COM cannot be found. Detail is:

Callee RC:
REGDB_E_CLASSNOTREG (0x80040154)

I installed the latest (5.0.12) on my Windows 10 system. I don't know how to begin to correct this other than constantly running repair (which doesn't fix the problem). Any suggestions??

You need to install VirtualBox properly, using "Run as administrator" while logged in as the correct user (not the Admin/Administator user account).

If you already installed it then uninstall it before you try again.

Reinstalled as you suggested -- deleted and then ran as Administrator. Same error:
Failed to create the VirtualBoxClient COM object.
Callee RC: REGDB_E_CLASSNOTREG (0x80040154)

Please post the VM log file. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" to a zip, and attach the zip here.

The VB GUI doesn't open. I simply get a Critical Error box that pops up with the error information I posted earlier. It is a short error message. I don't know what other GUI you may be referencing.

Is there maybe a conflict with another program - Putty, MtPutty, Cygwin?? Maybe the COM error comes from a port conflict? I don't know if the "failed to create" means that something wasn't installed correctly, or whether after install something isn't starting (virtual server/COM object?) because of some conflict. Vagrant can't run because VB can't run. And I can't get the VM manager to come up.

My gut feeling is that you're having Windows Installer problems. Search for "fix windows installer" and see if you can find a couple of articles that can help you.

This issue applies to me as well but started spontanously using v5.0.10. An entry to this issue already exists:
https://www.virtualbox.org/ticket/14296

Deinstalling VBox v5.0.10 and freshly installing v5.0.12 does not fix this issue.

I read the other thread, and it sounds like the same problem. It is a confusing thread - the problem was fixed, and then not?? In my situation, I started with the latest programs - Windows 10 and the latest VM 5.0.12. I was not working from upgrades. Also, for me it makes no difference if I run or install VM as Administrator or not. It doesn't work in both cases. I smile, but it is not a happy situation. I was wondering if my virus program (McAfee) was interfering, but honestly I made all effort to shut the virus scan down completely before install, before running the VM. I wish I had more of an error report, but it is very short. I wish that I could solve this roadblock to my work.