Shimming to get rid of UAC prompt on Windows 7 64-bit
-
Friday, November 09, 2012 4:48 PM
I'm currently working on shimming an application to work on Windows 7 x64.
Background: When installed the application has 2 exe files, an exe file to launch the main application and an exe file to configure the application for first time use. The first time the application is launched after installation, no matter which of the 2 exe files are clicked, the configuration exe is launched to allow the user to configure the app for first time use.
The Issue: I have applied the "ForceAdminAccess" and "RunAsInvoker" shims to both of the exe files. When the configuration exe is launched it works perfectly, no UAC prompt. However, when the main application exe is launched a UAC prompt is displayed asking if I would like to allow the Configuration exe to make changes to this computer.
I guess the most confusing part is that the prompt is asking for me to give permission to the Configuration exe file to make changes to the computer, which when launched directly from its shortcut needs no permission (does not display a UAC prompt).
Any suggestions as to what the problem could be would be much appreciated.
Thanks,
Brad
All Replies
-
Monday, November 12, 2012 7:32 AMModerator
Hi,
This situation occurs should be by design. You may change the UAC level to fix this issue.Kim Zhou
TechNet Community Support
- Marked As Answer by Kim ZhouModerator Wednesday, November 14, 2012 3:45 AM
- Unmarked As Answer by Kim ZhouModerator Wednesday, November 14, 2012 3:45 AM
-
Wednesday, November 14, 2012 3:45 AMModerator
-
Wednesday, November 14, 2012 5:44 PM
Unfortunately, this is not an option for the client. They do not want to change the UAC settings on the entire Operating System. They would like to control it on a per application basis. I have solved this problem with shimming in the past but for some reason it is not working on this particular application. Are there no other options?
Thanks,
Brad
-
Monday, November 19, 2012 3:11 AMModerator
Hi,
You may try to set Privilege Level as “Run this program as an administrator” under its Compatibility settings tab.Kim Zhou
TechNet Community Support
- Marked As Answer by Kim ZhouModerator Monday, November 26, 2012 3:02 AM
-
Friday, November 23, 2012 6:04 AMModerator

