Solution
This is a known issue. As a workaround, you can build your Application/Installer, then sign the resulting file(s) using command line functions. You can use CertUtil and SignTool to sign your file(s), according to the instructions in NI Package Builder User Manual - Signing Package Builder Installers.
When building an Installer, to automate this process, you can configure the Installer to call a custom Application after the Installer finishes its execution.
- Create an Application which will complete the necessary command line functions for signing certificates. You can do so by building a VI into an Application or use any other executable (.exe) to accomplish this.
- In the Installer Properties window for your Installer, navigate to Advanced >> Launch Executable After Installation and select the built Application.
For more in-depth instructions on how to automate this process using an Application, refer to How To Include And Run My Executable With My LabVIEW-Built Installer.