UAC, RunAs silent fail?

When running as a standard user with UAC disabled, choosing “Run as administrator” from the context menu is broken!

Silent Bob

Not showing the consent UI is understandable since UAC is not “hooked” into the system, but just starting the process non-elevated without a warning dialog is just wrong. When the runas verb is used with ShellExecute and UAC is not enabled it should just show the old Run As dialog used in Windows 2000/XP/2003.


Tags: , , , , ,

2 Responses to “UAC, RunAs silent fail?”

  1. someone Says:

    Use Sysinternals’ shellrunas as a workaround.

    • WindowsSucks Says:

      Windows already comes with runas.exe that does the same job when UAC is off, but that does not help programs/programmers that call ShellExecute and expect the user to be able to specify credentials or elevate. The issue is that this problem is not documented AFAIK so apps have to use ugly version and registry checks and implement their own runas dialog!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s