Glenn,

Adding an automatic association on your own system is one thing, but adding it to your user's Workstations is where the possible issue may arise.

VBS is automatically associated by Microsoft and that is what allowed the rise in VBS script type viruses. Nothing is evil about WSH and the VBS language, but rather how it was used for evil intent.

Most Enterprise email systems now days automatically either block or strip out .CMD .BAT .COM .EXE .VBS .HTA etc...

Scripting languages allow a much greater ability to silently damage a system then just a typical .BAT alone can.

By setting up your desktops to have a file association with KIX32.EXE or WKIX32.EXE will place KiXtart in the same predicament as Windows Scripting Host and VBS files.

No one thought anything about VBS accept a useful scripting tool until someone came along and used it in a negative method in the form of MELISSA

I don't think any of the Antivirus vendors write any code to try and trap a rouge KiX script as they do now days for VBS files. One could some day perhaps get hammered by an email sent to users that would run a KiXtart script that damaged their system just like a VBS file can. By not associating KiXtart the ability to perform such a task is extremely minimized.

Hopefully the above scenario would never happen. However, one needs to reason why you really need the association and if the benefit outways any possible risks.