Microsoft Watson Error Reporting
Contents |
reporting technology introduced by Microsoft with WindowsXP[1] and included in later Windows versions and Windows Mobile 5.0 and 6.0. Not to be windows error reporting localdumps confused with the Dr. Watson debugging tool which left the windows error reporting disable memory dump on the user's local machine, Windows Error Reporting collects and offers to send post-error
Windows Error Reporting Windows 10
debug information (a memory dump) using the Internet to the Microsoft or stops responding on a user's desktop. No data is sent without the user's consent.[2] When
Enable Windows Error Reporting
a dump (or other error signature information) reaches the Microsoft server, it is analyzed and a solution is sent back to the user when one is available. Solutions are served using Windows Error Reporting Responses. Windows Error Reporting runs as a Windows service and can optionally be entirely disabled. If Windows Error Reporting itself windows error reporting location crashes, then an error report that the original crashed process produced cannot be sent at all. Kinshuman is the original designer of Windows Error Reporting in Vista which is the same design and implementation that is present in current Windows versions. [3] Contents 1 History 1.1 Windows XP 1.2 Windows Vista 1.3 Windows 7 1.4 Windows 8 2 System design 2.1 Buckets 3 Third-party software 4 Impact on future software 5 Privacy concerns and use by the NSA 6 Alternatives 7 See also 8 References History[edit] Windows XP[edit] Microsoft first introduced Windows Error Reporting with WindowsXP.[1] Windows Vista[edit] Windows Error Reporting was improved significantly in WindowsVista. Most importantly a new set of public APIs have been created for reporting failures other than application crashes and hangs.[4] Developers can create custom reports and customize the reporting user interface. The new APIs are documented in MSDN. The architecture of Windows Error Reporting has been revamped with a focus on reliability a
Chen - MSFTAugust 10, 200533 Share 0 0 The nickname for the feature known as Windows Error Reporting is "Dr. Watson". Where did that name come from? As you have probably guessed,
Windows Error Reporting Disable Windows 10
The name Dr.Watson was inspired by the character of Dr.Watson, the assistant windows error reporting registry to Sherlock Holmes in the stories by Arthur Conan Doyle. It is my understanding that the doctor was windows error reporting tool originally developed as part of Windows3.0 beta testing. His job was to record data about application crashes to a file, so that the file could be uploaded and included with https://en.wikipedia.org/wiki/Windows_Error_Reporting bug reports. The icon was (and continues to be) a friendly doctor using his stethoscope to investigate a problem. The Doctor has remained true to the "capture information about an error" aspect of his job. In the meantime, the word "Watson" has expanded its meaning to encompass anonymous end-user feedback mechanisms in general, such as "Content Watson". (But if you hear https://blogs.msdn.microsoft.com/oldnewthing/20050810-13/?p=34623 "Watson" by itself, the speaker is almost certainly talking about error reporting.) Tags History Comments (33) Anonymous says: August 10, 2005 at 10:11 am Is Microsoft not afraid that the SQM stuff which is pronounced Squim might not be nicknamed Quim
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).aspx Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore Why Windows What’s new for Windows error reporting 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples windows error reporting Support Dashboard Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Diagnostics Windows Error Reporting Using WER Using WER Collecting User-Mode Dumps Collecting User-Mode Dumps Collecting User-Mode Dumps Collecting User-Mode Dumps TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Collecting User-Mode Dumps Starting with Windows Server 2008 and Windows Vista with Service Pack 1 (SP1), Windows Error Reporting (WER) can be configured so that full user-mode dumps are collected and stored locally after a user-mode application crashes. Applications that do their own custom crash reporting, including .NET applications, are not