The problem was due to the metadata.json path being incorrect.
The error message from Signtool was frustrating and misdirecting.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Recently we've rebuilt a Azure VM we use to build installers with Inno Setup with signing via Trusted Signing and Signtool. All our installer generation processes worked a few days ago. We've signed with Trusted Signing since August.
Now we are getting an error a file doesn't exist even though it clearly exists. We are thinking this is a type of access or permissions issue?
What we've tried:
Here is the command we are using:
C:\Program Files (x86)\Windows Kits\10\bin\10.0.26100.0\x64>signtool sign /debug /fd SHA256 /tr "http://timestamp.acs.microsoft.com" /td SHA256 /dlib "C:\Installs\Agent\Extras\tsc-dll\Azure.CodeSigning.Dlib.dll" /dmdf "C:\Installs\Agent\Extras\metadata.json" "C:\Installs\Working\DataAgent.exe
Error:
SignTool Error: File not found: C:\Installs\Working\DataAgent.exe
I can verify the path with signtool just fine:
C:\Installs\Agent\Extras\signtool>signtool verify C:\temp\DataAgent.exe
File: C:\temp\DataAgent.exe
Index Algorithm Timestamp
========================================
SignTool Error: No signature found.
Here is a screenshot of the error and the paths of the files:
The problem was due to the metadata.json path being incorrect.
The error message from Signtool was frustrating and misdirecting.