Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • The general instructions you link seem to say that this is actually doing the opposite: elevating without the UAC prompt. Commented Jan 13, 2011 at 12:10
  • @Peter, not quite (I had the links the wrong way round so you may have been on the wrong page, sorry about that, make sure you are looking here ), Figure E is setting the program to run "asInvoker" (ie, as the user calling the program, without elevation).
    – DMA57361
    Commented Jan 13, 2011 at 12:13
  • That's the one. It says "The RunAsInvoker option will allow the application to run with the same privileges and user rights as those of the parent process, which in this case is the Compatibility Administrator that you launched using the Run As Administrator command. Your application will run with full Administrator privileges." Commented Jan 13, 2011 at 12:16
  • @Peter - nuts, I think you're right. I'm sure I've done this before to un-elevate an executable... Unfortunatly I'm at work right now so can't verify. I wonder if one of the options or parameters contains something that needs tweaking (ie, to change the "invoker" to be the user, not the toolkit), I'll have to check this evening when I'm home...
    – DMA57361
    Commented Jan 13, 2011 at 12:23
  • @Peter - see this Microsoft article and the quote This fix specifies that the application does not require elevation. This is getting a little bit ambiguous between the sources, but I think it may well work. It also suggests trying SpecificNonInstaller to prevent Windows guessing that it is an installer and elevating because of that.
    – DMA57361
    Commented Jan 13, 2011 at 12:34