Windows ACT/UAC - RunAsInvoker suddenly not helping

1.7k views Asked by At

I'm hoping someone can help. User Account Control and the Application Compatibility Toolkit have been driving me nuts all day...

I have a USB mouse with programmable buttons; when I first got it, I disovered that they wouldn't send keystrokes to an application running with administrator privileges unless the mouse monitor had also started with administrator privileges.

Without too much fuss, I implemented a workaround by marking monitor.exe to be run as admin, and then used the Application Compatibility Toolkit to set-up RunAsInvoker. Subsequently, the monitor started normally (via HKLM\Software\Microsoft\Windows\CurrentVersion\Run) without a UAC prompt, and buttons mapped to keystrokes were sent to any other running application.

Since then, I've had to flatten the machine (more accurately: restore an image made before the mouse/workaround were installed). I've been trying various combinations of [basic] compatibility settings, registry hacks, and Compatibility Tool profiles for about the last 12 hours, but nothing will get keystrokes into apps running with admin rights.

Oddly, if I mark monitor.exe for 'run as administrator' (for my user or all users) in the compatibility tab on its properties page, and either apply RunAsInvoker by ACT or registry hack, the monitor starts without UAC prompt, but won't send keystrokes to other 'admin' apps. If I close it and restart it (without explicitly commanding 'as admin') there's no UAC prompt, and it won't send keystrokes. If I right click and 'run as admin', I get a UAC prompt, but keystrokes are sent just fine. When I 'test run' the monitor from the ACT wizard, there's no prompt and keystrokes work.(?!?)

I have no idea what I did differently the first time to make it work; so I'm really hoping [anyone still reading!] might have a tip or two for things to keep an eye out for.

Thanks for reading, and in advance for any help you can offer,

Rob.

EDIT: I should probably add, I had no joy with the scheduled task 'trick', either (not least because that way, the tray icon isn't available).

0

There are 0 answers