How to get (and kill) a specific process on an application?

[Raj222]

How can I find the specific process name and kill it?

For example, I have this Microsoft application open, and there can be multiple windows open on the application. Let’s say I am working on an open window A on the application.
When the robot tries to close window A like normally (e.g. attach window => close window), and if it fails, I want to just kill that window only, but not the entire application.

I cannot find the process name for that specific window, and I want to know how I can.
As of now, all I can do is, kill the entire application, but that’s not what I want. I want to kill only one specific window on the application, keeping the application itself open.

[prasath17 (Guru)]

@Raj222 - Normally Ctrl+w most often used for Close a program …See what is the shortcut key available for that application and use Send Hotkey/keyboard shortcuts.

[ppr (Peter)]

@Raj222
have a look here:

KillAllProcesses give me an exception

@Chand we encountered similar issues and after an RnD we worked out apattern close to your scenario: Set up a String List with the process names that get to kill. This can be done also with values from the config [grafik] here we go with OUTLOOK, EXCEL, iexplore then try to retrieve for each process name the process as long all are killed: [grafik] for each is iterating over process name to kill list while is killing the particular process so often till no one longer is existing We did…

And here:

How to kill process for specific (current) user

@Sajid_Masood with myPID = Process.GetCurrentProcess.SessionID you will get a marker of current user getting the processes by name currentProcessByName = Process.GetProcessByName(YourProcessName) filtering to current user: UserProcess = currentProcessByName.Where(Function (x) x.SessionId=myPID ).toArray for a defensive kill have a look here and just combine both approaches:

getting the PID/TID for the window and matching it to a process / thread was not reliable enough. So we defined the best practice of killing all Processes.

[Raj222]

Thank you. The reason why I asked this question was because, sometimes there are so many different types of pop-ups when closing the window. I don’t want to handle each of them because there’s so many. I thought just killing the window itself is the easiest.

[Yoichi]

Hi,

In simple case, the following might work for you.
(But there are many complicated cases, and this might not work.)

Main.xaml (8.1 KB)

[Raj222]

thanks! Unfortunately, this didn’t work in my situation. I tried it, but the condition always failed. But this answer is so far the closest to what I want to achieve.

[Yoichi]

Hi,

Thank you for trying.
I guess it’s because your target window isn’t Main Window of a process.

Perhaps Win32API GetWindowThreadProcessId will solve your matter. However it’s difficult to call this in default UiPath Studio.

GetWindowThreadProcessId function (winuser.h) - Win32 apps

It might work to create custom activity for it in Visual Studio or use the following custom activity, for example.

Tip: How to use Win32 API Calls or Win32 DLL Functions

In the last days I was looking for a way to realize Win32 API calls without additional packages. Surely this is a rather rare requirement, since almost everything can be handled via the dotNET framework. However, sometimes there are use cases where this may be required. Especially in the environment of older applications there may be Win32 libraries whose functions can be used on this way. In the main thing the Invoke Code activity calls another C# provider, which offers the possibility to perf…

Regards,