我有同样的“私钥过滤后，0 certs被留下”的消息，我花了太多的时间试图弄清楚这条消息的意思。

问题是我在Windows证书存储中错误地安装了证书，因此没有与代码签名证书相关联的私钥。

我应该做的是:

Using either Firefox or Internet Explorer, submit the request to the issuer. This generates a PRIVATE KEY which is stored silently by the browser (a dialog appears for a fraction of a second in Firefox). Note that other browsers may not work: your life is too short to find out if they do. Submit the request, jump through the issuer's validation hoops and loops, sacrifice a goat, pray to the gods, submit a signed statement from your great grandparents, etc. Download the certificate (.crt) and import it into the same browser. The browser now has both the private key and the certificate. Export the certificate from the browser as a Personal Information Exchange (.p12) file. You will be asked to supply a password to protect this file. Keep a backup copy of the .p12 file. Run the Certificate Manager (certmgr.msc), right click on the Personal certificate store, select All Tasks/Import... and import the .p12 file into Windows. You will be asked for the password you used to protect the file. At this point, depending upon your security requirements, you can mark the key as exportable so you can restore a copy from the Windows store. You can also mark that a password is required before use if you want to break batch scripts. Run signtool successfully, breathe a sigh of relief, and ponder how much of your life you have wasted due to bad error messages and poor or missing documentation.

以防其他人遇到这种情况:我的问题是，在使用signtool.exe应用程序之前，我需要以管理员身份运行命令提示符。然后一切都很好地工作。

我在控制台应用程序开发中遇到了同样的问题，作为一个快速的解决方案，

那就去项目物业，

点击签名选项卡，取消选中“签名ClickOnce清单”。

图片描述:

供你参考，你也可以看到这个少于一分钟的视频解决方案。上面的图片是从视频中截取的。

使用/debug，当您得到这条消息“After Private Key filter, 0 certs were left.”时，一个原因可能是pfx文件没有私钥。 当您将已安装的证书导出到pfx文件时，请确保启用复选框还包括私钥。

我在使用Git Bash时得到了这个错误。 使用PowerShell成功。 如果这对谁有帮助的话。

在我的情况下，我有错误的证书类型，我试图关联。我选择了“服务器认证”而不是“代码签名”。 您应该能够在预期用途部分的Certificate snap中看到这一点。在那之后，它就可以正常工作了。