This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(83.2, 67%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
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?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
@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.