LHC@home

Whenever I shut down Windows 10, and Virtualbox is in use (eg an LHC task), Windows says "Virtualbox has active connections". I can force it to stop, but if it's a remote computer this is annoying or very difficult to do, and it doesn't seem right to force stop a running project. If I wait, Windows eventually gives up and goes back to the desktop. Sometimes if I try to shut down again, it works, but sometimes I get the same error message again. I've done a Google search and this seems to have been a problem for years. Is this a Virtualbox problem, a Windows 10 problem, a Boinc problem, or an LHC problem?

---

You should give vboxwrappers the time to save the virtual machines to disk before shutting down the OS.
Simpliest method is to stop BOINC's client ahead and wait some minutes.
Even better is to suspend all tasks 'ready to start' first and then the running VBox-tasks one after another with some time interval.
Leave non-GPU tasks in memory while suspended should not be ticked in computing preferences.

You should give vboxwrappers the time to save the virtual machines to disk before shutting down the OS.
Simpliest method is to stop BOINC's client ahead and wait some minutes.
Even better is to suspend all tasks 'ready to start' first and then the running VBox-tasks one after another with some time interval.

Sorry, but every other program responds to my request to shut down within seconds. There's no reason VB ignores me. Windows 10 can hibernate the machine in seconds, so why can't VB "hibernate" it's own system in seconds? Both are writing the RAM to disk, which I see no evidence of as there's no disk activity. I'll just have to click "shut down anyway". Your suggestion is actually more work for me.

Leave non-GPU tasks in memory while suspended should not be ticked in computing preferences.

But I was told to tick that to prevent VB from having problems due to Boinc pausing it often to switch between projects or for exclusive applications.

---