Windows 7 Pro 上的 64 位凭据提供程序
我已经建立了自己的证书。我在Windows 7 home的64位系统上安装了它，没问题。我尝试在 3 台不同的 Windows 7 64 pro 机器上安装它，但我的提供程序未显示。
我不知道 Windows 7 版本中关于凭据提供程序存在差异。
我不知道该尝试什么来解决问题。我尝试安装商业提供程序（aloaha，rohos），它们没问题，我尝试安装微软示例（64位编译），但它们没有显示。
在 Windows 7 Home Premium 64 位中一切正常。
I have build a my own credential. I Installed it on 64 bit systems with Windows 7 home and it's ok. I tried to install it on 3 different machines with windows 7 64 pro and my provider is not shown.
I didn't know that there were differences in windows 7 version about credential provider.
I don't know what to try to solve problem. I tried to install a commercial Provider (aloaha, rohos) and they are ok, I tried to install microsoft samples ( 64 bit compiling) but they are not shown.
In windows 7 home premium 64 bit all is ok.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
你是用调试选项构建的吗？如果是这样，您的其他计算机上可能缺少调试运行时库。
您可以尝试以下一些操作
加载到dependency walker查看哪些库链接到您的CP。在加载正常的机器和未加载的机器上执行此操作。如果找不到某些 LogonUI 相关库，请不要惊慌，这是正常的。
尝试使用 WinDBG 查看登录界面，以确保确实没有加载并且没有其他任何内容在起作用。请查看此处
调试这些内容的最全面的方法是按照 这里。下载 ZIP 文件并阅读文档，尤其是调试部分。它非常复杂，您需要设置串行连接或使用虚拟机进行设置。但这样您就可以在登录界面启动时设置断点，您将能够看到凭据提供程序的加载顺序，并在出现故障时看到确切的错误消息。
Did you build it with the debug options? If so you are probably missing debug runtime libraries on your other machines.
Here are some things for you to try
Load into dependency walker see what libraries are linked to your CP. Do this on both the machine where it loads ok and the machine where it doesn't load. Don't be alarmed if it can't find some LogonUI related libraries, this is normal.
Try looking at logonui with WinDBG to make sure that it really the case that it doesn't load and there is not anything else is at play. Look here for instructions.
The most comprehensive way to debug those is to use setup the debugging as described here. Download the ZIP file and read the document especially the debugging section. It is pretty involved and you need to setup either a serial connection or do it with the VM. But this way you will be able to set a breakpoint right when logonui starts up, you will be able to see the loading sequence of the credential providers and will see the exact error message when something fails.