Use PowerShell with FlaUI to find and interact with UI elements of a native Windows desktop app

domain: github.com/FlaUI/FlaUI · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Get FlaUI.Core plus either FlaUI.UIA3 (COM-based, best for WPF/Store apps) or FlaUI.UIA2 (managed-only, sometimes better for WinForms) via NuGet, then load the assemblies in the PowerShell session
  2. Launch or attach to the target app with FlaUI.Core.Application.Launch("app.exe")
  3. Create an automation object, e.g. New-Object FlaUI.UIA3.UIA3Automation, then get the main window with $app.GetMainWindow($automation)
  4. Find an element with FindFirstDescendant using a condition factory, e.g. cf => cf.ByText("1"), and cast it with a helper like .AsButton()
  5. Interact with it, e.g. call .Invoke() on the button wrapper, then read other elements' state back

Known gotchas

Related routes

Automate native Windows application UI using PowerShell and the Windows UI Automation framework
docs.microsoft.com · 6 steps · unrated
Locate and interact with Windows desktop UI elements using FlaUI's UIA3Automation and ConditionFactory
desktop-automation · 6 steps · unrated
Inspect and drive native Windows application UI using Windows UI Automation (UIA) from code or inspection tools
learn.microsoft.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans