WOW, you said a lot there, quackhandle, because we were guilty of doing that as well. As developers we wrote our code so that it required elevated privileges. But I guess at least in this it wasn't entirely our fault. Back in the late 1990's it was common practice to store some configuration information in the registry. In some cases, storing all configuration information in the registry. We didn't know how to make it possible for regular users to be able to write into the registry, without making them all administrators on their own machines. So that's what we did, I am embarrassed to say. It may be possible to do that without making someone an administrator on their machine, but I don't know how. And honestly at this point I don't want to know. Configuration information shouldn't be in the registry. But the use of XML files to store that kind of information didn't come about until years later. Anyway, the old VB6 apps that I helped write at that agency, are still being used today, so they're still having to give admin rights on the machine to any user needing to use those apps. While I was there I lobbied to get those apps re-written so they wouldn't depend upon the registry, move them to some .NET app, but that never happened. And now it doesn't really matter, as the agency where I used to work, is going out of business at the end of 2016.