Advanced Installer can digitally sign all of the following files that it creates: EXE, MSI, MSP (patches) and CAB files. The EXE, MSI and MSP files are always signed while the CAB files are signed only if they are not embedded in the MSI.
Checking this checkbox will enable the actual signing of the package.
This button can be used to clear all fields.
Software Publisher Certificate
Use from Personal certificate store
Choose one of the currently installed certificates.
<Most suited certificate> - When this value is selected, "SignTool.exe" will sign the files with the best certificate found in the current user's Personal certificates store.
To view or manage certificates inside the system store, you can use certmgr.msc tool.
Use file from disk
When this option is selected the certificate used to sign the files is loaded from a local disk file. Every time you select this option, you will be prompted to select the path to the certificate from the hard-drive.
Certificate - This field contains the path on disk to the certificate. You can use thebutton in this field to select one from your hard-drive.
PFX certificates are recommended, you can use either pvkimprt or pvk2pfx to create a PFX certificate from the SPC and PVK files. If the PFX file is protected with a password, the “Selected certificate requires password. Select how to transmit it to signing tool:” section will be visible.
- pvkimprt can be downloaded from this page. Following the link from the page will download an .EXE archive containing the pvkimprt installation setup. To install, first extract the setup and then run the installation from the extract location.
- pvk2pfx is available as part of the Platform SDK.
Private Key - In this field you can set the “Private Key”. You can use thebutton to select one from your hard-drive. PFX certificates do not have a separate private key file, thus this field is hidden by default.
Enter password each time project is built - You will be prompted to enter the password when the MSI is built.
Advanced Installer caches the password for PFX files and hence you will be prompted for the password only once.
Store encrypted password in project file - The encrypted password will be stored in the project and used at build time to sign the installation files. This option is useful for unattended builds.
Password - The password for the PFX certificate.
Confirm password - Confirm the PFX certificate password.
This field contains the signed content's description. It will be showed by the Windows UAC after you click the "Install" button.
This field contains a URL for a complete description of the signed content. The URL will be used when the package is launched from an untrusted location (for example from the network) in the "Open File - Security Warning" dialog, where the "Name" field will become a link to the URL you specified.
Timestamp service URL
A digital certificate has a validity period. After that period expires the signed code is not considered certified anymore. To prevent that a timestamp can be placed at the signing time which will show that the certificate was valid when the signing was done.
The “Timestamp service URL” specifies the
URL of the timestamp server. Some examples of such servers are:
Signature properties are required to display the exact MSI name on the UAC prompt.
Sign only for modern operating systems, Windows 7 or newer (recommended)
If you enable this option your package will be signed only with SHA256 hashing algorithm.
By default Advanced Installer uses SHA256 as hashing algorithm, as recommended by Microsoft. However, it is very important to know that packages signed with SHA256 will not have their digital signature recognized on XP/2003 and Vista/2008 machines.
This option can be used only with SHA256 certificates. For SHA1 certificates this option will be ignored and only a SHA1 signature will be added for each file.
Sign for compatibility with all operating systems, including Windows XP/Vista (deprecated)
This option enables Advanced Installer to perform dual signing or to sign only with SHA1 hashing algorithm.
The dual signing process follows Microsoft documentation, ensuring your digital signature is correctly seen on all operating systems, including XP/2003 and Vista/2008.
Dual signing will succeed only if you have a SHA-2 certificate. SHA-1 certificates can only be used in certain scenarios, as explained in this article.
Enable installing of patches for this product without elevation
By enabling this option you don't need elevated privileges when applying the patch if both patch and target MSI are signed using the same certificate.
An administrator can disable least-privilege patching on the computer by setting the DisableLUAPatching policy to 1. You can set the MSIDISABLELUAPATCHING property to 1 during the initial installation of an application to prevent least-privilege patching for that application only.
This option is not available for Patch Projects.
Files Configured for Signing
A dynamically populated list of the files which will be signed when "Enable signing" option is checked. There are two listed categories, project files and output files.
Optionally, you can add, remove or locate project files from the context menu. The add/remove context operations simply enable/disable the project file's "Digitally sign the file" option.
The default tool, available with the Windows SDK v8.0 or higher, used by Advanced Installer. This tool can be used only with certificates exported as PFX files. You can use either pvkimprt or pvk2pfx to create a PFX certificate from the SPC and PVK files.
This is a tool from Advanced Installer, the automatic fallback if you do not have the Windows SDK installed.
From External Tools Options page you can choose which tool to be used, i.e SignTool.exe or our internal DigiSign tool.
On Windows 7 dual signing is supported only by SignTool.exe and it requires you have these updates installed, along with the Windows SDK v8.0 or newer. The alternative DigiSign tool from Advanced Installer can perform dual signing only on Windows 8 or newer.