virtualbox.org

I am running 6.1.14r140239:

Host: Windows 2012r2
Client-1: Windows 2016
Client=2" Windows 10
The windows 2016 client starts on boot via the Task Scheduler.
Windows 10 client is used as needed

Invariably overtime the VirtualBox Manager loses the client machines. When this occurs. the client instances running are unaffected. A reboot of the host server resolves the issue until it reoccurs, typically it takes a week.

Going around the VirtualBox manager to start a client using the command line:
C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm "PERS-WIN" --type headless
Returns:vBoxManager.exe: error Code ERROR_KEY_DELETED 0x8000703FA (0x8007033FA) - ERROR_KEY_DELETED
(extended info not available)
vBoxManager.exe: error: Context: "FindMachine(bstr(pszVM).raw(), machine.asOutParam())" at line 722 of file VBoxManagerMisc.cpp

To confirm the client machine is correct, I entered a bad client machine name and the command returns:
error: Code VBOX_E_OBJECT_NOT_FOUND again line 722 VBoxManangerMisc.cpp

Thanks!

Attached is an image of the VirtaulBox Manager UI and the cmd line

Virtualbox keeps its configuration file, including the guest list, in the logged-on user folder "C:\Users\{account}\.Virtualbox". If you registered the guest on one account it won't show up on a different account until you register it there too.

Guests started via Task Scheduler may not show up as running in any account or in only one account.

Register your guests in every account you log onto and you should then see them in every account.

Thank you for responding, however, I do not believe this is the issue.

Everything is done using the local administrator account on the host server, which is not part anyway, it is a standalone server. All interaction including the job in task scheduler is done with the local administrator account.

The issue I am experiencing is interaction on the host works propery for about a week, then the vb manager loses visability, and command lines stop working.

In the case of the error, please check if the VBoxSVC process is still running, and if the file .VirtualBox/VirtualBox.xml in the local administrator's user directory is still accessible by the local administrator and the SYSTEM accounts.