powered by Jive Software

BUG: Launch at startup

When you tick the “launch at startup” box, Spark creates a registry entry under HKEY_USERS{SID}\Software\Microsoft\Windows\CurrentVersion\Run

Spark - C:\Program Files\Spark\KYWINS.exe

Firstly, this should be in quotes, otherwise the launch will fail because Windows is unable to find C:\Program. Secondly this file doesn’t appear to exist.

Am I wrong? Should this executable exist?

Maybe this is some permissions problem. I have installed Spark with admin rights. And then i launch it with user and select that checkbox. Registry key with value “C:\Program Files\Spark\Spark.exe” appears in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

I wonder why it puts startup entry to HKEY_USERS in your case. There is no kywins.exe in Spark. Maybe this is Windows appending such name in that case. But i’m clueless why this is happening for you.

This should not happen. KYWINS.exe does not exist except for a custom client built for Kentucky. I have launch at startup enabled on every computer in my company. I did a scan of various registries and there is no reference for this program. Which version of the installer did you use, exe or msi?

This has been discussed and is still OPEN. http://www.igniterealtime.org/community/thread/30966?tstart=0

I knew this discussion was familiar. This would be a very good topic for open chat tomorrow. A little pressure could go a long way. So please block your schedule for the open chat at 1PM eastern time.

It would also help to know which MSI you are using (msi or online msi).

It would be in both locations in the registry as they are one in the same. Make changes in one it will reflect in the other.

I have confirmed this via the standard MSI file.

This has been filed as an issue: http://www.igniterealtime.org/issues/browse/SPARK-986. I also filed an issue for spark having the incorrect icons for the desktop and start menu which I discovered while investigating: http://www.igniterealtime.org/issues/browse/SPARK-987

Offline MSI, though you now appear to have verified this.