On your verify command add in the /pa option to tell it to use the Default Authentication Verification Policy instead of the Windows Driver Verification Policy, meaning it will look at your certificate stores instead of the limited set of CAs Microsoft trusts with drivers. Look here for more options: http://msdn.microsoft.com/en-us/library/8s9b9yaz(v=vs.90).aspx
I figured out the problem, the path to the certificate must be relative to the installer output path, not the current working folder. In this case, it would be “..\cert.pfx”.
I just ran into the same issue. Running the build from a Visual Studio 2012 Command Prompt worked, but it was failing in the IDE. Looking for a detailed or diagnostic log led me to What is the default location for MSBuild logs?, which told me that Visual Studio can’t give the diagnostic information I … Read more
Honestly, I would just try again. But you can use any of the following: http://timestamp.globalsign.com/scripts/timstamp.dll, http://timestamp.comodoca.com/authenticode, or http://www.startssl.com/timestamp. http://timestamp.sectigo.com
Use the /d command line argument with the required program name when executing signtool to sign the msi. It appears that the windows installer creates a temporary copy of the msi file and assigns it a generated name before running it. If you don’t use /d with signtool, you get to see the temporary filename … Read more
You need to install the Windows 10 SDK. Visual Studio 2015 Update 1 contains it already, but it is not installed by default. You should go to Control Panel -> Programs and Features, find Microsoft Visual Studio 2015 and select “Change”. Visual Studio 2015 setup will start. Select “Modify”. In Visual Studio components list find … Read more
I had the same issue but installing the Windows 8.1 SDK as per Catquatwa’s answer did not work for me (signtool.exe was still missing from C:\Program Files (x86)\Microsoft SDKs\Windows\vX\Bin). I stumbled across this solution: http://www.benedykt.net/2015/08/12/missing-signtool-exe-w-visual-studio-2015/ Basically, for VS 2015, this would be: Open Programs and Features Select “Microsoft Visual Studio 2015” and click “Change” Press … Read more
When getting this error through Visual Studio it was because there was a signing certificate setup to match the computer it was originally developed on. You can check this by going to the project properties > signing tab and checking the certificate details. You can uncheck “Sign the ClickOnce manifests” to disable signing. If you … Read more