Skip to main content
C
CSI-Juergen
Participant
July 22, 2020
Answered

Signature Failure: Error Code 3221226123 Windows Cryptography Service Provider

  • July 22, 2020
  • 2 replies
  • 2009 views

Hello community,

 

Since Acrobat was updated to 2020.009.20074 , I get get the following Error when signing a document:

Windows Cryptography Service Provider reportet an error: 3221226123

I work with signatures for 10 years and get this failure, now.  I already tried to repair the installation. Also the Certificate and Key is installed and valid. I also installed latest drivers and Windows security hotfixes.

 

System: Windows 10 Pro, Version 1909, 64bit

 

 

Regards, Juergen

This topic has been closed for replies.
Correct answer CSI-Juergen

I found the solution after investigating the security configuration on my Win10.  The Security Event Log reported following error message while trying to use the signing key: 5060 "Microsoft Software Key Storage Provider. Failed to unprotect persistent cryptographic key."

It means, the stored passphrase may be lost or the key is damaged and need to be re-installed.

 

The solution: I removed the related key-pair in Certitifcate Manager > certmgr.msc > Personal > Certificates. Then I impoterted the key-pair (PFX File) again.

Now, the signing in Acrobat works again.

 

2 replies

C
CSI-JuergenAuthorCorrect answer
Participant
July 25, 2020

I found the solution after investigating the security configuration on my Win10.  The Security Event Log reported following error message while trying to use the signing key: 5060 "Microsoft Software Key Storage Provider. Failed to unprotect persistent cryptographic key."

It means, the stored passphrase may be lost or the key is damaged and need to be re-installed.

 

The solution: I removed the related key-pair in Certitifcate Manager > certmgr.msc > Personal > Certificates. Then I impoterted the key-pair (PFX File) again.

Now, the signing in Acrobat works again.

 

Amal.
Amal.
Legend
July 30, 2020

Hi there

 

We are sorry for the delay in response.

 

We are glad to hear that the issue got fixed and thankyou for sharing the solution as it will help the other users on this community expoeriecing the similar issue.

 

Regards

Amal

Amal.
Amal.
Legend
July 23, 2020

Hi there

 

We are sorry ffor the trouble. As desxcribed you are getting the error 'Windows Cryptography Service Provider reported an error'

 

SHA256 has been the default hashing algorithm in Acrobat since version 9.1. However, if the signature device (for example, smart card or USB token) or its driver doesn’t support SHA256 or higher hashing, to prevent failure, Acrobat or Reader used to silently fall back to use SHA1 hashing while creating the signature.

Due to high customer demand for regulatory and industry compliance, Adobe has removed the silent fallback to SHA1 hashing. That’s why you see the error message, and subsequently signing fails if the requested hashing algorithm is not supported.

 

Please check with your signature device or driver manufacturer for an updated driver that may resolve this error. For more information please take a look at the help page https://helpx.adobe.com/acrobat/kb/key-does-not-exist-error-code-2148073485.html

 

Regards

Amal

C
CSI-JuergenAuthor
Participant
July 23, 2020

I work with signatures for 10 years and it worked fine on my current notebook Lenovo X1 Yoga 4th Gen before Acrobat was updated last week.  The problem happens just in latest Acrobat version 2020 since I updated it last week.

 

So, My Lenovo X1 Yoga supports SHA-256. The problem is Acrobat Version 2020.  It looks like the error code 3221226123 is new to Acrobat. Have you any ideas what has changed in Acrobot 2020 to previous version 2019? Have you a solution for it?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices