Windows Error Reporting: Difference between revisions

Revision as of 12:37, 26 January 2022

Latest revision as of 18:42, 23 January 2025

(18 intermediate revisions by 15 users not shown)

Line 1:

{{Short description|Crash reporting technology}}

[[File:Windows Error Reporting problem details.png|thumb|right|Windows Error Reporting displaying problem details from an issue with [[Windows Explorer]]]]

'''Windows Error Reporting''' ('''WER''') (codenamed Watson) is a [[crash reporter|crash reporting]] technology introduced by [[Microsoft]] with [[Windows&nbsp;XP]]<ref name="whatisit">[http://blogs.msdn.com/b/wer/archive/2008/12/26/what-are-wer-services.aspx What are WER Services?]</ref> and included in later Windows versions and [[Windows Mobile]] 5.0 and 6.0. Not to be confused with the [[Dr. Watson (debugger)|Dr. Watson]] debugging tool which left the memory dump on the user's local machine, Windows Error Reporting collects and offers to send post-error [[debug]] information (a [[Core dump|memory dump]]) using the Internet to [[Microsoft]] when an application crashes or stops responding on a user's desktop. No data is sent without the user's consent.<ref>[http://blogs.msdn.com/b/wer/archive/2009/03/11/an-overview-of-wer-consent-settings-and-corresponding-ui-behavior.aspx An overview of WER consent settings and corresponding UI behavior]</ref> When a crash dump (or other error signature information) reaches the Microsoft server, it is analyzed, and information about a solution is sent back to the user if available. Solutions are served using Windows Error Reporting Responses. Windows Error Reporting runs as a [[Windows service]].

<ref>[https://xxsolution.com/ 0x0 0x0 Solution]</ref>

Kinshuman Kinshumann is the original architect of WER. WER was also included in the [[Association for Computing Machinery|Association for Computing Machinery (ACM)]] hall of fame for its impact on the computing industry.

<ref>[http://m.cacm.acm.org/magazines/2011/7/109883-debugging-in-the-very-large/abstract Debugging in the (Very) Large: Ten Years of Implementation and Experience]</ref>

<ref>[https://www.sigops.org/2019/hof-award-2019/ WER CACM Award Kinshuman]</ref>

==History==

===Windows XP===

[[Microsoft]] first introduced Windows Error Reporting with [[Windows XP]].<ref name="whatisit" /> It was added during early Beta 1 development in build 2250 as Exception Reporting, and was renamed to Error Reporting in build 2267.

===Windows Vista===

Line 13 ⟶ 16:

===Windows 7===

The Problem Reports and Solutions [[Control Panel (Windows)|Control Panel]] applet was replaced by the Maintenance section of the [[WindowsSecurity and Maintenance|Action Center]] on [[Windows 7]] and [[Windows Server 2008 R2|Server 2008 R2]].

A new app, Problem Steps Recorder (PSR.exe), is available on all builds of Windows 7 and enables the collection of the actions performed by a user while encountering a crash so that testers and developers can reproduce the situation for analysis and debugging.<ref>[http://msdn.microsoft.com/en-us/library/windows/desktop/dd371782(v=vs.85).aspx Windows Error Reporting Problem Steps Recorder]</ref>

Line 41 ⟶ 44:

==Third-party software==

Software & hardware manufacturers may access their error reports using Microsoft's [[Windows Dev Center]] Hardware and Desktop Dashboard (formerly [[Winqual]]) program.<ref>[{{Cite web |url=https://sysdev.microsoft.com/ |title=SysDev (was Winqual) website] |access-date=2012-11-07 |archive-date=2018-08-03 |archive-url=https://web.archive.org/web/20180803125334/http://sysdev.microsoft.com/ |url-status=dead }}</ref> In order to ensure that error reporting data only goes to the engineers responsible for the product, Microsoft requires that interested vendors obtain a [[VeriSign]] Class 3 Digital ID or [[DigiCert]] certificate.<ref>[http://msdn.microsoft.com/en-us/library/windows/hardware/br230783.aspx Update a code signing certificate]</ref> Digital certificates provided by cheaper providers (such as [[Thawte]], [[Comodo Group|Comodo]], [[GlobalSign]], [[GeoTrust]], [[Cybertrust]], [[Entrust]], [[GoDaddy]], QuoVadis, [[Trustwave]], [[SecureTrust]], [[Wells Fargo]]) are not accepted.<ref>[http://blogs.technet.com/b/empower/archive/2007/05/15/introducing-windows-error-reporting.aspx Introducing Windows Error Reporting]</ref><ref>[http://idvlpsw.wordpress.com/2008/03/08/winqual-registration-head-aches/ WinQual Registration Head Aches]</ref><ref>[http://social.msdn.microsoft.com/forums/en-US/windowscompatibility/thread/37cc820e-d715-44b2-a7bd-a7fe47f6f13e/ Microsoft Support Forum: WER with Thawte authenticode signed app]</ref><ref>[https://archive.today/20120707011358/http://blogs.msdn.com/oldnewthing/archive/2005/08/10/449865.aspx The Old New Thing: How can a company get access to Windows Error Reporting data?]</ref><ref>[http://successfulsoftware.net/2008/02/27/the-great-digital-certificate-ripoff/ The great digital certificate ripoff?]</ref>

Software and hardware manufacturers can also close the loop with their customers by linking error signatures to Windows Error Reporting Responses. This allows distributing solutions as well as collecting extra information from customers (such as reproducing the steps they took before the [[Crash (computing)|crash]]) and providing them with support links.

==Impact on future software==

Microsoft has reported that data collected from Windows Error Reporting has made a huge difference in the way software is developed internally. For instance, in 2002, [[Steve Ballmer]] noted that error reports enabled the Windows team to fix 29% of all Windows&nbsp;XP errors with Windows XP SP1. Over half of all [[Microsoft Office]] XP errors were fixed with Office XP SP2.<ref>[http://www.microsoft.com/mscorp/execmail/2002/10-02customers.mspx Steve Ballmer's letter: Connecting to customers]</ref> Success is based in part on the [[pareto principle|80/20 rule]]. Error reporting data reveals that there is a small set of bugs that is responsible for the vast majority of the problems users see. Fixing 20% of code defects can eliminate 80% or more of the problems users encounter. An article in the [[New York Times]] confirmed that error reporting data had been instrumental in fixing problems seen in the beta releases of Windows&nbsp;Vista and [[Microsoft Office 2007]].<ref>[{{cite news |title=A Challenge for Exterminators (Published 2006) |work=The New York Times |date=9 October 2006 |url=https://www.nytimes.com/2006/10/09/technology/09vista.html?_r=1&oref=slogin&pagewanted=print A|last1=Markoff challenge for|first1=John exterminators]}}</ref>

==Privacy concerns and use by the NSA==

Although Microsoft

Although Microsoft has made privacy assurances, they acknowledge that [[personally identifiable information]] could be contained in the memory and application data compiled in the 100-200&nbsp;KB "minidumps" that Windows Error Reporting compiles and sends back to Microsoft. They insist that in case personal data is sent to Microsoft, it won't be used to identify users, according to Microsoft's [[privacy policy]].<ref>[{{Cite web |url=http://oca.microsoft.com/en/dcp20.asp |title=Microsoft Privacy Statement for Error Reporting] |access-date=2007-10-07 |archive-date=2012-10-10 |archive-url=https://web.archive.org/web/20121010075211/http://oca.microsoft.com/en/dcp20.asp |url-status=dead }}</ref><ref>[http://support.microsoft.com/kb/283768/ Description of the end user privacy policy in application error reporting when you are using Office]</ref> But in reporting issues to Microsoft, users need to trust Microsoft's partners as well. About 450 partners have been granted access to the error reporting database to see records related to their [[device driver]]s and apps.<ref>{{cite web | url = https://rcpmag.com/articles/2002/10/03/microsoft-error-reporting-drives-bug-fixing-efforts.aspx | title = Microsoft Error Reporting Drives Bug Fixing Efforts | last = Bekker | first = Scott | date = 3 October 2002 | website = Redmond Partner Channel | publisher = 1105 Redmond Media Group}}</ref>

Older versions of WER send data without encryption; only WER from [[Windows 8]] uses TLS encryption.<ref name="wsense2013-12"/> In March 2014, Microsoft released an update (KB2929733) for Windows Vista, 7 and Server 2008 that encrypts the first stage of WER.<ref>{{cite web|title=The first stage of the WER protocol is not SSL encrypted in Windows|url=http://support.microsoft.com/kb/2929733|publisher=Microsoft|access-date=10 January 2015|date=11 March 2014}}</ref>