I assume this is designed behavior, just never noticed it before. I created an account for a friend and when she signed in my pair of GPU running milkyway (or collatz) showed status of "waiting to run" but in any event they only started back up when I logged her out.

CPU tasks were all left running unlike the GPU.

Notice that boinc somtimes started a new gpu task, for example milkyway, instead of continueing a partially run task such as collatz. ie: collatz was left "waiting to run". But that might be a function of whether a cpu or %50 of a cpu was available as cpu tasks continued to execute when she was logged in unlike the gpu ones.


I also noticed that when she logged in I could momentarily see the boinc command shell run which is configured in the registry as
"C:\ProgramFiles\Boinc\boinc.exe" --detach --allow_remote_gui_rpc

Was wondering if there was some way to configure my system so the GPU tasks would continue to run just like the CPU tasks.

[EDIT] boinc (V) 7.8.3

It's more an issue with the way gpu drivers work than anything else. It would appear that your second user is triggering the windows rdp drivers into life, and they don't support computation :-(
There are other remote desktop tools that don't use these drivers, but as I don't remote into my windows computer I'm somewhat out of date as to what is good, bad or indifferent.

No, the drivers are the same - IIRC the problem is that a program started by the first user can't use drivers running under the second user's account.

I did some work with Rom Walton on this - that says how long ago it was. I think the best the second user can do is to shutdown BOINC and start it again in the second account. Then you have to repeat the process when the users swap again.

That's dredged up from a very old memory - I'll go and have a delve in the archives again.

Found some work on shared user logs under fast user switching - v7.3, March 2014: [boinc_alpha] v7.3.8 - 'all users' installation testing

But nothing on GPUs yet.