> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/create-element-repository/capturing-elements-in-avo-assure/capturing-desktop-elements/finding-process-id-process-name.md).
# Finding Process Name or Process ID
When the window name of an application is not available, you can use the Process ID (PID) or Process Name to uniquely identify and target the correct running instance. Providing the PID or process name ensures that Capture targets the correct running application instance for automation. This article describes how to locate the PID or Process Name and use it in Avo Assure Capture to launch the desired application.
## Finding a Process Name or Process ID
To find a Process Name or PID, perform the following actions:
1. Right-click the taskbar, and then select **Task Manager**.
2. Select the **Details** tab.
3. Locate the application process you want to capture.
{% hint style="info" %}
**Note**: You can use the search box in **Task Manager** to quickly find the required application.
{% endhint %}
4. Note the **Name** or **PID** value for the application.
5. In the **Avo Assure Capture** window, enter the PID or process name into the **Enter Window Name/Process ID/Process Name** box.
6. Select **Launch** to open the specified application.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-element-repository-section/create-element-repository/capturing-elements-in-avo-assure/capturing-desktop-elements/finding-process-id-process-name.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
