For more information about the underlying functionality that redirects error reports to a server on your intranet, see WER Settings on the MSDN website. For more information about the answer-file entries or Group Policy settings that are described in this subsection, see Controlling Windows Error Reporting to prevent the flow of information to and from the Internet later in this section.
The data that Microsoft collects through Windows Error Reporting is used strictly for the purpose of tracking and solving issues that users and administrators are experiencing. This subsection describes various aspects of the data that is sent to and from the Internet during error reporting, and how the exchange of information takes place.
The next subsection provides additional details. Specific information sent or received : In most cases, the information that is collected for an error report only includes software parameters, which include such information as the application name and version, module name and version, and exception code. In unusual cases, a more complete crash report might be collected. Rarely, some information that is unique to the person who is using the computer might be collected unintentionally.
This information, if present, is not used to identify the person. Microsoft may send solution information about an issue to the user or administrator, including links to websites. Default settings : By default, error reporting is enabled. However, additional configuration steps are needed to configure error reporting, and no reports are sent unless these steps are completed.
When a computer is started for the first time, the Initial Configuration Tasks interface appears which displays a variety of tasks including Enable automatic updating and feedback. In this task, you can choose to enable a default level of automatic updating and feedback which includes error reporting , or you can manually configure settings. For details about consent levels, see Consent levels in Windows Error Reporting earlier in this section.
Triggers : The opportunity to send an error report is triggered by application or system errors. User notification : User notification depends on the consent level. See Consent levels in Windows Error Reporting earlier in this section. Windows provides reminders in the form of pop-up notifications to check for solutions to reports that have not been sent, for example, reports that were generated in the background or while you were offline.
Logging : Descriptions of system and application errors are recorded in the event log. In addition, the Problem Reports and Solutions feature records information about problem reports sent and solution information received on that computer, so that the user or administrator can investigate solutions later. New solutions might overwrite old solutions if the number of stored solutions exceeds the allowed maximum. The software parameters information, which includes such information as the application name and version, module name and version, and exception code, is also encrypted.
Access : Microsoft employees and contingent staff may access the error reports to maintain Windows Error Reporting or to improve Microsoft products. They may not use the reports for other purposes. If the error report indicates that one or more non-Microsoft products were involved in causing the issue, Microsoft may send the report to the respective companies if the companies agree to abide by the terms of the privacy statement.
Software or hardware developers employed by Microsoft or one of its partners may analyze the fault data and try to identify and correct the problem. Details that are related to privacy of data are presented in Types of data collected later in this section.
Ability to disable : The feature can be disabled through Group Policy or on an individual computer. You can also control the feature as described in Overview: Using Windows Error Reporting and the Problem Reports and Solutions feature in a managed environment earlier in this section, and Controlling Windows Error Reporting to prevent the flow of information to and from the Internet later in this section.
This section provides an overview of the data that Windows Error Reporting collects and information about data that might be collected from four sources:. Windows Error Reporting collects information about the computer configuration, what the software was doing when the problem occurred, and other information directly related to the issue.
It is possible that such information may be captured in memory or in the data that is collected from open files, but Microsoft does not use it to identify users. Windows Error Reporting collects Internet Protocol IP addresses, but the addresses are not used to identify users, and in many cases, they are the address of a network address translation NAT computer or proxy server, not a specific client behind that NAT computer or proxy server.
IP address information is used in aggregate by the operators who maintain the servers that receive error reports. Use WerAddExcludedApplication. The directory path. If the default is not used, the application must ensure that the folder has a sufficient ACL. Windows Vista: The registry values under the LocalDumps key are not supported. Note that per-process settings will override any global settings that exist For more information, see Collecting User-Mode Dumps.
The maximum number. The default is When the maximum value is exceeded, the oldest dump file in the folder will be replaced with the new dump file.
Possible values: 0 - Custom dump 1 - Minidump default 2 - Full dump. The custom dump options to be used. This value is used only when DumpType is set to 0. WER's Live Kernel Reports settings, which are described next, are both located under the following registry subkey:.
Yes No. Sorry this didn't help. Thanks for your feedback. Will ther be any issue after that? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Developers can register with Windows Desktop Application Program to get information about the problems customers are experiencing with their applications and help customers fix these problems.
Developers can also use Application Recovery and Restart to ensure that customers do not lose data when their application crashes and allow users to quickly return to their tasks.
Application Recovery and Restart. Windows Desktop Application Program. Skip to main content.
0コメント