Host: Windows 2008 x64 with 2 Gb of RAM
Guest: Debian 64bit limited to 980ish Mb of RAM
Issue: A few weeks ago, all was well. I had Virtual Box 4.2.18 running with VboxVMService-4.0-Bayberry, so the VM started each time the host OS booted. The host is not part of a domain. The only account in use on the box is the Administrator account, there are no limited user accounts. I changed the Administrator password on the host by using ctrl-alt-delete and changed the old password to a new one. I rebooted the server, and the VMS service failed to start. I recalled that I had given that service the admin credentials, so those would need changing. I changed the credentials to the new password, and the service still failed to start. I uninstalled the VboxVMService completely, and rebooted the computer again. At this point, I tried double clicking on the Oracle VM Virtualbox icon on the desktop, and after about 30 seconds, I received an error with this info:
Code: Select all
Failed to create the VirtualBox COM object.
The application will now terminate.
Callee RC: CO_E_RUNAS_LOGON_FAILURE (0x8000401A)
- 1) Rerun the VirtualBox-4.2.18-88781-Win.exe installer, chose repair. Rebooted the box, tried to manually start the Oracle VM Virtualbox, and continuted to get the same error.
2) Use Windows Add/Remove to uninstall Virtualbox 4.2.18 completely, but leave the disk image untouched.
3) Reboot, reinstall, try to start, same error.
4) Uninstall 4.2.18 again, reboot.
5) Installed current stable Virtualbox, VirtualBox-4.3.18-96516-Win.exe.
6) Trying to start again gives this same error.
Code: Select all
c:\Program Files\Oracle\VirtualBox>vboxmanage.exe list vms
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_RUNAS_LOGON_FAILURE (0x8000401A) - The server p
rocess could not be started because the configured identity is incorrect. Check
the username and password. (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or
failed to start.