Using Spark 2.5.8 on both XP Pro SP 3 and Vista Business SP 1 using different accounts (and trying same accounts from XP) whenever I logout starter.exe starts running. The problem is that it does nothing but consume resources so after a few logouts there are multiple instances running using 9mb of memory and 20mb of virtual memory. The initial shortcut used runs spark.exe as created by the installer.
The accounts I have tried do NOT have their password saved and auto login is off. The accounts being used to run spark are administrators on both machines.
Another user account and openfire user on the Vista machine with the password saved and auto login on also has the starter.exe run when they log out. This user account is not an adminstrator.
Either starter.exe should not run or if it is meant to do something, only one instance should be allowed to run if only one instance of spark can run.
Starter.exe is used to start Spark.exe when you do Log out. Because Spark is programmed in a scuh way, that it quits completely when you do log out. Then starter.exe should close. And it does this for me with 2.6.0 Beta 2. Maybe you should try Beta or the latest version from here http://www.igniterealtime.org/community/docs/DOC-1822
Just answered my own question about making starter.exe ‘disappear’. Renamed it starter.exex and now Spark actually quits faster and the starter.exe does not run.
I’ll take this as a working solution till 2.6 is out.