Barry Patterson

So change how you're doing it - instead of writing to the Windows\CurrentVersion\Run registry, create a shortcut under the user's startup (<username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup) or just tell the admin/installer that they have to put a shortcut in programdata\microsoft\windows\start menu\programs\startup or something like that. We have guys on the mill floor trying to run this software to control equipment and it is not a good idea for them to have admin rights on the PC for a lot of reasons. Another option would be to have a script that can be run as admin to give the specific registry permissions if you have to... but there should be "normal user" alternatives. (CurrentUser_classes versus Root_Classes for example - ran into that with a different software package) UAC is here to stay. Our IT department uses it constantly - they do not log in as their admin accounts, they use "run as admin" all the time to manage the system, but the end users don't get that option because of the security and legal issues it can cause. (User installs software the company is not licensed for and gets caught in an audit for example)