Task Scheduler for VM launch at boot issue

[truxartus]

Greetings all,

Hopefully this issue hasn't been asked before, I'm assuming it hasn't as I've yet to find a post that matches my circumstances. I've been running into an issue on a system where I've set a Task Scheduler event to launch two VMs at boot. What occurs is that when the system boots up, I get the following error:

There is no virtual machine with the identifier 8a3e01db-822f-44fc-8a0b-c4b73e95ecfc.

Could not find a registered machine with UUID {8a3e01db-822f-44fc-8a0b-c4b73e95ecfc}.

Result Code: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Component: VirtualBox
Interface: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554}

I've checked the VirtualBox.xml file to make sure there is no entry with the UUID mentionned by the error, and I can find nothing that matches. Only the UUID of the two VMs that are installed on the machine that I am trying to launch at boot. I've also double checked the Vbox files of both VMs to make sure the that UUID isn't listed there, which it isn't. Only the valid UUIDs of the VMs are in the Vbox file. What's odd is, testing the Task Scheduler event doesn't cause this error to occur. It only seems to occur on boot. I'm running the latest version of VirtualBox and I'm at a loss of what to try next to try and get rid of this error. Are there any other files I should be looking at that might also contain VM UUIDs beyond the files I've noted above?

Any help with this matter would be greatly appreciated.

[Martin]

The Task Scheduler needs to run in the same user context as your normal user account to see the VMs.

[truxartus]

Just to clarify, the event task is running as the correct user. For some reason, Virtualbox is trying to start a VM that doesn't exist along with the other two VMs.