quote:
Works just fine like this so is it possible that the first place it will look it the current directory?
Yes, and no.

Without the extra secure settings the KiXcrypt simply calls %COMSPEC% with the executable name, and I guess the spawned interpreter will conform to the DOS convention of locating the executable including the brain-dead "look in the current directory first"

However, the kix32.exe executable is not compiled into crypted.exe. What this means is that it won't (necessarily) use the executable in your C:\Something directory when it runs, it will use the first one that it finds on the client PC. This is by design.