sodcalculator

10 Tech How-To

System Queued Windows Error Reporting: Fix

Guide 10-52575 · Updated · Step by step

System queued Windows Error Reporting is a message that appears when Windows has collected error data that it has not yet sent to Microsoft. The fix is to either send the reports, clear the queue, or disable the reporting service—each is covered below. This article explains what the queue is, why it fills up, and the exact steps to resolve it on current versions of Windows.

What Is Windows Error Reporting?

Windows Error Reporting (WER) is a built-in feature that has existed since Windows XP. When a program crashes or stops responding, WER collects a small dump file—usually a few megabytes—containing the state of the crashed process. It then asks whether you want to send that data to Microsoft. If you choose not to send it immediately, or if the system is busy, the report is placed in a local queue.

The queue is stored under C:\ProgramData\Microsoft\Windows\WER\ReportQueue. Each subfolder holds one pending report, with files like Report.wer and a memory dump. The “System queued Windows Error Reporting” notification typically appears in the Action Center or as a balloon tip when the queue contains at least one report that has not been transmitted.

WER is not the same as the Blue Screen of Death (BSOD) memory dump. BSOD dumps are larger and stored separately; WER handles application crashes, hangs, and kernel-mode faults with smaller payloads. The queue is a temporary holding area—reports sit there until Windows sends them, usually during idle time or when you click the notification.

Why the Queue Fills Up

The queue grows for several common reasons:

  • You clicked “Don’t send”—Windows still stores the report locally for a while in case you change your mind.
  • No internet connection—if the network is unavailable, reports wait until connectivity returns.
  • Group Policy or registry settings—some administrators set WER to queue reports but never send them automatically.
  • Frequent crashes—a program that crashes repeatedly generates many reports in a short time.
  • Corrupted queue files—if a report is damaged, Windows may fail to send it and keep retrying.

In most cases, a full queue is harmless. It uses disk space (typically under 100 MB) and does not slow down your system. However, the notification can be annoying, and in rare cases a corrupted queue can cause the Action Center to hang or the WER service to use high CPU.

How to Send or Clear the Queue

You have three options. Choose based on whether you want to help Microsoft improve Windows or simply stop the notification.

Option 1: Send the Reports Manually

  1. Open Control Panel and go to System and Security > Security and Maintenance (or search for “Security and Maintenance” in the Start menu).
  2. Click Maintenance to expand the section.
  3. Look for “Review reliability history” or “Check for solutions to problem reports”. The exact link varies by Windows version.
  4. If you see a list of pending reports, click Send or Check for solutions.

Alternatively, you can open the Action Center (click the flag icon in the taskbar) and click the message about queued reports. Windows will then upload them.

Option 2: Delete the Queue Manually

  1. Open File Explorer and navigate to C:\ProgramData\Microsoft\Windows\WER\ReportQueue.
  2. Select all folders inside (Ctrl+A) and press Delete. You may need administrator permission.
  3. Empty the Recycle Bin.

This removes the reports permanently. The notification should disappear immediately. If it does not, restart the Windows Error Reporting service (see below).

Option 3: Disable Windows Error Reporting

If you never want to see the notification again, you can turn off WER entirely. This is a system-wide change and will stop all error reporting, including for future crashes.

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll to Windows Error Reporting Service.
  3. Right-click it and select Properties.
  4. Set Startup type to Disabled.
  5. Click Stop if the service is running, then OK.

You can also disable it via Group Policy (for Windows Pro/Enterprise): gpedit.msc > Computer Configuration > Administrative Templates > Windows Components > Windows Error Reporting and set “Disabled” for “Windows Error Reporting”.

Common Problems and Their Fixes

If the notification persists after clearing the queue, try these steps:

  • Restart the WER service—open services.msc, right-click Windows Error Reporting Service, and choose Restart.
  • Clear the archive folder too—the ReportArchive folder (next to ReportQueue) stores sent reports. Deleting it can help if the queue is stuck.
  • Check for corrupted files—run sfc /scannow in an elevated Command Prompt to repair system files.
  • Update your drivers—recurring crashes often come from outdated or faulty drivers. Check Windows Update and the device manufacturer’s website.
  • Run Disk Cleanup—the built-in tool can remove old WER files. Open Disk Cleanup, select the system drive, and check “Temporary files” and “System error memory dump files”.

If you are on a corporate network, your IT department may have a policy that forces queuing. In that case, you cannot clear it manually without breaching policy—contact your administrator.

Privacy and Security Considerations

WER reports can contain sensitive information. The crash dump may include snippets of memory from the crashed process, which could hold passwords, documents, or other data that was in use at the time. Microsoft states that it uses the data only to fix bugs and does not intentionally collect personal information, but you should be aware of what you are sending.

If privacy is a concern, you have two safe options:

  • Delete the queue and never send anything.
  • Disable WER entirely via the service or Group Policy.

Disabling WER does not affect Windows Update or other system functions. It only stops the error reporting feature. You can re-enable it at any time by setting the service back to “Automatic” and starting it.

Alternatives to WER

If you are troubleshooting a recurring crash, WER is not your only tool. The Reliability Monitor (type perfmon /rel in the Run dialog) shows a timeline of crashes and warnings, which can help identify the offending software. The Event Viewer (eventvwr.msc) logs detailed error codes under “Windows Logs > Application” and “System”. For kernel crashes, the BlueScreenView utility (from NirSoft, a third-party tool) can read minidump files and display the driver that caused the BSOD.

These tools do not send data to Microsoft—they only read local logs. They are useful if you want to diagnose the problem yourself without participating in WER.

Frequently Asked Questions

Is it safe to delete the queued error reports?

Yes. Deleting the files in ReportQueue only removes pending crash reports. It does not affect your system, installed programs, or Windows Update. The only downside is that Microsoft will not receive the data, so a bug that caused the crash may not be fixed in a future update.

Why does Windows keep asking me to send error reports?

Windows asks each time a program crashes. If you click “Don’t send”, the report is still queued for a while. If the same program crashes repeatedly, you will see the notification again. To stop the prompts, disable WER as described above.

How much disk space does the error reporting queue use?

Each report is typically 1–10 MB, depending on the crash type. A full queue rarely exceeds a few hundred megabytes. You can check the folder size by right-clicking ReportQueue in File Explorer and selecting Properties.

Will disabling WER affect Windows Update?

No. Windows Update is a separate service. Disabling WER only stops crash reporting. Your system will still receive security and feature updates normally.

What if I cannot delete the files because they are in use?

Stop the Windows Error Reporting Service first (as shown in Option 3), then delete the folder contents. If the service is still running, it may lock the files. After deletion, restart the service if you want to keep WER enabled.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →