I use a DigiCert certificate on a thumbdrive to code sign my setups.
It has been working fine for several years, through a number of renewals.
Suddenly, when building my setup project, Advanced Installer (22.8) no longer asks me for my password while signing the files (it normally asks several times, actually), and while the setup file is built correctly, when running the setup program it says "unknown publisher" instead of our company's name as before.
I haven't made any changes to the signing settings and everthing looks correct. Any thoughts as to what could be happening?
Suggested Articles
-
almostEric
- Posts: 2
- Joined: Mon Jun 16, 2025 10:51 pm
Re: CodeSigning not working properly
Hello Eric,
Just to make sure I understand your scenario correctly, by thumbprint, do you mean a USB?
If so, we have tested this on our end, both with project conversion and on a new project, and the signing works just fine. Additionally, we tested with both the .cer on the disk and the certificate being installed in the store.
Normally, the "Unknown publisher" appears if your setup is not signed. Could you please check this and let me know if it is signed?
Note: the signing process should appear in Advanced Installer as well, when you build your project, e.g.:
Does it appear that way for you as well?
Another way of checking is after the build, in the file's properties --> "Digital Signature" tab.
What I'm thinking here is trying to also use a custom signtool (the one that comes with Windows SDK) and see whether that helps. This would be the only thing we have changed in 22.8 regarding our signing support - we only changed the version of signtool, we now deliver the latest version from Windows SDK.
Best regards,
Catalin
Just to make sure I understand your scenario correctly, by thumbprint, do you mean a USB?
If so, we have tested this on our end, both with project conversion and on a new project, and the signing works just fine. Additionally, we tested with both the .cer on the disk and the certificate being installed in the store.
Normally, the "Unknown publisher" appears if your setup is not signed. Could you please check this and let me know if it is signed?
Note: the signing process should appear in Advanced Installer as well, when you build your project, e.g.:
- Screenshot_46.png (7.07 KiB) Viewed 554 times
Does it appear that way for you as well?
Another way of checking is after the build, in the file's properties --> "Digital Signature" tab.
- Screenshot_47.png (15.54 KiB) Viewed 554 times
What I'm thinking here is trying to also use a custom signtool (the one that comes with Windows SDK) and see whether that helps. This would be the only thing we have changed in 22.8 regarding our signing support - we only changed the version of signtool, we now deliver the latest version from Windows SDK.
Best regards,
Catalin