Hi,

The 4.1 release on the beta forum may very well fix this issue.

Your version...
What is probably happening is that your .bat file is paused or blocked somewhere.
As the option "don't wait for .bat files to complete" is NOT checked by you, WD is waiting for the .bat to quit. The loop where it waits is checking the output of the .bat (even if you didn't select "capture output") and writes it to WD's window. When your .bat is blocked, WD will, in some bizar circumstances, run a very tight loop that will consume all cpu on the current processor (multi processor) or core (multi-core). Not sure how it would run on hyper-threading cpu's, but 50% seems logical.

4.1: when WD detects the strange situation, it will try 20 times (0.5 second interval) to see if the .bat writes anything. If it does WD continues to wait for it (and reset the "20 counter" to zero). If after 20 attempts (10 seconds) there is still no output from the .bat, WD will give up waiting, and the next event will be processed.

Gert