Announcing Version 7.0.0 of BugSplat for Windows

A simpler and more reliable way to capture Windows and Xbox crashes.

Windows crash reporting has always been a little scattered, with different APIs, different quirks, and plenty of places where crashes disappear without a trace. For 7.0.0, we stepped back and rebuilt our Windows SDK around a clear goal: make crash reporting on Windows and Xbox dramatically simpler and more dependable, especially when things get messy.

This release is the result of a lot good work by our team, and we are excited to put it in your hands. Here is what changed, why it matters, and what you should update in your projects.

⸻

A single unified SDK for Windows and Xbox

The first big improvement is that everything is now one SDK.

We merged BugSplatNative and BugSplatGdk into a unified BugSplat SDK for Windows. This means one integration path, one set of APIs, and one documentation set. No more choosing between SDK flavors or maintaining parallel implementations for desktop and console.

As part of this work, we also:

• Rewrote and expanded the Windows SDK API documentation (link)
• Updated all example applications
• Published a new GitHub repository with sample implementations for several platforms (link)

If you are starting a new project, begin with the unified SDK. If you are using an older SDK, this release simplifies your setup and unlocks the improvements that follow (link).

⸻

Deeper and cleaner integration with Windows Error Reporting (WER)

WER is powerful, but not simple to work with. Our goal was to take the useful parts and make them practical for real developers.

The new BugSplat for Windows SDK can register a WER callback (link), allowing WER to forward crashes directly to BugSplat. For certain crash types, this is not just helpful, it is the only way to capture them reliably.

This includes:

• Heap corruption and heap overwrite crashes
• Fast fail errors
• Crashes that happen very early or very late in the process lifetime
• Scenarios in WinUI 3 where traditional handlers often fail

Configuring WER is straightforward. Run your installer with admin privileges and create a registry key. Our WER configuration guide (link) includes the exact steps.

⸻

Out of process crash reporting and why it matters

Crash handlers should not crash, yet on Windows this can happen more often than you would expect.

To fix this, the Windows SDK now reports crashes out of process. A separate monitor executable captures crash reports even when the main process is unstable. This leads to more reliable reporting, especially during severe or unusual failures.

As part of this update:

• BsSndRpt.exe is now BugSplatMonitor.exe
• Support for x86 platforms has been dropped
• BugSplatRc.dll replaces BugSplatRc64.dll
• We now ship BugSplat.lib and BugSplatSharedMemory.lib instead of BugSplat.dll

If you are upgrading, make sure to:

• Link against the new static libraries
• Ship BugSplatMonitor.exe and BugSplatRc.dll with your application

Overall, this change reduces missing reports and gives teams more consistent insight across development, testing, and production.

⸻

Updated toolchain for modern Windows development

The SDK now builds with MSVC 2022 and targets the v143 build tools. This keeps BugSplat aligned with the current Windows ecosystem and improves long-term compatibility.

⸻

Why this update matters

Beyond the individual features, version 7.0.0 reflects a simple philosophy. Crash reporting should be boringly reliable.

This release gives you:

• More complete crash coverage, including failures that were previously difficult to capture
• A single, simpler integration path across Windows and Xbox
• A more robust crash reporter that continues working even when your application does not
• A modern toolchain built for today’s Windows development practices

If you rely on crash reporting to keep your players happy and your support overhead under control, this is a meaningful upgrade.

⸻

A note from the team

We build BugSplat the same way we build software: small team, tight feedback loops, and a lot of care for the details that matter. Everything in this release, from unified APIs to WER callbacks to out of process reporting, came from conversations with developers who needed clearer and more dependable visibility into their crashes.

If 7.0.0 makes your life easier, we want to hear it.

If anything feels rough or could be better, we want to hear that even more.

You can reach us through:

• The chat in the BugSplat web app
• Email at support@bugsplat.com
• Our Discord community at https://discord.gg/bugsplat

Thanks for using BugSplat and good luck bug hunting!