Windows 7 / Getting Started

---

ReportArchive Folder

The ReportArchive folder contains reports that have been uploaded or denied upload (via policy or explicit user action). This folder is referred to as the Archive store. Reports that are successfully submitted from the queue store(s) are automatically transferred to the archive store.

You also can create an Event Reporting Console (ERC) folder in the WER store folder(s). The subfolders in the ERC folder store response metadata and templates used for displaying the response data in the Problem Reports And Solutions Control Panel. You don't need to modify the data in the ERC folder, and modifying the data is not supported. The location of the ReportArchive folder is either of the following:

• Users\<username>\AppData\Local\Microsoft\Windows\WER\ReportArchive (for reports in the user store)
• ProgramData\Microsoft\Windows\WER\ReportArchive (for reports in the computer store)

Queue Reporting

When a new error report is successfully submitted to any of the queues or directly to the Watson back-end servers, WER enters Queue Reporting mode. In Queue Reporting mode, WER will prompt you to send the queued report(s) if conditions permit. If conditions are not optimal for reporting, WER schedules itself to be started when a network connection is established (SENS) or when the current user logs on the next time (HKCU\Run). This ensures that at some point in the future when conditions are right for reporting, infrastructure will be able to show the queued reporting console.

In Queue Reporting mode, WER performs the following checks in the following order:

1. Is the failing process running in an interactive desktop? If not, WerMgr.exe terminates. This is necessary because WER dialog boxes should not be shown for noninteractive desktops, such as the ones that the service accounts own.
2. Does the current user have reports in her queue, or is the current user an administrator and is administrative queuing enabled? If neither of the conditions is true, the current user has no reports to report. In this case, WER will ensure that network and logon triggers for the current user are removed, and it will exit immediately. If either of the conditions is true, WER attempts to prompt you to report entries in the queue.
3. WER sets the network and logon triggers for the current user in case conditions are not optimal for reporting at this time.
4. WER checks network access to see if the last reporting time has expired. If either of these checks fails, WerMgr.exe terminates.
5. Open the Problem Reports And Solutions Control Panel to prompt you and update the last reporting time.

Store Maintenance

By default, the Queue Management System performs maintenance such as deleting stale data and trimming the size of the queue on a report store whenever 50 saved reports are in the store. When the total queued report count exceeds the number defined in the registry value MaxQueueCount or the registry value MaxArchiveCount for archive stores, the queue subsystem deletes the oldest .cab files from the queues in the following order until the size of the queue reaches MaxQueueCount or no more CABs remain to delete:

• Archive Store
• Signoff Queue
• Upload Queue

The metadata for a report persists for one calendar year unless the user has disabled the archive via the DisableArchive setting.

WER queue data retention policies can be configured using Group Policy. If no queuing policies are configured, the Archive queue will retain 1,000 reports and the Upload/Signoff queue will retain 50 reports. If a queue becomes full and a new report is created, the new report will overwrite the oldest report in the respective queue.

Queue Triggers

This section describes the launch triggers that WER uses to ensure that the queued reporting prompt is started for users when they have unsent reports in their queues. Triggers are persistent across reboots.

WER launch triggers include:

• Network trigger This trigger starts WerMgr.exe in Queue Reporting mode for a specific user when a network connection is established. The network trigger is implemented through the SENS API that senses the presence of a network connection.
• Logon trigger This trigger starts WerMgr.exe in Queue Reporting mode for a specific user when the user logs on. WerMgr.exe is responsible for WER error queue management.
• Administrator trigger The administrator trigger notifies an administrator of unsent entries in the machine queue. This trigger occurs only for administrators on the system.