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(25.6, 9%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWC%3C/text%3E%3C/svg%3E)
We've successfully been using SignTool.exe with Microsoft.Trusted.Signing.Client 1.0.60 for some time.
In upgrading to Microsoft.Trusted.Signing.Client 1.0.76 we now get the following exception being raised: Windows Data Protection API (DPAPI) is not supported on this platform.
This is happening when running the 64 bit version of SignTool.exe on both Windows 10 and Windows 11.
We have found that this is due to the exact copy of System.Security.Cryptography.ProtectedData.dll that is present in the bin\x64 folder of Microsoft.Trusted.Signing.Client
1.0.76 appears to be shipping with the version of the dll from the NuGet package: system.security.cryptography.protecteddata.4.7.0\lib\netstandard2.0
Everything starts working again if we replace with the version from:
system.security.cryptography.protecteddata.4.7.0\runtimes\win\lib\netstandard2.0
While this does allow things to work, patching the contents of a NuGet package obtained as part of a build is error prone and likely to result in errors further down the line.
Is this an error that needs correcting in Microsoft.Trusted.Signing.Client?
If this is a deliberate change, how should we be changing our Azure settings and .json configuration file to enable SignTool to authenticate correctly?
A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
![](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(185.6, 85%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEL%3C/text%3E%3C/svg%3E)
This issue has been reported to the owners of this package. Thanks for your report, as your workaround unblocked me!
![](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(256, 37%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPJ%3C/text%3E%3C/svg%3E)
I encountered this same error today with 1.0.86. I did not try exchanging DLLs. I was using 1.0.60 and it still works, but 1.0.86 does not. Has this been resolved or am I encountering some other issue?
![](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(243.2, 89%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERC%3C/text%3E%3C/svg%3E)
![](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(3.2, 56.00000000000001%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Swapping the DLL did allow us to sign using signtool.exe with v1.086. However, we were then prompted for each signing action to select a user to auth with. By switched to using environment variables to auth the workaround is no longer required. See step 8 in the forum post link below.
https://melatonin.dev/blog/code-signing-on-windows-with-azure-trusted-signing/
I did get it working by installing from the .msi and referencing the DLL directly
![](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(227.2, 35%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
I set up signing late last year and hadn't updated the tooling until recently, when I updated because of an email saying I'd need to by late July. I've since run into this bug, first reported several months ago. Is there a plan/timeline to update the MIcrosoft.Trusted.Signing.Client such that swapping DLLs around or having to interact with browser windows over and over will no longer be a problem? Thanks.
![](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(156.8, 52%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
If you are still experiencing issues, please use this version: https://www.nuget.org/packages/Microsoft.Trusted.Signing.Client.