#Macro-ing UAC Prompts
I was curious as to if I can send <VK_LEFT> and <VK_RETURN> to a UAC prompt as soon as it pops up, a fairly graphical not-really-bypass way to interact with UAC for potential malice.
I thought, how could nobody have done this before? Well, as it turns out, I didn't give MS enough credit. Going into this I didn't understand how Windows handles privilege seperation between window handles.
http://www.vistax64.com/vista-security/67070-uac-blocks-windows-messages.html
http://stackoverflow.com/questions/10562877/why-does-the-sendmessage-function-not-work
User Interface Privilege Isolation: http://en.wikipedia.org/wiki/User_Interface_Privilege_Isolation https://social.msdn.microsoft.com/Forums/en-US/b68a77e7-cd00-48d0-90a6-d6a4a46a95aa/sendinput-fail-beause-interface-privilege-isolation-uipi-and-integrity http://blogs.msdn.com/b/vishalsi/archive/2006/11/30/what-is-user-interface-privilege-isolation-uipi-on-vista.aspx
If I would have used GetLastError() I probably would have figured this out sooner.
Anything trying to inject code or messages to UAC will fail unless it's properly authorized. Sending raw keyboard input would do it, but as far as I know windows provides no way to do this without interfacing with a driver directly.
I was incorrect about the blank window thing being a sign of UAC, the window handle was NULL.