EEP! indeed.

Jim, can you confirm that you are using version 2.12b?

I've not come across this one before (natch) so any details you can give would help.

KiXcrypt should not output to a file that it cannot delete or overwrite, so the files *should* be deleted, or nulled. KiXtart files contain there own sematics for deleting the file (unless you specify the "-k" switch), so the file is deleted in at least two diffetent places.

Can you confirm that the temporary files contain the script (rather than created empty)?

If you are calling the encrypted script from a batch file you may want to change directory before running it to a known safe directory (%TEMP% or similar) - the temporary file is created in the current working directory, and if you have locked down access to the users root drive there might be some permissions weirdness going on (raised permissions during logon?)

The only way I can think to cause the files to be left behind is if the "-k" flag has been used to defeat the KiXtart script delete semantics, and the KiXcrypt script abends or is killed.

If changing the directory doesn't help, please answer the questions above and include details of your environment.