title: CMD.exe closes immediately after calling (Win7 64)
body: <p>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 wrong was detected, I’ve even copied cmd.exe file from other win 7 machine and it is still working same way.
  Strangest thing is – on the windows 7 64 there is also 32 bit version of that file which works perfectly normal. </p>
  
  <p>SysInternals Process Monitor shows that cmd.exe process ends with exit code 0x0... o_O</p>
  
  <p>Also calling commands directly from start menu, like ping, works normal… </p>
  
  <p>Maybe that question is not strictly related to coding but that issue holds me from doing many things related to actual application development and environment check.</p>