Windows Error Reporting: Getting Started
Windows Error Reporting (WER) is a set of Windows technologies that capture software crash and failure data from end users. This data is analyzed to create a list of top user-mode (software) and kernel-mode (operating system) failures associated with a company’s mapped products. Through the Hardware Dev Center hardware dashboard website, software and hardware vendors can access these reports and use them to analyze, fix and respond to these failures. This service is available for all products, even those that do not qualify for the Microsoft Certified Products list—although we strongly recommend that you submit your products to the Windows Hardware Compatibility Program.
Over time, Microsoft has found that across all the issues that exist on the affected Windows platforms and the number of incidents received:
Fixing 20 percent of the top-reported bugs can solve 80 percent of customer issues.
Addressing 1 percent of the bugs would address 50 percent of the customer issues.
To access WER reporting service, as well as Hardware Dev Center hardware dashboard, you need a standard code signing certificate. To learn more about code signing certificates, see Get a code signing certificate.
Once you have a Hardware Dev Center hardware dashboard account, you can log in to view the top user-mode and kernel-mode failures associated with your company’s mapped products. For more information about the options available in these reports, see Browse Reports.
After you’ve analyzed a specific user-mode or kernel-mode failure, and created a fix or other solution, you can then create a response to be delivered through Windows Action Center to your customers. After this response is in place, customers who experience this problem (including those who experienced the problem in the past) will receive your solution.
By taking advantage of the WER feedback loop, you can provide information to your customers to help solve their problems and to reduce your company's support costs. For more information about how to create responses, see Create Responses.