Click here to Skip to main content
15,883,606 members
Please Sign up or sign in to vote.
3.33/5 (3 votes)
See more:
I'm struggling to get my application to load without having a UAC popup window. My application does require admin access as I'm managing user accounts locally and with the domain on a 2008 server. My application is two parts, a service and a WPF app that controls the service.

I purchased a developer cert from Comodo and am able to sign the application. I also have a .manifest file assigned to the project.

After I build the application I see the shield on it so I know it's working ok. However, when I click on it I get a blue window asking if I want to allow the following program to make changes to this computer.

I believe my issue is around this line:
<requestedexecutionlevel level="requireAdministrator" uiaccess="false" />

If I set the level to asInvoker the UAC window doesn't appear but my app shuts down because of what it needs to operate.

Does anyone know how I can around this issue without disablign UAC?

You can't get rid of the UAC window.

When UAC is activated, any admin account will run WITHOUT admin priv's until they are actually needed. When that determination has been made by Windows, the UAC prompt window appears.

There's nothing you can do about it for your application. it's up to the user's admins to turn off UAC or set it to some other level in policy.
Share this answer
Sergey Alexandrovich Kryukov 11-Jul-12 22:37pm    
How about so called "XP mode"? Or switching UAC off for the whole system? I would strongly discourage it though.
Dave Kreskowiak 11-Jul-12 23:42pm    
Weeeelll, that depends on what his app is doing. XP Mode doesn't provide complete access to the Win7 host, so XP mode may let the app run, but it may also still be crippled by the wall between 7 and XP Mode.

You can add a manifest to the application[^] that identifies the privileges for that program.
Save the file as ApplicationName.exe.manifest.
Share this answer
Sergey Alexandrovich Kryukov 11-Jul-12 22:37pm    
Really? I though that the manifest will simply request some privileges by default, which could cause, in this case, the request through the UAC dialog be default, without specifying the option through the shell, *.lnk or any other way (and the default running without elevated privileges will simply throw exception during run-time at the moment of access violation). If I'm wrong, please explain it to me, perhaps I don't know something. There is a way to switch off the UAC totally or use so called "XP mode", which I would strongly discourage. I think Windows 7 is better than XP, and it provides quote reasonable balance between safety and the ease of use.
Sergey Alexandrovich Kryukov 11-Jul-12 23:17pm    
Abhinav, I tried this thing with manifest and found that it works as I thought, please see above.
I think this makes your answer invalid. Tell me if I'm missing something.
Please see my answer which I put based on my simple experiments.
Abhinav S 11-Jul-12 23:25pm    
If you are running the application with elevated privileges, the user will not see the UAC window.

It is not advisable to turn off the UAC.
Is that what the OP is looking for? That is not recommended.
Dave Kreskowiak 11-Jul-12 23:43pm    
He's trying to suppress the UAC dialog without turning off UAC. Depending on how tight UAC is configured, it can't be done.
I do have a successful manifest being applied. If I change the line in the manifest from requireAdministrator to asInvoker the window goes away. But my app will not run because it requires administrator to do so. BTW Dave, I'm attempting to do more reading on what you have mentioned. Thanks.
Share this answer
I found some references to running asInvoker then elevating the privileges from within the application with Does anyone have any experience with that in Win7/2008?
Share this answer
Dave Kreskowiak 11-Jul-12 23:44pm    
Doesn't work. You still get the UAC window when admin priv's are required.
Please see my comments to the answer by Abhinav. I tried to create a manifest and found that it works as I thought.

If you need elevated execution level "requireAdministrator", it will simply request your confirmation via the UAC dialog immediately and by default. If you do not request the elevated privileges but try to perform any operation which actually requires such privileges and do not execute the application with elevated privileges, you will simply get an exception at the moment of the illegal access.

It looks perfectly logical. If you could be able to do some miracle trick to work around UAC confirmation at the level of the application itself, based on the content of application's executable modules, it would totally defeat the purpose of UAC.

However, instructions to "disable UAC for certain applications" circulate. Please see:[^].

I never tried it, but just because I consider UAC as of Windows 7 quite well balanced between ease of use and security.

The radical way to disable UAC is to disable it totally. You can find the related recipes here:[^].

I would strongly discourage doing so. Anyway, you decide.

Share this answer

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900