From afbc00e27e369115356498fec837f7e96f06cc8a Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 4 Sep 2026 02:15:28 +0000 Subject: [PATCH] Clarify that WER LocalDumps registry values are optional The upgrade guide claimed WER stops creating dumps after a few crashes of the same type and that DumpType=0 / DumpCount=0 were needed to disable this. That is not how these values work, and BugSplat does not consume the dumps WER writes: BugSplatMonitor writes its own minidump when WER hands a crash to BugSplatWer.dll. Reword the section to explain that only the RuntimeExceptionHelperModules entry is required, and that the LocalDumps values merely prevent WER from writing a duplicate dump when local dump collection is enabled. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01Hci8qhAhPSkzqFM7eWfKCM --- .../cplusplus/bugsplat-for-windows-upgrade-guide.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/introduction/getting-started/integrations/desktop/cplusplus/bugsplat-for-windows-upgrade-guide.md b/introduction/getting-started/integrations/desktop/cplusplus/bugsplat-for-windows-upgrade-guide.md index 20b89b73..d61b07c5 100644 --- a/introduction/getting-started/integrations/desktop/cplusplus/bugsplat-for-windows-upgrade-guide.md +++ b/introduction/getting-started/integrations/desktop/cplusplus/bugsplat-for-windows-upgrade-guide.md @@ -73,7 +73,11 @@ Here is that value shown highlighted in the registry editor for one of our sampl
-By default, WER will stop creating crash dumps after it has seen a few of the same type. To disable this, create the following registry key: +#### **Optional: Suppressing WER Local Dumps** + +The `LocalDumps` registry values described in this section are **optional**. BugSplat's WER integration works fully with only the `RuntimeExceptionHelperModules` entry above. BugSplat does not read the dump files that WER writes: when WER hands a crash to `BugSplatWer.dll`, `BugSplatMonitor.exe` writes its own minidump directly from the crashed process, using the minidump type configured via `SetMiniDumpType`, and uploads that file. + +If [WER local dump collection](https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps) is enabled on a machine, WER will also write its own copy of each crash dump, typically under `%LOCALAPPDATA%\CrashDumps`. To prevent this duplicate dump for your application, create the following registry key: ``` Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\{Application Name} @@ -81,11 +85,13 @@ Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\L Add the following values under the new key you created: -
Registry Key SettingDescriptionValue
DumpTypeSets the type of dump to create.0
DumpCountSets the maximum number of dumps.0
+
Registry Key SettingDescriptionValue
DumpTypeSets the type of dump WER creates. 0 selects a custom dump controlled by CustomDumpFlags.0
DumpCountSets the maximum number of dump files WER keeps for the application. 0 prevents WER from retaining its own dumps.0
Here's an example of this shown in the registry editor:
-For additional information, see [https://learn.microsoft.com/en-us/windows/win32/wer/wer-settings](https://learn.microsoft.com/en-us/windows/win32/wer/wer-settings) +If local dump collection is not enabled on the machine, omitting this key has no effect on BugSplat. + +For additional information, see [WER Settings](https://learn.microsoft.com/en-us/windows/win32/wer/wer-settings) and [Collecting User-Mode Dumps](https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps).