Looks like this version has now been pushed to the latest stable release. Just upgraded on my Win11 machine and everything seems to be working fine so far.

It's not necessary to micromange like that. Set your other "backup" project to a priority of zero. If your primary project runs dry, BOINC Manager will automatically download work from your backup project, until work is available from the primary project again. That's what I have set up. No additional management is necessary.

BobbyB -- Paul will probably reply, but the way to do that might depend upon whether you use the Device Profile Mgmt from the Backup Projects website (you can determine this under the Options | Computing Preferences menu in BOINC Mgr).

If you use BAM! or another Account Mgr, you'd set it there.

Or, if you have the Activity Preferences set in the BOINC Mgr under the Activity Menu to override on each client (i.e. - local prefs) -- you'll have to create an app_config.xml file in whatever is the backup Project's directory (unsure if you have Linux or Windows, for Windows it's down in C:\ProgramData\BOINC\projects\ -- I'd have to go look on my Linux boxes to tell you where it's at there).

I'm sure there's a thread someplace on this forum explaining this, but I couldn't readily find. Look at this for a hint:

https://boinc.berkeley.edu/wiki/Client_config...oject-level_configuration

And also toward the bottom of this thread with a post by Tom M (you'll need to substitute whatever is your backup project's name in that app file since they're talking about SETI and limiting WCG -- you'll want to go the other way around and limit your backup project until WCG runs dry):

https://setiathome.berkeley.edu/forum_thread.php?id=81592

--

Perhaps someone will find a thread with a step-by-step explanation but if not, the above can be used to reverse-engineer and make this work. Once you do it, it'll be a "set and forget" instead of having to manually adjust all the time.

Hope this helps...