When a pipeline job is terminated while executing a batch script, it will sometimes continue running the batch file after terminating the batch file's child process. This means you cannot reliably check if the process was terminated by Jenkins or if it exited normally. See attached script and log.

To test, run the attached pipeline script and terminate while in the middle of pinging. Most of the time it will continue to run the batch file after jenkins kills ping. I would expect the batch file to also stop.

I've also attached a log of where ping terminated but the job hung and had to be force killed. (but probably related to the other bat issues)