Brief History of the Application
The idea of KillProcess came up during development of another much larger and more complex application.
This application would spawn a lot of other processes, and also depended on other applications spawning their own processes to communicate with the main application. A general run of this nasty application would start up something like 7 different processes all over Windows, all depending on eachother. This was a real pain while still in development, since the main application would behave rather strangly and crash or hang alot (like 40 times a day).
This all ment that it would literally take forever to clean up the orphan processes all of the time (since they where GUI-less). This was why KillProcess was born.
KillProcess lets you create an list of processes that should be destroyed and then perform an "batch-type" run on the list, killing of all of the processes listed.
The KillProcess application can terminate almost any application on an PC running Microsoft Windows, including Windows Services and applications being debugged (but not while at a breakpoint) in a matter of millisecond. This is more powerful than the Windows TaskManager, which also has an delay to wait for applications to "die" gracefully. KillProcess is also free from stupid questions that asks you if you are really sure that you now what you are doing (well there actually is such questions, but you can disable them). The Windows TaskManager also cannot terminate multiple processes at the same time, which is something that KillProcess is really good at! Either have the processes in your kill list, or select them in the process list and "kill" them manually.
KillProcess includes a nifty process tracker, which can prevent any process in the system from starting to execute, and thus releasing precious CPU resources to applications that should be running instead. This is great if you for some reason would like to prevent the network administrator from running a nasty virus scan application on your computer while you are making a huge animation or code compilation that consumes a lot of computer resources.