Code signing error 0x80190194

HTML Executable
#1

At compilation time, I get the following code-signing error. (The asterisks represent data I have deleted.)

GSignCode 2.1 – simple code signing utility
Copyright G.D.G. Software 2011-2016. All rights reserved.
Certificate Subject Name:*********************
Issuer: CN=Sectigo RSA Code Signing CA, O=Sectigo Limited, L=Salford, S=Greater Manchester, C=GB
Serial Number: ************************
Signing C:\Users\jmilb\Documents\My Poetry\Exe\aeiour5.exe
SIGNING ERROR:
Signing Error - Code 0x80190194
Warning: code signing failed, an error occurred.

Compilation Successful

#2

Go to the Environment Options, and enter http://timestamp.sectigo.com
for both timestamp URLs.

#3

Thanks. That worked.

#4

I am getting the same error. But if I enter the URL http://timestamp.sectigo.com for both options I still get the same error. I am using the Comodo certificate, it is valid until 21st May 2021.

#5

I have the same problem. I cannot sign my pacquet builder package on a windows 10 machine with comodo certificate. I am using a pfx file which does work when using it in an xlspad compilation of an excel file on the same computer (using sha1, sha256 does not work). In a next step putting this compiled file into an install package the error messages as shown above comes up both for sha1 as for sha256. Changing the URL did not help. Any other ideas ?

#6

For Paquet Builder, please contact us by email or ticket to get a fix.

#7

For the first URL (SHA1), use
http://timestamp.digicert.com

#8

I have tried that but no success unfortunately

#9

It’s for HTMLEXE. For PB, see the answer to your ticket that you opened.

#10

Hello, I again have the same problem. The Code Signing gives the following errors:
SHA1
Signing Error - Code 0x800B010A
Warning: code signing failed, an error occurred.
SHA256
SIGNING ERROR:
Signing Error - Code 0x800B010A
Warning: code signing failed, an error occurred.
I tried changing the environment URLs to the ones in this thread but the problem persists. How can I resolve this?

#11

The next HTML Executable 2021 will come soon, and it provides a fix for that error. Until that, use SignTool as a workaround.

#12

Thanks, is there a guide that shows how? I searched in Google and the Microsoft documentation is not very clear.

#13

Here: Using SignTool to Sign a File - Win32 apps | Microsoft Docs