Power Platform Community Forum Thread Details

Hi everyone,

I'm facing a persistent issue with Power Automate Desktop. The native host launches correctly, the browser extension is active, but no web elements are detected on standard pages — the red highlight boxes never appear. Interestingly, they *do* appear on internal browser interfaces like `edge://settings`, which suggests that the UI Automation engine is working.

PAD diagnostics:
- Fails in the “Desktop Automation” section
- Reports an MSAA-related error
- Automatic repair fails: “MSAA automation could not be repaired. Run the manual repair utility for more information.”

What I’ve tried:
- Manually registered `oleacc.dll` and `UIAutomationCore.dll` (no errors)
- Launched Edge with flags: `--no-sandbox`, `--disable-web-security`, etc.
- Created a fresh local admin user profile
- Compared with another machine where everything works fine
- Verified that Edge is *not* running in AppContainer
- Ran `sfc /scannow` — no integrity violations
- Checked registry keys under `HKLM\...\Accessibility` — no custom values

Conclusion so far:
- UI Automation works for native interfaces
- DOM access is blocked in web contexts, even with sandbox disabled
- Likely caused by persistent security policies, drivers, or runtime isolation

Has anyone encountered this kind of deep UI automation failure in web scenarios? Any ideas on how to unblock DOM access for PAD in hardened environments?

Thanks in advance!