Skip to main content

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on the installation. So instead of increasing our delay to God-Knows-How-Much , we went for another approach. That is to continuously try to kill the process ( after a certain  delay ) until it is actually out of the task list. This would mean  a:) continuously monitoring the task list to see if the process is still alive b:) create a loop that will do the monitoring of the task list, try to kill the process, delay for some time and repeat again. 

Here is a simple script that my friend came out to solve the issue. She used TASKKILL to kill the process, TASKLIST to list the currently running process, a temporary file to dump the task list result, PING command to add delay and some FOR and IF statements. This worked on XP machines and also tested on Win2003 machines.

    TASKKILL /F /T /IM MyProcess.exe
    echo delaying for 35sec...
    ping -n 1 -w 35000
    TASKLIST /FI "IMAGENAME eq MyProcess.exe" /NH > tmp.txt
      FOR /F %%A IN (tmp.txt) DO (
      IF /I "%%~A"=="MyProcess.exe" (
          GOTO Loop
    del /F /Q tmp.txt

REM Continue the installation process here, after MyProcess.exe has been killed.


Instead of 'ping -n 1 -w 35000' one could use the timeout utility (e.g. timeout /T 35).

The creation of temp file is not really needed. If Command extensions are enabled (SETLOCAL ENABLEEXTENSIONS) FOR can execute a utility and then parse its output
FOR /F ["options"] %variable IN ('command') DO command [command-parameters]

See "FOR /?" for more details...

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :


Get Started with MongoDB Stitch : The New Backend As Service Offering from MongoDB

Halfway of this year, the guys from MongoDB launch their new backend as service product called MongoDB Stitch. While the launch is just for the beta, the promise of the service is quite interesting. MongoDB has been around for long now and some development stacks have been based on its database product, the MongoDB-ExpressJS-Angular-NodeJS (MEAN) and the MongoDB-ExpressJS-React-NodeJS (MERN) stacks to name a few. These stacks, however, relies on backend technology such as ExpressJS and NodeJS. The idea of provisioning servers and developing the backend solution makes it daunting for small to medium scale applications. MongoDB Atlas, at least made life much easier by providing on cloud database solution, but there must be a simpler solution, right? A solution the would stitch the backend and frontend together ( see what I did there ?).
MongoDB Stitch lets developers focus on building applications rather than on managing data manipulation code, service integration, or backend infrastruct…

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless