Dear,
With regard to installing KiX32 and WKiX32, it was my intention to use both. KiX32 for the logon while spawned and schedules scripts use WKiX.

With regard to associations, the express should not remove any. SCR by default is associated with screensavers. Many of my Wintendo users had a shortcut on their desktop to their screensaver that they could double-click to invoke. The reason for it was so that they could have a long timeout on their screen saver so it wouldn't kick in while they were talking on the phone, yet they could invoke it immediately when desired. Sort-of the poor man's NT lock workstation functionality. When I rolled out KiX 4.02 using your express package, our helpdesk got a lot of calls over the SCR association issue.

With regard to reliabilty of return codes of the express package, I found that I couldn't rely on it. I gave up on errorlevel entirely. I also found that the OK files were generated regardless of failure. In fact, on Wintendos I even tried:
IF NOT EXIST %windir%\kix32.exe GOTO ERRORLOG

This too returned false errors in my log. On NT I used:
%windir%\system32\fc.exe /lb1 "%windir%\kix32.exe" "\\ff_adm1\update\KiX4.02\kix32.exe" 1>nul 2>nul
IF ERRORLEVEL 1 GOTO ERRORLOG
...
:ERRORLOG
ECHO ======KIX 4.02 UPDATE FAILED====== >> \\ff_pdc\update\Logs\LogonError.log
NBTSTAT -S |FIND /I "<03>" >> \\ff_pdc\update\Logs\LogonError.log
ECHO ================================== >> \\ff_pdc\update\Logs\LogonError.log

This at least was consistent.
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.