Monitoring Task Manager in Windows 11 only to notice your cooling fans spinning at maximum speed and an executable named WerMgr.exe (Windows Problem Reporting) consuming 80% to 100% of CPU and disk throughput causes system sluggishness. WerMgr.exe is the native Windows Error Reporting executable responsible for generating diagnostic crash dumps, collecting application fault logs, and uploading telemetry data to Microsoft servers whenever software crashes. When a background system service or device driver enters a continuous crash loop, WerMgr.exe launches repeatedly, creating an infinite backlog of uncompressed crash dumps that overwhelms processor resources.
Why Does WerMgr.exe Consume Excessive CPU and Disk?
The Windows Error Reporting manager is designed to execute briefly during a crash event. Persistent utilization is driven by:
- Background Application Crash Loop: A broken background utility, third-party antivirus component, or peripheral driver crashing and restarting hundreds of times per minute.
- Corrupted WER Report Queue: Damaged crash dump files inside
C:\ProgramData\Microsoft\Windows\WER\ReportQueuelocking the reporting engine in an upload retry loop. - Corrupted System Files: Damaged Windows core libraries causing Windows Error Reporting itself to encounter runtime exceptions.
- Low Disk Space on System Partition: Inability to write complete crash logs causing the WER service to repeatedly reallocate swap memory.
Step 1: End the WerMgr.exe Process in Task Manager
Immediately recover processor capacity by terminating the runaway diagnostic threads.
- Press Ctrl + Shift + Esc to open Task Manager.
- Switch to the Details tab.
- Sort the process list by Name and locate
WerFault.exeorWerMgr.exe. - Right-click the process and select End process tree.
- Check if new instances immediately respawn; if so, proceed to Step 2 to clear the report queue.
Step 2: Clear Corrupted Windows Error Reporting Queues
Deleting accumulated crash reports stops the Windows Error Reporting service from reprocessing stale crash dumps.
- Press Win + R, paste the following directory path, and press Enter:
C:\ProgramData\Microsoft\Windows\WER - Open the ReportArchive and ReportQueue folders.
- Press Ctrl + A to select all files and subfolders within these directories, and press Shift + Delete to permanently remove them.
- Repeat this process for user-specific error queues:
%localappdata%\Microsoft\Windows\WER - Clear any cached crash files in the user directory to restore storage health.
Step 3: Identify the Crashing Application in Event Viewer
Stopping WerMgr.exe requires resolving the root program that continues crashing in the background.
- Press Win + X and choose Event Viewer.
- Expand Windows Logs on the left pane and select Application.
- Look for recurring Error entries with Source marked as Application Error or Windows Error Reporting.
- Review the Faulting application name (such as an audio driver utility, game launcher, or OEM software).
- Uninstall, update, or reinstall the offending application to stop the crash cascade.
Step 4: Run System File Checker (SFC) and DISM
Repair core Windows servicing components to eliminate operating system faults.
- Open Terminal (Admin) or Command Prompt (Admin).
- Execute the DISM repair command:
DISM /Online /Cleanup-Image /RestoreHealth - Once DISM reaches 100%, execute the System File Checker:
sfc /scannow - Allow the scan to finish and restart Windows 11.
Step 5: Disable Windows Error Reporting Service (Temporary Workaround)
If a legacy application must remain running while awaiting a vendor patch, disable the WER service temporarily.
- Press Win + R, type
services.msc, and press Enter. - Scroll down to find Windows Error Reporting Service.
- Right-click the service and select Properties.
- Change the Startup type to Disabled.
- Click Stop under Service status, then click Apply and OK.