Windows Registry Path for Application Crash Dumps

This article outlines the specific Windows Registry location used to configure system-wide application crash dumps and their retention settings. By modifying these registry values, administrators can enable local user-mode crash dumps, specify the retention directory, and control the maximum number of dump files preserved on the system.

The Registry Path

The configuration for system-wide user-mode application crash dumps is located in the following Windows Error Reporting (WER) registry path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps

If the LocalDumps key does not exist under Windows Error Reporting, you must create it manually to enable local crash dump collection.

Configuring Dump Retention and Storage

Under the LocalDumps key, several values control the retention path, dump count, and dump fidelity:

• DumpFolder (REG_EXPAND_SZ or REG_SZ): Sets the directory where application crash dump files are stored. The default path is %LOCALAPPDATA%\CrashDumps.
• DumpCount (REG_DWORD): Defines the maximum number of crash dump files retained in the designated DumpFolder. The default value is 10. Once this threshold is reached, Windows automatically deletes the oldest dump file when a new crash occurs.
• DumpType (REG_DWORD): Determines the level of detail collected in the dump file:
  • 0: Custom dump.
  • 1: Mini dump (smaller file, limited triage data).
  • 2: Full dump (complete memory capture of the crashing process).
• CustomDumpFlags (REG_DWORD): Specifies custom dump options when DumpType is set to 0.

Per-Application Overrides

To apply different retention paths or limits to a specific executable rather than system-wide, create a subkey beneath LocalDumps using the application’s executable name (for example, LocalDumps\appname.exe). Any values configured inside this subkey will override the global settings for that specific process.