1. In fact it doesn't disable UAC in any way! 2. It forces the application that might come up with a UAC prompt to "run as invoker"! 3. As a result: The application will not receive access to HKLM and other areas, so the programs virtualization is disabled. The article and the blog are extremely confusing. And to be honest: I blogged about it too until I found that it doesn't hold really what it seams to promise. I removed my article from my blog, because it isn't really useful.
-- Martin Richter (MVP for C++) WWJD http://blog.m-ri.de "A well-written program is its own heaven; a poorly written program is its own hell!" The Tao of Programming