Darren,
What OS platform/version?
Which Kix version?
Can you provide the results of a "GPRESULT /R" command? You might have conflicting GPO settings - wouldn't be the first time I've seen that, especially if your environment has had many admins supporting it over time. Once you get this report, you can look at the GPOs and see if more than one might be setting the login script visibility values. Also - confirm that this is set in the user profile and you aren't running a GPO based logon script.
The latest version of W-10 defaults to use PowerShell instead of the command prompt. I didn't see this issue when I tested this release a few weeks back, but forcing CMD.EXE to start Kix would resolve any issue that PS had launching it, so something to consider if you're on release 1703.
Also - running Kix32.exe without args is supposed to find/run "Kixtart.kix", but some versions were buggy and did not start this correctly - that's why it's preferred to always specify the script, even in the batch file.
Glenn
_________________________
Actually I
am a Rocket Scientist!
