How to Clean User Application CrashDumps (%LocalAppData%\CrashDumps)

🟢 100% Safe to Delete Typical Space Reclaimed: 1.0 GB – 12.0 GB

Location & Quick Verdict

%LocalAppData%\CrashDumps

Windows WER writes full process memory dumps (.dmp) into %LocalAppData%\CrashDumps whenever a game or desktop app crashes.

Safety confirmation: Completely safe to delete unless you are actively debugging a recent crash in WinDbg.

Why Kernel Minidumps, WER Archives & ETW Traces Fill User Application CrashDumps (%LocalAppData%\CrashDumps)

Whenever a hardware driver times out (TDR), a background service faults, or Windows Servicing installs a patch, the Windows Error Reporting (WER) pipeline and kernel crash handler write uncompressed memory snapshots (.dmp) and verbose text logs into %LocalAppData%\CrashDumps. A single full or kernel memory dump or LiveKernelReports WATCHDOG snapshot can consume 500 MB to 4 GB of disk space immediately.

Unless you are actively debugging a recurring Blue Screen of Death (BSOD) with WinDbg right now, historical crash dumps and rotated CBS/DISM log archives inside %LocalAppData%\CrashDumps serve zero runtime purpose. Deleting User Application CrashDumps (%LocalAppData%\CrashDumps) safely reclaims 1.0 GB – 12.0 GB without affecting Windows stability or future error reporting.

PowerShell Size Verification (Read-Only Check):
# Inspect current disk footprint of User Application CrashDumps (%LocalAppData%\CrashDumps) (Read-Only)
$target = "$env:LOCALAPPDATA\CrashDumps"
Get-ChildItem -Path $target -Recurse -Force -ErrorAction SilentlyContinue |
  Measure-Object -Property Length -Sum |
  Select-Object Count, @{Name="SizeGB";Expression={[math]::Round($_.Sum / 1GB, 2)}}
🛡️ What Stays 100% Protected Active Windows kernel drivers, system services, Event Viewer configuration, and OS stability are completely unaffected.
⚡ What Gets Safely Removed Historical kernel/user minidumps (.dmp), WATCHDOG GPU timeout snapshots, Windows Error Reporting (.wer) queues, and rotated servicing logs.

Manual Cleaning Instructions

  1. 1 Press Windows Key + R, type %localappdata%\CrashDumps and press Enter.
  2. 2 Select all .dmp files (Ctrl+A) and press Delete.

Note: If Windows alerts that a file is in use or locked by a background process, close the associated task in Task Manager before deleting, or use SWEEPR Cleaner to release locked handles safely.

Sub-Folders & Cache Locations Breakdown for User Application CrashDumps (%LocalAppData%\CrashDumps)

Modern Windows applications and system services split their disk footprint across multiple sub-directories (`Cache_Data`, `Service Worker\CacheStorage`, `Code Cache`, `GPUCache`, and `Crashpad\reports`). Review which sub-folders inside User Application CrashDumps (%LocalAppData%\CrashDumps) are safe to purge and which files remain protected:

Sub-Folder / Cache Location Storage Role Typical Footprint Deletion Safety
%LocalAppData%\CrashDumps (*.dmp / *.hdmp / *.mdmp) Uncompressed Kernel & User-Mode Memory Crash Dumps 1.0 GB – 12.0 GB 🟢 100% Safe
C:\ProgramData\Microsoft\Windows\WER\ReportArchive Queued & Archived Windows Error Reporting Bundles 300 MB – 4.0 GB 🟢 100% Safe
C:\Windows\Logs\CBS & DISM Rotated Servicing & Component Store Text Logs 250 MB – 3.5 GB 🟢 100% Safe
Active Windows Drivers & Event Viewer Channels Live System Services & Security Audit Configuration Protected 🔒 Protected — Never Touched

Frequently Asked Questions

Is it safe to delete User Application CrashDumps (%LocalAppData%\CrashDumps)?

Yes, 100% safe. Completely safe to delete unless you are actively debugging a recent crash in WinDbg.

How much storage space will cleaning User Application CrashDumps (%LocalAppData%\CrashDumps) free up?

Users typically reclaim 1.0 GB – 12.0 GB on Windows 10 and Windows 11 systems depending on update frequency and active cache retention in %LocalAppData%\CrashDumps.

Does Windows need the files in User Application CrashDumps (%LocalAppData%\CrashDumps) to boot or run properly?

No. Files inside %LocalAppData%\CrashDumps are strictly post-mortem diagnostic snapshots and historical logs written for troubleshooting. Windows never reads them during normal startup or runtime operation.

Where is User Application CrashDumps (%LocalAppData%\CrashDumps) located on Windows 10 and Windows 11?

It is stored at %LocalAppData%\CrashDumps. You can paste that path directly into the Windows Run dialog (Win + R) or File Explorer address bar to inspect it.

Manual File Explorer vs. 1-Click SWEEPR Cleanup

Feature Manual Deletion SWEEPR Cleaner
Locked File Handling Fails on locked processes Safe background release
Accidental Deletion Risk Moderate (easy to delete wrong folder) Zero (strict rules & hashes)
Safety Undo Rollback None (Shift+Del is permanent) 7-Day Automatic Rollback
Time Required 10–20 minutes per app < 60 seconds across 40+ areas

Related Windows Cleanup Guides & Hidden Space Hogs

Clean User Application CrashDumps (%LocalAppData%\CrashDumps) Automatically

SWEEPR Cleaner safely clears User Application CrashDumps (%LocalAppData%\CrashDumps) along with 40+ other hidden app folders and leftover files in one click—covering up to 5 devices (Windows, Mac, Android & iOS) with a 7-day undo safety net.

🛡️ Windows 10/11 First-Launch Walkthrough: Because v0.1.0 is a freshly compiled 5 MB native Rust app, if Windows SmartScreen appears: Step 1: Click "More info" → Step 2: Click "Run anyway".