Work around Windows UIPI blocking pywinauto from controlling a UAC-elevated application

Steps

1. Diagnose the symptom first: an elevated target app whose windows pywinauto can see via Desktop().windows() but can't reliably click or send input to, or that errors with an invalid-window-handle-style failure, is a strong UIPI signature
2. Confirm the integrity-level mismatch by checking whether the target app was launched elevated (shows a UAC shield or was started via Run as administrator) while your Python process was not
3. Run the pywinauto script itself elevated, for example by launching the terminal/IDE as Administrator, so both processes share the same integrity level
4. Where elevating the whole script isn't desirable, isolate elevation to a small elevated launcher process and keep the bulk of the automation logic in a non-elevated caller
5. For CI/service accounts, ensure the account driving pywinauto has matching elevation for both the target app's launch and the automation process, since scheduled/service-launched apps can end up elevated without an interactive UAC prompt