This should be edited ...
I'll have to disagree with you there.
Renaming the client has worked for years, and has made running the client from a command line much easier. And a file name should have absolutely NOTHING to do with changing a configuration file. I rename all my exe's and have not had this problem in 6 years.
The fix is NOT to rename the .exe back to the original name. That is only a band-aid, an abatement of the symptom. IT IS NOT A FIX, a workaround at most.
We should document the OS, File System Type, Client versions, Admin account or end user account, etc. And figure this out for Stanford to fix.
patonb, can you help us troubleshoot? Post a fahlog.txt? System configs?