True Crypt 6.3 UAC issue (Application Packaging)

Hi All,

Currently we are packaging TrueCrypt 6.1 application, but unfortunately we are facing some issues in that.

Source is simple legacy application, and after installation when we launch shortcut we do not get UAC prompt; but after capturing through installshield or wise package studio, when we launch shortcut, we get UAC prompt. We tried to check with procmon,procexplorer and multilpe things,but we are not able to suppress that UAC, or not able to find out why UAC is coming in captured MSI, and it is not coming in original source.

If anyone has faced this issue before then please guide.

1 Comment   [ + ] Show comment
  • Where are you installing the TrueCrypt exe? - rileyz 8 years ago

Answers (2)

Posted by: jagadeish 8 years ago
Red Belt

There will be a kernal driver service created by this applicaiton in msinfo32->Software Environment->System Drivers

Ensure that the service state is "Running"

if it is in Running state already then restart the machine and launch the shortcut

Posted by: Guttormr1 8 years ago
Senior Yellow Belt

without looking i obviously have no clue.  But if TrueCrypt is an msi install already and you tried to capture it...that can cause problems.  (if it is a msi)  double check your shortcuts and make sure they are running the proper .exe files and that they are not awkwardly pointing to a c:\windows\installer location.  Also...double check the permissions on the install directory from the vendor install.  Maybe the vendor has opened permissions on certain file or registry keys.  Most capturing tools don't capture these types of changes.  It could be as simple as opening some permissions.

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ