I am trying to terminate adb.exe on my Windows machine. I am using taskkill /F /IM adb.exe /T to do this. However each time I do it, 3 adb.exe instances come back into the task manager process view. Something is restarting them.
I'm trying to do some connection-between-virtual-machine stuff and I need adb.exe to die and stay dead on the Windows host, because it is interfering.
How do I identify what is restarting these processes? Or otherwise make adb.exe stay dead without doing extreme stuff like temporarily deleting it from the Windows host?
Extra notes: When I run the taskkill, a process group called "Service Host: DCOM Server Process Launcher" jumps to the top of the process list at 20% cpu, so maybe it's what is responsible.
No, adb kill-server etc is no more effective.
It may help you if you look at process explorer. It resolves process trees and may lead you to the starting process.
https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx
However, if I start the adb server through a command promt, it shows adb.exe as subprocess of cmd.exe only for some seconds and then gets handed up as independend process. You might want to have the process explorer open and monitor the restarting procedure of adb.exe.