bobjohnson1983

I've had the same issue. The real catch is getting the run/CMD prompt started/removed quickly. A thought: could you run the silencing piece of the script first, then using the batch file to run the exe? This may shorten the exposure length that the run and CMD screens are visible...