-1

I want to run my c# console application as an admin without UAC on non-admin account. Problem is, when i disable UAC with eiter Task scheluder or Microsoft Compatibility kit, my app runs with non-admin rights. Only time i Can rup an app with admin privilegs is when i right click - run as admin and i enter password. But i dont want to do that. I want to run app on non-admin account with admin privileges.I dont know where to problem is. When i try to run application with "runas" and i use Admin account with correct password, it pops me : access is denied. I dont know if problem is in my application or somewhere else.

Thanks

Christián Szeman
  • 11

2 Answers2

0

Add application manifest file and enter following code

<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
Zeeshan
  • 125
0

The process of using Task Scheduler to “run with highest privileges” is not how you bypass UAC.

If you have an application that needs to run and interact with the logged on user, then that app will run with the user’s permissions. You can use task scheduler to run a task as a different user but then it won’t interact with the logged on user. Running a task as the logged in user limits the application to the highest permission the user has.

The other procedure of using the application compatibility toolkit also does not solve the issue. What this does is take a misbehaving application that is “requiring” an admin password but doesn’t actually “need” admin permissions and making it so it will run without any UAC / admin prompts.

If your application “requires” admin permissions then the user HAS to run the application as another user with admin permissions using the username and password of that user or it will fail.

Disabling UAC on the computer will not only severely reduce the security of the system it will make it so when you run any app with a limited user account you won’t even be prompted to elevate with the credentials of an admin user and your application, if it requires admin access, will fail.

The problem here is your app requires admin permissions. That is what needs to be fixed. What is it doing that requires admin permissions? Why? Redesign it so it doesn’t. Otherwise, there is no “secure” way of allowing a non-admin user to run an application with admin permissions. It is no longer acceptable practice, and has not been for years now, to design applications that require that level of permission for standard users to use.

If you absolutely have to have a standard user run an application as admin you can use the “runas” command or some third party administrator tools that allow a user to request access and an administrator to remotely respond to allow the application. Again, the problem is the app, not the OS. Trying to work around this would not be acceptable in most use cases that required users to use limited accounts in the first place.

Appleoddity
  • 11,970