Has anyone found such behavior when Command Processor (cmd.exe) closes immediately after calling it?
I’ve run McAfee AV and Windows System File Check (sfc.exe) and nothing wron
This is a shot in the dark, but I have seen problems like this in the past when incorrectly specifying a debugger via Image File Execution Options. You might check to see if there's an entry for 'cmd.exe' there.