Renaming the service likely wont happen until the next major release, and even then most likely as a side by side service to the current service.  We hear your concerns and will address this in the future.

If I may add, a trojan or a virus seeks to hide from suspecting eyes, not stand out and shout here I am.  The long, readable and identifyable naming convention employed with all of AppLife Updates assemblies does catch your eye and might cause someone to say, "why do I have a Kjs.AppLife...." process running?  But shouldnt stand out as malware.  Thats just not how malware works.  I also suspect that this convention will catch favor as some point and you will start seeing more assemblies named in similar fashion.  Nevertheless, the issue is noted and will be addressed some time in the future.

This reply is a bit late, but I thought I'd update this thread to note that as of the AppLife Update 2.0 release, the update service was renamed to use a short service executable name (kjsausvc.exe).