ixm7

I noticed that your image shows Signtool location as: **C:\users\...** While mine shows: **C:\Program Files\...** Perhaps you'd be able to replicate the bug by testing using a machine where the...

Another issue I noticed is that **the dialog doesn't remember last used options** such as: Signing Account Name, Certificate Profile, and Files to Sign.

The tool already remembers the endpoint options. In the same way, users would expect remembering process options. This would also facilitate calling the tool via a **command line** (defaulting to...

The error: **Dlib file not found at: .\Tools\Azure.CodeSigning.Dlib.dll** is an exception triggered in your code, not on Azure's side:

I installed the new version. It still generates the following error: File signing failed after 3 attempts. Last error: Dlib file not found at: .\Tools\Azure.CodeSigning.Dlib.dll Consider trying to locate the...

The relative path is relative to the **current working directory**. It may not be the application directory. So consider changing the code to build the path using something like: `AppDomain.CurrentDomain.BaseDirectory...

Is there a new download link?

Good news: the GUI now remembers the processing options. And the dll path error is gone. Bad news: a new error is logged: Attempt 1: Using timestamp server 'East US'...

My Resource Group location is East US Azure shows this as the Account URI: https://eus.codesigning.azure.net/ I didn't create a metadata.json file. Is that a required step? I assumed your GUI...

I don't use a 'Service Principal' or a 'certificate based authentication'. I can invite you to a Zoom session if you'd like to look at the problem.