Is it possible to use the Trusted Signing service on Windows 10 (22H2)?

J P 5 Reputation points
2024-10-02T11:46:46.67+00:00

Hi,

Is it possible to use the Trusted Signing service on Windows 10 (22H2)? I followed this:

https://learn.microsoft.com/en-us/azure/trusted-signing/how-to-signing-integrations

then also this:

https://github.com/koaladsp/KoalaDocs/blob/master/azure-code-signing-for-plugin-developers.md

I installed Windows SDK (10.0.26100, to use the latest signtool.exe), Trusted Signing dlib package and both .NET 8.0 Runtime and .NET 6.0 Runtime (as the above how-to-signing-integrations says the 8.0 is required, but according to the readme.md from dlib the 6.0 is required).

Anyway, when running signtool.exe I receive a cryptic message "the parameter is incorrect", 0x80070057.

On https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/ there is some user's comment that the new signtool.exe doesn't work on "older" Windows (which generates the above error). Is this correct?

Azure Trusted Signing
Azure Trusted Signing
Trusted Signing is a Microsoft fully managed, end-to-end signing solution that simplifies the certificate signing process and helps partner developers more easily build and distribute applications.
123 questions
0 comments No comments
{count} vote

2 answers

Sort by: Most helpful
  1. Givary-MSFT 34,111 Reputation points Microsoft Employee
    2024-10-07T04:34:50.99+00:00

    @J P Apologies for the delayed response. Based on the information you provided, it seems that you have followed the necessary steps to use the Trusted Signing service on Windows 10 (22H2). However, the error message you received when running signtool.exe indicates that there may be an issue with the parameters you are using.

    Regarding the comment you mentioned from https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/, it is possible that the new signtool.exe may not work on older versions of Windows. However, Windows 10 (22H2) is a relatively recent version, so it should be compatible with the latest signtool.exe.

    To troubleshoot the issue further, I would recommend checking the parameters you are using with signtool.exe to ensure they are correct. You may also want to try running signtool.exe with different parameters or on a different file to see if the issue persists.

    If the issue still persists, you can try reaching out to our support team, if in case you don't have support contract, feel free to share the Azure Subscription id over the private message so that we can help in creating a one-time support option for this issue.


  2. Meha-MSFT 410 Reputation points Microsoft Employee
    2024-11-16T00:14:53.9133333+00:00

    Here's the list of supported versions and any version that is still supported by MSFT. Please ensure the machine has the latest Windows Updates.

    https://support.microsoft.com/en-us/topic/kb5022661-windows-support-for-the-trusted-signing-formerly-azure-code-signing-program-4b505a31-fa1e-4ea6-85dd-6630229e8ef4

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.