What is Error code 0x1

[Kim Hawker]

Does anyone know what this error is telling me? 

[Eivind Bakkestuen]

Run the signtool command (manually) from the command line, and you may get a better error description there

On Tue, Feb 8, 2022 at 7:20 AM Kim Hawker <hawke...@gmail.com> wrote:

Does anyone know what this error is telling me? 

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/innosetup/030da273-4b60-4ac6-aa41-cf6d1b8db7ean%40googlegroups.com.

[Kim Hawker]

On Monday, February 7, 2022 at 7:17:15 PM UTC-6 eivind.b...@gmail.com wrote:

Run the signtool command (manually) from the command line, and you may get a better error description there

Thanks again eivind.b. for persuading me to look in a different direction. Now I saw that in my Innosetup I had the command signtool.exe sign /T etc.. but in my file.bat files I had it as signtool.exe sign /V so I changed it within Innosetup and now she’s working without any errors. You’ve been a big help again eivind.b. Thank you.

[Kim Hawker]

My bad. It works and then it quits working without me changing anything. What is going on? Is InnoSetup that unstable? I ran it using different versions of InnoSetup. 

[Gavin Lambert]

On 8/02/2022 17:23, Kim Hawker wrote:
> My bad. It works and then it quits working without me changing
> anything. What is going on? Is InnoSetup that unstable? I ran it using
> different versions of InnoSetup.

If that's happening, it's not Inno that's unstable, it's your signing
tool. Look in the compiler log output; it may have printed a more
useful error message.

In particular note that when compiling a script there may be more than
one call to your signing tool in quick succession (for the uninstaller,
any [Files] you've specified to be signed, and the final installer).

Signing typically requires a call out to the Internet (for a
timestamping service), and this may be speed-limited or otherwise fail
for various reasons, depending on which service you use.

Consider requesting help from your certificate provider, or using a
parameter or wrapper script for the signing tool that will retry (with
delay and limit) in case of a temporary failure. Or just retry manually.

[Laurent Combémorel]

It is a common error with signing : signing operation is signing a temporary file created in the [Setup]: OutputDir directory. If a Windows Explorer is opened on this directory, it will open the temporary file to fetch the icon or preview to display in the actualized list of files. So the signing tool cannot get a lock on the file which is already used by the Windows Explorer, and it fails to sign.

Maybe it should be worth to warn against opening a Windows Explorer (or any similar tool) during signature in the doc ?

[Kim Hawker]

On Tue, Feb 8, 2022 at 3:48 AM Laurent Combémorel <lcm...@gmail.com> wrote:

It is a common error with signing : signing operation is signing a temporary file created in the [Setup]: OutputDir directory. If a Windows Explorer is opened on this directory, it will open the temporary file to fetch the icon or preview to display in the actualized list of files. So the signing tool cannot get a lock on the file which is already used by the Windows Explorer, and it fails to sign.

Maybe it should be worth to warn against opening a Windows Explorer (or any similar tool) during signature in the doc ?

 

Thanks People,

This error can come up for various reasons, but any way I figured it all out and I now I have it all working. Using InnoSetup I now get no errors and a signed file.exe. It’s all good. Thanks to all of you for your efforts.

[vmars vernon]

" This error can come up for various reasons,  "

Pls , what was the reason it came uo for you ?

Thanks

[Kim Hawker]

On Saturday, February 12, 2022 at 9:58:08 AM UTC-6 vmar...@gmail.com wrote:

" This error can come up for various reasons,  "

Pls , what was the reason it came uo for you ?

Thanks

vmar, I think it was something like in my signtool setup I had put something different then signtool.exe sign /v but now when I put /t or /anything I get a different error so I really can't be sure what it was. but it's all working now.

[vmars vernon]

Thanks