在哪里报告 Windows 核心库问题？
如何让 Microsoft 了解我在其核心库例程之一中发现的问题？ 他们有一个中央存储库来报告这些事情吗？
我不是 Microsoft 开发网络 (MSDN) 的成员。
或者我应该打扰吗？
How do I let Microsoft know about a problem I've found in one of their core library routines? Do they have a central repository to report these things?
I am not a member of Microsoft Development Network (MSDN).
Or should I even bother?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
最终用户没有向 Microsoft 报告错误的官方方法。 如果您正在参与即将发布的版本的测试版计划，则该测试版计划包括错误报告渠道。 否则，如果该错误导致您想要解决的问题，您可以致电 Microsoft 支持，他们将帮助您解决问题（无论是提供补丁还是解决方法）； 如果问题确实是由错误引起的，他们将退还支持电话的费用。
Microsoft 确实有一个中央存储库（可能每个产品都有一个单独的存储库），但公众无法访问该存储库。
There is no official way to report bugs to Microsoft for an end-user. If you are participating in a beta program for an upcoming release, the beta program includes a bug-reporting channel. Otherwise, if the bug causes problems that you want to get resolved, you can call Microsoft support, and they will help you solving the problem (be it by providing a patch, or a work-around); if the problem turns out to be caused by a bug indeed, they will refund the costs of the support call.
Microsoft does have a central repository (perhaps separate ones per product), but this repository is not accessible for the general public.
如果这是文档错误（或者文档应该指出它），您可以通过 MSDN 库中的反馈链接获得良好的结果。 您可以通过在 connect.microsoft.com 上注册来报告 Microsoft 开发人员工具（以及其他工具）中的错误。
如果您确定在核心库例程中发现了错误，您可以提出 PSS（支持案例。这会花费您金钱，但如果结果证明您是对的（并且他们会向您提供修补程序） ，我认为他们会退款，
我从来没有如此自信地发现了一个错误，以至于我愿意进行赌博。
If it's a documentation bug (or if the documentation should call it out), you can get good results with the Feedback links in MSDN library. You can report bugs in Microsoft developer tools (among other things) by signing up at connect.microsoft.com.
If you're sure you've found a bug in a core library routine, you can raise a PSS (support case. It'll cost you money, but if it turns out you're right (and they issue you a hotfix), I think that they refund the money.
I've never been so confident that I've found a bug that I'm willing to make that gamble.
我不知道为什么 ChrisN 收回了他的答案。 今天早些时候，当他提出这个问题时，我看到了，他说：
我没有听说过 Microsoft Connect 网站，但是当我使用那里的搜索框搜索“Registry Unicode”时，列出的第一个条目是一个与我遇到的错误非常相似的错误。 并单击该条目让我查看了似乎是 Microsoft 人员解决该问题的对话，将其传递给适当的人员并根据需要升级。
我没有使用 Microsoft Connect 网站的经验，但如果事实证明它像看起来那样有前途，那么这可能就是我问题的答案。
I don't know why ChrisN took back his answer. I saw it earlier today when he had it up, He said:
I had not heard of the Microsoft Connect website, but when I used the search box there to search for "Registry Unicode", the first entry listed was a bug very similar to the one I encountered. And clicking through on that entry led me to look at the conversation that appears to be Microsoft people addressing the issue, passing it on to appropriate people and escalating it as necessary.
I have no experience with the Microsoft Connect website, but if it turns out to be as promising as it appears, this may be the answer to my question.