# pad.bridgetouiautomation2.exe

Process: Microsoft

Catalog search terms Bridge to UIAutomation2

Recorded role: This process bridges Power Automate Desktop workflows with the Windows UI Automation accessibility framework.

## What you need to know

Feex's process catalog associates this filename with Bridge to UIAutomation2.

Check the running file before relying on the catalog identification.

- **Does this name prove the file is safe?**: No. Verify the running file, its digital signature, publisher and behavior. The name alone is not enough.

A filename alone cannot establish that a running file is safe. Check the full executable path and digital signature, confirm the signer against the publisher, and investigate unexpected behavior with Windows Security or vendor guidance. A familiar folder or a valid signature alone is not a guarantee.

## What the catalog records

| Executable name                 | pad.bridgetouiautomation2.exe |
| ------------------------------- | ----------------------------- |
| Associated product or component | Bridge to UIAutomation2       |
| Recorded publisher              | Microsoft                     |
| Catalog classification          | Helper                        |

## Recorded role and behavior

This process bridges Power Automate Desktop workflows with the Windows UI Automation accessibility framework. It allows desktop flows to inspect, interact with, and manipulate graphical user interface elements in other applications. It runs quietly whenever UI automation actions or recording sessions are executed.

## Inspect the running instance

In Windows PowerShell, this read-only query lists matching process IDs, creation times and executable paths on this PC.

`Get-CimInstance -ClassName Win32_Process | Where-Object { $_.Name -eq 'pad.bridgetouiautomation2.exe' } | Select-Object ProcessId, ParentProcessId, CreationDate, Name, ExecutablePath | Format-List`

No result or an inaccessible path is inconclusive. Protected processes may restrict access, and process IDs can be reused. Keep personal paths local.

Use the [file-identity guide](https://feex.it/wiki/software/system/verify-executable-path-signature/) to compare signatures and product metadata. A filename alone cannot establish safety.

## Identify the actual running file

A filename alone cannot establish safety. Compare the actual path, product metadata and digital signature with the software you installed.

## Investigate a problem safely

Compare repeated observations for the same PID while the symptom occurs. A single CPU peak or memory reading is not a diagnosis.

Save work and use the associated application controls to reproduce the symptom. Confirm the product identity before following its official update or repair guidance.

## Evidence and corrections

The role and publisher are catalog associations. The references explain file checks, not the product association or your file's safety.

For corrections, send the article URL and public product documentation through Feex contact. Keep personal paths and credentials private.

## Related

These entities connect to this article. Type is shown on every link.

[How to check an executable path and digital signature: Guide](https://feex.it/wiki/software/system/verify-executable-path-signature/)[Read Task Manager and compare process activity: Guide](https://feex.it/wiki/software/system/how-to-read-task-manager/)[Application processes: Category](https://feex.it/wiki/process/application/)

## Sources and verification

Editorial ownership: Feex. No independent review date is recorded. [How we research](https://feex.it/wiki/research/).

- [Microsoft Sysinternals: Sigcheck ](https://learn.microsoft.com/en-us/sysinternals/downloads/sigcheck)· File-version and digital-signature inspection method.
- [Microsoft Sysinternals: Process Explorer ](https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer)· Process-tree, module and handle inspection method.
- [Microsoft Support: Virus and threat protection ](https://support.microsoft.com/en-us/windows/security/threat-malware-protection/virus-and-threat-protection-in-the-windows-security-app)· Windows Security scanning guidance.
- [Microsoft: Get-CimInstance ](https://learn.microsoft.com/en-us/powershell/module/cimcmdlets/get-ciminstance)· Read-only local process-query method.
- [Microsoft: Win32_Process properties ](https://learn.microsoft.com/en-us/windows/win32/cimwin32prov/win32-process)· Documents process IDs, executable paths, creation dates and parent-ID reuse.

[Report a correction to Feex](https://feex.it/contact/)

## Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.

Quick facts

The short identity of this page. Specs, sources, and the full story stay in the article.

- **Executable**: pad.bridgetouiautomation2.exe

  **Catalog product**: Bridge to UIAutomation2

  **Recorded publisher**: Microsoft

Recorded source status: Imported catalog mapping: Editorial ownership: Feex. No independent review date is recorded.

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/process/pad.bridgetouiautomation2.exe/)

[Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)