本文介绍了Inno Setup - 签名失败,“签名工具失败,退出代码为 0x1";的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有 Inno Setup 脚本,我需要在其中使用 SignTool=signtool,该脚本已正确配置并在过去工作.

但是当我尝试编译时失败,出现以下错误:

签名工具失败,退出代码为 0x1.

解决方案

您没有向我们提供任何可用于调试您的问题的信息.

因此,我发布了使用签名工具"调试问题的通用说明.

  1. 尝试

  2. 或者临时在符号工具命令前加上 cmd.exe/k 以保留其输出,即使在 Inno Setup GUI Compiler 中编译时也是如此.例如:

     cmd.exe/k C:path	osigntool.exe sign/f C:mykey.pfx $f

    请注意,如果您使用带有空格的 signtool.exe 路径,由于 cmd 的工作方式,您不仅必须将路径本身包装为双引号,还有整个命令:

     cmd.exe/k ""C:signtoolsigntool.exe 的路径";签名/f C:mykey.pfx $f"


另请参阅signtool 失败,Inno Setup 失败,退出代码为 0x1.

I have Inno Setup script, where I need to use the SignTool=signtool, which is configured properly and worked in past.

But it's failing when I try to compile with the following error:

解决方案

You didn't provide us any information that we can use to debug your problem.

So I'm posting generic instructions to debug issues with a "sign tool".

  1. Try command-line compiler (ISCC.exe). It will preserve a full signtool.exe error message in the output:

  2. Or temporarily prefix the sign tool command with cmd.exe /k to preserve its output even when compiling in Inno Setup GUI Compiler. E.g.:

     cmd.exe /k C:path	osigntool.exe sign /f C:mykey.pfx $f
    

    Note that if you use a path to signtool.exe with spaces, due to the way cmd works, you have to wrap not only the path itself to double quotes, but also the whole command:

     cmd.exe /k ""C:path to signtoolsigntool.exe" sign /f C:mykey.pfx $f"
    


See also signtool fail with Inno Setup with exit code 0x1.

这篇关于Inno Setup - 签名失败,“签名工具失败,退出代码为 0x1";的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

07-29 15:57
查看更多