Geek Answers Handbook

Virtualbox "Callee RC: REGDB_E_CLASSNOTREG" (0x80040154)?

I got a problem with Virtualbox

Callee RC: REGDB_E_CLASSNOTREG "(0x80040154)

suddenly. The problem started with VirtualBox 4.3 (I think). I upgraded to version 5, hoping to fix the situation, but had no luck at this point.

+12
virtualbox
source share
9 answers

My solution: Check your directory C:\Users\yourname\.VirtualBox\ ( yourname is actually your username.)

On my PC there was a VirtualBox.xml size 0 Kb. There was also VirtualBox.xml-prev of 3 Kb. Dates where somewhere around time the problem started ...

Renaming VirtualBox.xml-prev one to VirtualBox.xml SOLVED is my problem.

For those who do not have an xml file, here is my xml file, hope this helps .....

 <?xml version="1.0"?> <!-- ** DO NOT EDIT THIS FILE. ** If you make changes to this file while any VirtualBox related application ** is running, your changes will be overwritten later, without taking effect. ** Use VBoxManage or the VirtualBox Manager GUI to make changes. --> -<VirtualBox version="1.12-windows" xmlns="http://www.innotek.de/VirtualBox-settings"> -<Global> -<ExtraData> <ExtraDataItem value="general,system,previewClosed,display,storage,audio,network,usb,sharedFolders,description" name="GUI/DetailsPageBoxes"/> <ExtraDataItem value="m=59397901-1440-48ea-8781-6f86d06c7fbb" name="GUI/GroupDefinitions/"/> <ExtraDataItem value="m=Sharepoint" name="GUI/LastItemSelected"/> <ExtraDataItem value="415,153,770,550,max" name="GUI/LastWindowPosition"/> <ExtraDataItem value="D:/virtualbox" name="GUI/RecentFolderHD"/> <ExtraDataItem value="D:\virtualbox\Sharepoint.vdi;" name="GUI/RecentListHD"/> <ExtraDataItem value="334,1261" name="GUI/SplitterSizes"/> <ExtraDataItem value=",confirmGoingScale,remindAboutAutoCapture,remindAboutMouseIntegration,showRuntimeError.warning.HostAudioNotResponding,confirmInputCapture,warnAboutInaccessibleMedia" name="GUI/SuppressMessages"/> <ExtraDataItem value="53" name="GUI/UpdateCheckCount"/> <ExtraDataItem value="1 d, 2015-08-19, stable, 5.0.0" name="GUI/UpdateDate"/> </ExtraData> -<MachineRegistry> <MachineEntry src="D:/virtualbox/Sharepoint/Sharepoint.vbox" uuid="{59397901-1440-48ea-8781-6f86d06c7fbb}"/> </MachineRegistry> -<MediaRegistry> <HardDisks/> <DVDImages/> <FloppyImages/> </MediaRegistry> -<NetserviceRegistry> -<DHCPServers> <DHCPServer enabled="1" upperIP="192.168.56.254" lowerIP="192.168.56.101" networkMask="255.255.255.0" IPAddress="192.168.56.100" networkName="HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter"/> </DHCPServers> </NetserviceRegistry> <SystemProperties exclusiveHwVirt="false" LogHistoryCount="3" webServiceAuthLibrary="VBoxAuth" VRDEAuthLibrary="VBoxAuth" defaultHardDiskFormat="VDI" defaultMachineFolder="C:\Users\yourname\VirtualBox VMs"/> <USBDeviceFilters/> </Global> </VirtualBox>
+32
source share

I had a mistake ...

Failed to create COM object VirtualBoxClient. The application will be terminated. Callee RC: REGDB_E_CLASSNOTREG (0x80040154)

... when starting VirtualBox as a regular user. Starting with the administrator, he worked on the other hand.

System: Windows 8, VirtualBox 5

In fact, the problem “suddenly” appeared after I was playing with unprocessed disk accesses. During this test, I installed VirtualBox again as an administrator.

What people do not always know is that the registry also has access control, such as files. Right-click on a folder to open the Autorisations window to display them.

When I reinstalled it as an administrator, the registry keys were created during access at the administrator level. Thus, I could no longer run VirtualBox as non-admin.

Reinstalling as a regular user did not solve the problem. Probably because some admin level keys cannot be deleted.

Solution that worked for me:

  • Backup .VirtualBox (optional since all backups :-)
  • Remove VirtualBox
  • Open the regedit.exe registry editor as an administrator.
  • Delete all remaining VirtualBox keys (especially .NET, driver registration, compatibility manager settings)
  • Reinstall VirtualBox using the user account.

Notes:

I have not tested the uninstallation process of VirtualBox at the administrator level using sysinternals. That might work.

Be careful with regedit. The graphical interface is pretty 90s. Good to know: CTRL + F searches under the currently selected key, so be sure to start your search.

I had one key for the USB driver, which I could not remove due to access rights issues. Finally, this is still not necessary.

Please remember to change permissions on VirtualBox disk files when they were created using VirtualBox, which is run by the administrator.

+16
source share

Renaming VirtualBox.xml-prev one to VirtualBox.xml solved my problem.

+5
source share

After switching to VirtualBox-5.0.8-103449 an error was started: Virtualbox "Callee RC: REGDB_E_CLASSNOTREG" (0x80040154)

No advice on the internet helped.

This helped delete the entire contents of the "C: \ Users \" user "\. VirtualBox" folder, and then restarted the Oracle VM VirtualBox shortcut on the desktop.

Apparently, when you delete the previous version of the Virtualbox folder "C: \ Users \" user "\. VirtualBox" .

Since the contents of the folder must be deleted manually after reinstalling VirtualBox, as well as in case of damage to VirtualBox, for example, due to lack of space on the hard disk.

Not to be confused with the folder "C: \ Users \" user "\ VirtualBox VMs

This folder appears later, only after the institution has a specific virtual machine.

sorry for the machine translation.

+1
source share

In my case, this error was caused by the null byte of VirtualBox.xml in the user folder .VirtualBox . I found out after switching to 4.x and received a more detailed message about the absence of the < tag.

+1
source share

As I suggested for the superuser , today (09/09/2015).

Go to the new version that has been released. You can find her here.

There have been some changes regarding Windows 10 issues.

0
source share

The solution is in the last paragraph.

I had another reason for the same error message in VirtualBox 5.0.20.
So, I temporarily installed VirtualBox 5.1.10, which is trying to analyze the situation and gives more information about the likely culprit.

In my case, the error message from VB 5.1.10 looked like this:

Could not create CLSID_VirtualBox w / IVirtualBox, but CLSID_VirtualBox w / IUnknown is working.
PSDispatch looks like a broken program "xxx" ({11B6009E-3F04-4478-A807-30FBD579FC07}), suspecting that it has a broken oleaut32.msm module as component {997FA962-E067-11D1-9396-00A0C90F27F9}.
We suggest you try removing "xxx".
See also https://support.microsoft.com/en-us/kb/316911 .

Result Code:
E_NOINTERFACE (0x80004002)
Component:
VirtualBoxClientWrap
Interface:
IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

Where 'xxx' is here, the placeholder name for a specific program name, which he mentions and suggests deleting. (The specific name in my case is not important here).

So, I deleted the specific program that the new version of VirtualBox blamed, and after that VB started working again. Then I reinstalled the old version of VB 5.0.20. I needed to keep using, and everything was fine.

0
source share

After some research, I found this thread with a step:

 find C:\Program Files\Oracle\VirtualBox\drivers\vboxdrv\VBoxDrv.inf right click and select Install
0
source share

I had the same problem, I believe that something is damaged when I turned off without properly closing the connections, and I can not load VB.

I tried all the solutions above, but none of them worked.

Without uninstalling, I went to the virtual box website, took the latest version and installed on top of it, and VB came to life.

Version 6.0.14 from 6.0.10

0
source share

More articles:


All Articles