Kill some processes by .exe file name

C#C++ProcessExeKill Process

C# Problem Overview


How can I kill some active processes by searching for their .exe filenames in C# .NET or C++?

C# Solutions


Solution 1 - C#

Quick Answer:

foreach (var process in Process.GetProcessesByName("whatever"))
{
    process.Kill();
}

(leave off .exe from process name)

Solution 2 - C#

My solution is to use Process.GetProcess() for listing all the processes.

By filtering them to contain the processes I want, I can then run Process.Kill() method to stop them:

var chromeDriverProcesses = Process.GetProcesses().
    Where(pr => pr.ProcessName == "chromedriver"); // without '.exe'
    
foreach (var process in chromeDriverProcesses)
{
     process.Kill();
}

Update:

In case if you want to do the same in an asynchronous way (using the C# 8 Async Enumerables), check this out:

const string processName = "chromedriver"; // without '.exe'
await Process.GetProcesses()
             .Where(pr => pr.ProcessName == processName)
             .ToAsyncEnumerable()
             .ForEachAsync(p => p.Kill());

Note: using async methods doesn't always mean code will run faster.
The main benefit is that the foreground thread will be released while operating.

Solution 3 - C#

You can use Process.GetProcesses() to get the currently running processes, then Process.Kill() to kill a process.

Solution 4 - C#

If you have the process ID (PID) you can kill this process as follow:

Process processToKill = Process.GetProcessById(pid);
processToKill.Kill();

Solution 5 - C#

You can Kill a specific instance of MS Word.

foreach (var process in Process.GetProcessesByName("WINWORD"))
{
    // Temp is a document which you need to kill.
    if (process.MainWindowTitle.Contains("Temp")) 
        process.Kill();
}

Solution 6 - C#

Depending on how many processes there are to kill (e.g. when its hundreds like in my case), foreaching over all of them might take quite a while. (interesting sidenote: while Kill() was usually quite quick in .NET FW 4.8 , somehow in NET 6.0 Windows its a lot slower - seeing multiple Win32Exceptions in the debug/trace until the target process is finally done)

Anyway back to topic: In case of an app shutdown, where u need to make sure every process is is gone, consider using the TAP library - particulary the Parallel shortcuts, hundreds of processes killed within a glimpse.

Usage example:

var procs = Process.GetProcessByName("mydirtyprocesses");

if (procs.Length == 0) return;

procs.AsParallel().ForAll(process => 
{
   try
   {
      process.Kill();

   // No process linked to the process comp (mostly because the process died in 
   // the short timespan between invoking GetProcess() and the effective 
   // initialization of the props/fields of the component. -OR- Process has 
   // already exited (when the exit happened after the process component has 
   // beenpopulated (difference is, in case 1 you cannot even get the Process 
   // ID from // the component, in case 2 you see data like Id and get the true 
   // for HasExited // - so always be prepared for that.
   // catch (InvalidOperationException) 
   {
     // Process is gone, no further action required
     return;
   }

   // Ensuring process is gone (otherwise try again or fail or whatever)
   if (!process.HasExited)
   { 
       // Handle it
   }
}

In this particular scenario just wrap it properly in try/catch , as with such a number of processes the probability for an exception is quite increased

Solution 7 - C#

static void Main()
    {
        string processName = Process.GetCurrentProcess().ProcessName;
        int processId = Process.GetCurrentProcess().Id;
        
        Process[] oProcesses = Process.GetProcessesByName(processName);

        if (oProcesses.Length > 1)
        {
            if ((MessageBox.Show("Application is opened!", "",MessageBoxButtons.YesNo) == DialogResult.Yes)) ;
            {
                foreach (var process in Process.GetProcessesByName(processName))
                {
                    if (process.Id != processId)
                    {
                        process.Kill();
                    }
                }
            }
        }
        else
        {   
            Application.EnableVisualStyles();
            Application.SetCompatibleTextRenderingDefault(false);
            Application.Run(new frmLogin());
        }
    }

Solution 8 - C#

public void EndTask(string taskname)
{
      string processName = taskname.Replace(".exe", "");

      foreach (Process process in Process.GetProcessesByName(processName))
      {
          process.Kill();
      }
}

//EndTask("notepad");

Summary: no matter if the name contains .exe, the process will end. You don't need to "leave off .exe from process name", It works 100%.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionAliasghar YaghoobzadehView Question on Stackoverflow
Solution 1 - C#ConsultUtahView Answer on Stackoverflow
Solution 2 - C#Arsen KhachaturyanView Answer on Stackoverflow
Solution 3 - C#driisView Answer on Stackoverflow
Solution 4 - C#tomloprodView Answer on Stackoverflow
Solution 5 - C#Rakesh Ravi GView Answer on Stackoverflow
Solution 6 - C#TronTronic EntertainmentView Answer on Stackoverflow
Solution 7 - C#Ahmad HamdeenView Answer on Stackoverflow
Solution 8 - C#user7993881View Answer on Stackoverflow