有时，当我们尝试使用专为此目的设计的软件将数字签名放入PDF文件时，会出现带有以下任一描述的错误消息：^(PDF)

The Windows Cryptographic Service Provider reported an error. Invalid provider type specified, invalid signature, security broken, code 2148073504 or keyset does not exist

在大多数情况下，该问题是由于过时的证书或注册表中的设置损坏而引起的。因此，您可能想要做的第一件事是在域中重置或重新创建用户的配置文件以检查结果。

Windows 加密服务提供程序^{(Windows Cryptographic Service Provider)}报告错误

According to Microsoft, a cryptographic service provider (CSP) contains implementations of cryptographic standards and algorithms. At a minimum, a CSP consists of a dynamic-link library (DLL) that implements the functions in CryptoSPI (a system program interface). Providers implement cryptographic algorithms, generate keys, provide key storage, and authenticate users.

如果您遇到 Cryptographic Service Provider错误，您可能需要尝试以下操作：

1. 重启加密服务
2. 检查证书
3. 重新安装证书
4. SafeNet 身份验证客户端工具
5. 重新创建 Microsoft Cryptography 的本地存储^{(Local Store)}文件夹
6. 卸载 ePass2003。

1]重新启动加密服务

运行services.msc并重新启动Windows 加密服务^{(Windows Cryptographic Service)}。

2]检查证书

打开Internet Explorer > Tools > Internet 选项^(Options)。选择内容选项卡^{(Content Tab)}并单击证书^{(Certificates)}。检查是否存在发出错误的程序或提供程序的证书。如果丢失，您将不得不创建一个新的。如果它已过期，请将其删除并创建一个新的。如果特定证书不起作用，请选择其他证书并删除旧证书。

3]重新安装证书

重新安装整个证书存储区和用户的证书。

4]检查^(Check)SafeNet身份验证客户端^{(SafeNet Authentication Client Tool)}工具

如果您的系统上安装了SafeNet 身份验证客户端工具^{(SafeNet Authentication Client Tool)}应用程序，请通过导航到其安​​装目录或右键单击系统托盘中的SafeNet图标并从菜单中选择工具来打开该应用程序。

单击^(Click)“齿轮”形图标以访问“高级视图”^{(Advanced View)}部分。在Advanced View部分下，展开Tokens并导航到要用于签名的证书。您可以在用户^(User)证书组下找到它们。

接下来，右键单击您的证书并从下拉菜单中选择设置^(Set)为CSP 。对您正在使用的所有证书重复相同的步骤。

关闭SafeNet 身份验证客户端工具^{(SafeNet Authentication Client Tools)}并再次尝试签署文档。

5] 重新创建 Microsoft Cryptography 的本地存储^{(Local Store)}文件夹

导航到C:\ProgramData\Microsoft\Crypto\RSA文件夹。重命名标记为S-1-5-18的文件夹。重新启动系统，看看它是否有帮助。

6]卸载ePass2003

如果您安装了ePass2003软件，问题的原因可能是 ePass2003 电子令牌。建议首先将其卸载并重新安装。为此，请转到该工具的“设置”^(Settings)部分，导航至“应用程序^(Apps)和功能”，然后像任何其他应用程序一样将其卸载。

重新启动计算机并再次安装ePass2003。在重新安装时，请确保在选择CSP选项时选择Microsoft CSP 。事情应该会恢复正常，并且不会再出现Windows加密服务提供商错误。

All the best!

相关阅读^{(Related read)}：Windows 服务将无法启动^{(Windows Services will not start)}。

The Windows Cryptographic Service Provider reported an error

Sometimes, when we attempt to place a digіtal signаture into a PDF file using a software designed specifically for the purpoѕe, an errоr message bearing any one of the following descriptiоns:

The Windows Cryptographic Service Provider reported an error. Invalid provider type specified, invalid signature, security broken, code 2148073504 or keyset does not exist

The issue, in most cases, arises due to outdated certificates or corrupted settings in the registry. So, the first thing you may want to do is reset or recreate the user’s profile in the domain to check the result.

The Windows Cryptographic Service Provider reported an error

According to Microsoft, a cryptographic service provider (CSP) contains implementations of cryptographic standards and algorithms. At a minimum, a CSP consists of a dynamic-link library (DLL) that implements the functions in CryptoSPI (a system program interface). Providers implement cryptographic algorithms, generate keys, provide key storage, and authenticate users.

If you face Cryptographic Service Provider errors, here are a few things you may want to try:

1. Restart Cryptographic Service
2. Check the Certificate
3. Reinstall the Certificate
4. SafeNet Authentication Client Tool
5. Recreate Microsoft Cryptography’s Local Store folder
6. Uninstall ePass2003.

1] Restart Cryptographic Service

Run services.msc and restart the Windows Cryptographic Service.

2] Check the Certificate

Open Internet Explorer > Tools > Internet Options. Select the Content Tab and click on Certificates. Check if there is a certificate for the program or the provider which is giving out errors. If it is missing, you will have to create a new one. If it is expired, remove it and create a new one. If a particular certificate does not work, choose a different certificate, and remove the old certificates.

3] Reinstall the Certificate

Reinstall the entire certificate store and the user’s certificates.

4] Check the SafeNet Authentication Client Tool

If you have the SafeNet Authentication Client Tool application installed on your system, open the app by navigating to its installation directory or by right-clicking the SafeNet icon in the system tray and selecting Tools from the menu.

Click the ‘gear’ shaped icon to access the Advanced View section. Under the Advanced View section, expand Tokens and navigate to the certificate you want to use for signing. You can locate them under User certificates group.

Next, right-click on your certificate and choose Set as CSP from the drop-down menu. Repeat the same step for all certificates that you’re using.

Close SafeNet Authentication Client Tools and try signing the documents again.

5] Recreate Microsoft Cryptography’s Local Store folder

Navigate to the C:\ProgramData\Microsoft\Crypto\RSA folder. Rename the folder labeled S-1-5-18. Restart your system and see if it helps.

6] Uninstall ePass2003

If you have ePass2003 software installed, the cause for the problem could be the ePass2003 e-token. It is advisable to have it uninstalled in the first place and reinstall it. For this, go to the Settings section of the tool, navigate to Apps and features and uninstall it just like any other application.

Restart your computer and install ePass2003 again. At the time of re-installation make sure that you select Microsoft CSP when choosing CSP option. Things should revert to normalcy and Windows cryptographic service provider error should no more appear.

All the best!

Related read: Windows Services will not start.

Related posts

• Background Intelligent Transfer Service不在Windows 11/10工作

• 如何在Windows Time Service上打开debug logging

• Windows Update Medic Service（WaaSMedicSVC.exe）在Windows 10

• 如何在Windows 10启用或禁用IP Helper Service

• Problem uploading至Windows Error Reporting service

• dependency Service or Group未能在Windows 10开始

• Fix Services和Controller应用High CPU usage在Windows 10

• Windows无法启动Diagnostic Policy Service

• Windows Service在Windows 11/10中不会启动

• 如何查找已停止或启动的过程Windows Services

• Audio Service在Windows 11/10上未运行

• Fix Windows Server Update Services ​​Error Code 0x80072EE6

• 如何打开Windows Services Manager; Start，Stop，Disable Services

• 如何在Windows 10上禁用Windows Insider Service

• 我的Windows Services Panel让您轻松管理Windows Services

• 自动Windows Service | Restart Services Find Dependencies

• 如何识别Windows Services延迟Shutdown or Startup

• Windows Installer不Windows 10正常工作

• 如何在Windows 10灰色灰色，启用DNS Client Service

• WMI Provider Host（WmiPrvSE.exe）High CPU Usage在Windows 10