Application giving UAC prompt AFTER it's repackaged
Hi Guys
I had a vendor EXE with no hidden MSI so I repackaged it using the Repackager and after I cleaned and created the MSI and tested it, it gave the UAC prompt but when I installed the vendor EXE, it didn't give the UAC prompt.
I repackaged it three times using all three methods, Installation Monitoring, Snapshot single step, Multiple step with the same result.
Has anyone ever encountered the same problem and knows what the solution might be?
Thanks in advance for your help/
SOLUTION:
The application installs a service that requires a reboot. After the reboot, the application started working fine.
-
Have you examined a verbose log of the MSI installation to see which action is triggering the UAC prompt? Since the vendor EXE is not an MSI it is not going to install in the same way as an MSI. Once you know which action is responsible then you can take the necessary steps to resolve. However, this is less likely to be the problem than the fact that your repackage has created an MSI. An exe is used for a lot more than just installers so cannot trigger a UAC prompt in all situations, but the MSI file extension is explicitly a trigger for UAC. This should not be an issue for any corporate, service based, deployment system - EdT 10 years ago
Answers (5)
//The application installs a service that requires a reboot. After the reboot, the application started working fine.//
If the soultion is restart then how vendor exe is working fine without a restart..
<Check whether the service status is "Started">
UAC has nothing to do with packaging, it's all about security. Read this for starters:
http://en.wikipedia.org/wiki/User_Account_Control
then follow it with this:
http://windows.microsoft.com/en-us/windows/what-are-user-account-control-settings#1TC=windows-7
Comments:
-
I know what UAC is but how do you explain that the application works fine using the vendor EXE but after it's repackaged and converted into a single MSI, it starts giving the UAC prompt. - tellmehow 10 years ago
I'll guess that the MSI you created was not scrubbed properly and contains one of the UAC triggers noted in the Wiki:
- Running an Application as an Administrator
- Changes to system-wide settings or to files in %SystemRoot% or %ProgramFiles%
- Installing and uninstalling applications
- Installing device drivers
- Installing ActiveX controls
- Changing settings for Windows Firewall
- Changing UAC settings
- Configuring Windows Update
- Adding or removing user accounts
- Changing a user’s account type
- Configuring Parental Controls
- Running Task Scheduler
- Restoring backed-up system files
- Viewing or changing another user’s folders and files
- Running Disk Defragmenter
Comments:
-
Already checked. None of this. - tellmehow 10 years ago
Hi
EXE you have launching required Addmin rights
There might be chances like ,you launching the shortcut in STANDARD User
install application and run shortcut in ADMIN user and see the result there mught be changes like this application might be require for the person having ADMIN rights
Comments:
-
I am installing and running as admin and still get the UAC. - tellmehow 10 years ago
Please check whether the repackaged application works fine for admin user. If it works fine and this issue is only with User ,then in this case we can can apply a shim using Application Compatibility toolkit (ACT) tool.
Create a shim(.sdb file) including Runasinvoker, Runasadmin and Runashighest shims to suppress UAC prompt.
Apply this shim through one custom action to install it.
