Solved Is it possible to end a task/process using a .bat file in Windows 11?

Stormbow · Mar 3, 2023

Windows 11 Version 22H2 (OS Build 22621.1265)

One of my favorite things about Windows 7 was using .bat files to close all processes associated with whatever I was doing— after saving my work, where applicable of course. It was one of my life's simple joys to click one thing— actually, I press 1 macro key on my keyboard, which executed a .bat file —and close the game I was playing, my voice controls for the game, my voice chat program, and any other related software.

An example of my old .bat file looked like this:

Batch:

@echo off
@echo Terminating chosen processes...

taskkill/F /IM "game.dll"
taskkill/F /IM "voicebot.exe"
taskkill/F /IM "discord.exe"
taskkill/F /IM "hotkeynet.exe"

exit

But since I've finally skipped Windows 8 and 10 to jump straight into 11, I find this .bat file doesn't work anymore.

Is it possible to accomplish this same feat in Windows 11? Could someone please provide me with a .bat file example, if it is?

Many thanks for reading, and for any help anyone may be able to offer.

LesFerch · Mar 3, 2023

Cmd shell (batch file) commands work the same in Windows 11. I would put a space between "TaskKill" and "/F", but that does not appear to be the issue.

We need to see error messages. Open a Cmd prompt and try each of those individual commands and see if you get any error messages.

BTW, killing is not the same as closing. Programs should be closed properly whenever possible to avoid open handles that may lead to other issues or even data corruption. Yes, for some processes you can get away with killing without any adverse effects, but it's not a good habit in general.

Archigos · Mar 3, 2023

As LesFerch stated, it'd be easier if you take a screenshot of you trying to run that so we can see the exact errors.

I'm thinking it's the *.dll that you're trying to kill that is giving you the error.

Ben Myers · Mar 3, 2023

Be sure to run the batch file with administrative privileges.

Ben

LesFerch · Mar 3, 2023

Ben Myers said:
Be sure to run the batch file with administrative privileges.

If the processes were started by the user they can be killed by the user. We need to see the error message(s) to know for sure.

Stormbow · Mar 5, 2023

Wouldn't you know it... As soon as I finally ask someone for help with it, I figured it out— for some reason I'd changed from using "name.exe" to "window name" in the new /bat files, and that was 100% of why it didn't work. I should know better than to attempt to recreate things from (failing) memory. LOL

Thank you all very much for attempting to assist me! I do appreciate it very much.