Question

I tried to wrap a little command in a batchfile to prevent me from typing it the whole time. But the result was a mess! I’m ended up with thousands of cmd processes and was unable to stop it with CTRL+C

The command was quite simple START iisreset

System Win7 64bit

Why is that happening?

EDIT:

With some help and additional tests I can now say that the Batch command START within a *.cmd file cause that mess. It opens a new commandwindow with every window until it crashes. Maybe you have luck and hit CTRL-C exactly the right time, but that really has to be luck. Anyway I will not use this command in future and it also seems not to be applicable to all machines. (Read the comments for full history of this)

Answer 1

It works OK on Windows 7 pro, 64 bit, but based on the other stuff you’ve tried, it looks like it might be a bug… You could try raising a bug report
(although that seems like a non-trivial exercise).