1

Greetings to the community, I recently tried to open my VirtualBox (windows 10 host OS) after approximately 3-4 months (when everything was perfect). Unfortunately, now the VirtualBox is unable to get started and I'm getting the following error message

Failed to acquire the VirtualBox COM object. The application will now terminate.

Completely failed to instantiate CLSID_VirtualBox: ERROR_FILE_NOT_FOUND 0x80070002.


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

error message

What I have tried so far is:

  1. Uninstall the virtualbox installation

  2. Re-install

  3. Reboot

(failed)

I have searched on the web for a solution but did not find anything really enlightening. Maybe this was caused due to a corrupted file on my system? Could you please provide an alternative workaround? I just do not want to lose my existing VMs. Thanks in advance :)

PS: I don't know if this is related, but I have previously used Vagrant on my system, I mention that because it would not come to me as a surprise if the Vagrant corrupted something related to the VirtualBox.

4
  • Generally, reinstallation solved this same issue in my case. Did you see any error code during installation? Did you delete any file from the installation folder? – Biswapriyo Dec 5 '18 at 20:48
  • @Biswapriyo thanks for your reply, no I did not see any error during the installation neither I deleted any file from the installation folder, maybe is a corrupted in the registry file? – NickAth Dec 5 '18 at 22:16
  • Run these two commands as administrator: 1. reg query "HKEY_CLASSES_ROOT\Interface\{D2937A8E-CB8D-4382-90BA-B7DA78A74573}\ProxyStubClsid32" /VE 2. reg query "HKEY_CLASSES_ROOT\CLSID\{0BB3B78C-1807-4249-5BA5-EA42D66AF0BF}\InProcServer32" /VE. Replay with what did you see? – Biswapriyo Dec 6 '18 at 14:35
  • @Biswapriyo Reply from command 1) reg query "HKEY_CLASSES_ROOT\Interface\{D2937A8E-CB8D-4382-90BA-B7DA78A74573}\ProxyStubClsid32" /VE HKEY_CLASSES_ROOT\Interface\{D2937A8E-CB8D-4382-90BA-B7DA78A74573}\ProxyStubClsid32 (Default) REG_SZ {0BB3B78C-1807-4249-5BA5-EA42D66AF0BF} Reply from command 2) reg query "HKEY_CLASSES_ROOT\CLSID\{0BB3B78C-1807-4249-5BA5-EA42D66AF0BF}\InProcServer32" /VE HKEY_CLASSES_ROOT\CLSID\{0BB3B78C-1807-4249-5BA5-EA42D66AF0BF}\InProcServer32 (Default) REG_SZ C:\Program Files\Oracle\VirtualBox\VBoxProxyStub.dll – NickAth Dec 6 '18 at 14:57
2

Solved it by deleting C:\Users\[Username]\.VirtualBox.

Note: I have previously installed VB and the issue only came up after I installed a new one.

0

According to Administration's Guide of VirtualBox:

Oracle VM VirtualBox makes use of the Microsoft Component Object Model (COM) for interprocess and intraprocess communication. This enables Oracle VM VirtualBox to share a common configuration among different virtual machine processes and provide several user interface options based on a common architecture. All global status information and configuration is maintained by the process VBoxSVC.exe, which is an out-of-process COM server. Whenever an Oracle VM VirtualBox process is started, it requests access to the COM server and Windows automatically starts the process. Note that it should never be started by the end user.

When the last process disconnects from the COM server, it will terminate itself after some seconds. The Oracle VM VirtualBox configuration XML files are maintained and owned by the COM server and the files are locked whenever the server runs.

In some cases, such as when a virtual machine is terminated unexpectedly, the COM server will not notice that the client is disconnected and stay active for a longer period of 10 minutes or so, keeping the configuration files locked. In other rare cases the COM server might experience an internal error and subsequently other processes fail to initialize it. In these situations, it is recommended to use the Windows task manager to kill the process VBoxSVC.exe.`

If you just delete C:\Users\[Username]\.VirtualBox, the problem will de "solved", but you will lose all your VM's.

I solved the problem changing the name of C:\Users\[Username]\.VirtualBox to C:\Users\[Username]\.VirtualBox.bkp and starting VIrtualBox. It will create a new folder named C:\Users\[Username]\.VirtualBox.

Now, delete C:\Users\[Username]\.VirtualBox and change back the name of C:\Users\[Username]\.VirtualBox.bkp to C:\Users\[Username]\.VirtualBox

0

Moving or Deleting .VirtualBox did not fix it for me.

However ending the background process VBoxSDS in the Task Manager (Ctrl + Alt + Del) allowed me to restart VirtualBox without the error.

0

Just delete the VboxSDS service from a task manger and everything will start working automatically.It worked for me.

1
  • Processes and services are not "deleted" from the Task Manager. Please edit your post to make it more correct and informative. – music2myear Feb 23 at 5:00
0

I met this today and tested all the above but did not help me. so try to do the following that gets right with me

  1. Go to (turn Windows features) and enable (Virtual Machine Platform)
  2. Go to Windows services and make sure that( com+) service and VirtualBox system service are running.
  3. Deleting C:\Users[Username].VirtualBox. maybe help after these steps.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.