It is hard to tell from a distance what is going on. But here are a few things to check. Make sure all of the users have full access rights to the install directory for World Community Grid. Double check that the program in the startup folder is pointed at UD.exe within that install directory. Make sure they are all pointed to the same install directory and that the startup folder link gives that directory as the "Start in" folder too. If the "Owner" id has it both in the Owners and shared startup folder, remove the one in the Owners startup folder. You might scan your disk to see if it might be installed in more than one place somehow. If the agent is installed in some sort of temp directory where some of its files might be erased or overwritten by something other than the agent software, then that might cause this problem. You might want to run a full virus scan with the latest updates to make sure a virus of some sort is not being launched (which might be damaging the agent files) when the "Owner" id logs on. That is all I can think of at the moment that might cause this problem.

Question. The only change you made was moving the startup shortcut. If you create a second shortcut (to UD.exe) and put it on the desktop as Owner, what behavior does it give you if you click on it manually? (assuming that the Agent is not running for Owner) What I want is to check on the one change that you made to the system. This is not normal behavior.

The file cs.ud contains your registration. So if this is erased, or the agent does not have write access to it, it will act like it has to reregister.

You might scan your hard drive for other copies of ud.exe and cs.ud.

What happens if you go ahead and register the agent under the Owner id?