# x64dbg changelog

> x64dbg release notes.

- Vendor: x64dbg
- Category: Developer Tools
- Official site: http://x64dbg.com/
- Tracked by: What's New (https://whatsnew.fyi/product/x64dbg)
- Harvested from: GitHub (x64dbg/x64dbg)
- Entries below: 6 (newest first)

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

## Releases

### 2026.05.27

- Date: 2026-05-27
- Version: 2026.05.27
- Original notes: https://github.com/x64dbg/x64dbg/releases/tag/2026.05.27
- Permalink: https://whatsnew.fyi/product/x64dbg/releases/2026.05.27

- **added** — Add CPUStack for Linux
- **added** — Add module RVA address display mode in CPU
- **added** — Add IMAGE_FILE_LARGE_ADDRESS_AWARE to x32dbg
- **added** — Add PageUp/PageDown selection movement
- **added** — Show hotkeys in toolbar tooltips
- **changed** — Make tests declarative
- **changed** — Move toggle FPU button into menu
- **changed** — Allow passing absolute path to -cf
- **fixed** — Fix r8 modification
- **fixed** — Fix Running label font color for dark theme
- **fixed** — Fix memory fault in trace reader when memory status change
- **fixed** — Fix cross CI windeployqt overwrite

#### May 2026: Small hotfix release

This is a small hotfix release after the April release. It fixes an `r8` register modification issue, a trace reader memory fault, dark theme label coloring, and support for passing an absolute path to `-cf`. It also includes a few small UI, packaging, testing, and experimental Linux debugger updates.

##### 📜 Changelog
- Added CPUStack (Linux) by @3rdit in #3839
- Make tests declarative by @mrexodia in #3837
- Fix cross CI windeployqt overwrite by @mrexodia in #3841
- Fix "Running" label font color for dark theme by @d2k2-git in #3844
- Fix r8 modification (closes #3850)
- Add module RVA address display mode in CPU by @ZehMatt in #3848
- Add IMAGE_FILE_LARGE_ADDRESS_AWARE to x32dbg
- Fix memory fault in trace reader when memory status change by @torusrxxx in #3863
- Move toggle FPU button into menu by @XanderSteyn in #3860
- Add PageUp/PageDown selection movement by @mrexodia in #3842
- Show hotkeys in toolbar tooltips (#3864)
- Allow passing absolute path to -cf #3865

Full commit history: [`2026.04.20...2026.05.27`](https://github.com/x64dbg/x64dbg/compare/2026.04.20...2026.05.27)

### 2026.04.20

- Date: 2026-04-20
- Version: 2026.04.20
- Original notes: https://github.com/x64dbg/x64dbg/releases/tag/2026.04.20
- Permalink: https://whatsnew.fyi/product/x64dbg/releases/2026.04.20

- **added** — Accessibility support for Registers, Disassembly, Hex Dump, Trace Browser and table-based views with screen reader compatibility
- **added** — Pattern finding usability and performance improvements
- **added** — Breakpoint expression validation in dialog with real-time feedback
- **added** — Direct editing of raw bytes in registers
- **added** — Save graph images as PDF
- **added** — Highlight call stack by module or symbol
- **added** — Bulk toggling of software breakpoints on selected instructions
- **added** — Cycling hotkeys for dump view modes
- **added** — Faster filtering in search lists
- **added** — New test framework for reliability testing
- **added** — Expanded memory breakpoint coverage
- **added** — Pre-alpha Linux debugger based on ElfBug engine with AppImage build
- **changed** — Improved table behavior for accessibility
- **changed** — Clearer naming around trace coverage options
- **changed** — Improved trace parsing robustness
- **changed** — Improved tracing performance
- **fixed** — Crashes with files larger than 2GB
- **fixed** — Loading DLLs without an entrypoint
- **fixed** — Loading modules when file path is stale or file is locked
- **fixed** — Fatal GUI exception when pressing Ctrl+A in search boxes

#### April 2026: Bug fixes, workflow polish, and initial accessibility support

This release focuses mostly on bug fixes, workflow polish, and groundwork for future stability. The most visible addition is initial accessibility support across several core views, alongside a number of smaller improvements that should make day-to-day debugging smoother.

##### 🤖 Automation
**❗ If you are experimenting with agent-assisted reverse engineering, you might want to check out [x64dbg-skills](https://github.com/dariushoule/x64dbg-skills) by @darbonzo. It is built on top of x64dbg Automate MCP, and the accompanying [cookbook post](https://x64.ooo/posts/2026-02-12-cooking-with-x64dbg-and-mcp/) walks through practical reverse engineering workflows.**

This is not part of x64dbg itself, but it is a nice example of the kind of tooling that is starting to form around automation and scripting. The `headless` executable has been fleshed out a bit more as well, mostly to support testing.

##### ✨ Everyday improvements
A lot of the work in this release shows up as small improvements in places you use all the time.

Pattern finding got a usability/performance pass, making it easier to work with. Breakpoint expressions now validate directly in the dialog with clear red and green feedback, which should make it much easier to catch mistakes before saving a condition. You can also edit the raw bytes of a register directly, save graph images as PDF, and highlight the call stack by module or symbol.

There are also a number of smaller quality-of-life improvements: bulk toggling software breakpoints on selected instructions, cycling hotkeys for dump view modes, copy shortcuts in more places, faster filtering in search lists, and clearer naming around trace coverage options.

This release also fixes several frustrating issues that could get in the way of normal debugging work, including crashes with files larger than 2GB, loading DLLs without an entrypoint, loading modules when the file path is stale or the file is locked, and a fatal GUI exception when pressing Ctrl+A in search boxes.

![](https://github.com/user-attachments/assets/153b1bf8-bebd-4b43-8866-e5f74fe0f240)

![](https://github.com/user-attachments/assets/945fff35-af86-4711-9bb4-c3ca9fd56a45)

##### ♿ Accessibility support
This release introduces the first accessibility support in x64dbg. Registers, Disassembly, Hex Dump, Trace Browser and most table-based views now expose accessibility information that can be used by screen readers and other assistive or UI automation tools.

There are also a number of supporting fixes in this area, including additional accessibility names, improved table behavior, and follow-up fixes for the new registers view. This is still only a first step, but it lays the groundwork for using x64dbg in environments where accessibility APIs matter.

##### 🧪 Reliability and testing
Much of the less visible work in this release went into reducing regressions.

A new test framework has been added and memory breakpoint coverage was expanded significantly. There were also many fixes around testing lifecycle issues, headless behavior, tracing, and scripting edge cases. This kind of work is not flashy, but it should help catch problems earlier and make snapshots more trustworthy over time.

A few other fixes in this area are worth calling out too: tracing performance was improved, trace parsing became more robust, patch import undo was fixed, and several issues around command line handling, elevation, and general UI behavior were cleaned up.

##### 🐧 A small Linux experiment
Thanks entirely to @3rdit, the first pre-alpha pieces of a Linux debugger based on the new `ElfBug` engine have been merged, together with an AppImage build for the `cross/debugger` project.

The point of this work is not to ship a polished Linux port. Instead it gives us a proving ground for the cross-platform widget library that is slowly taking shape, and @3rdit is a

_[Truncated at 4000 characters — full notes: https://github.com/x64dbg/x64dbg/releases/tag/2026.04.20]_

### 2025.08.19

- Date: 2025-08-19
- Version: 2025.08.19
- Original notes: https://github.com/x64dbg/x64dbg/releases/tag/2025.08.19
- Permalink: https://whatsnew.fyi/product/x64dbg/releases/2025.08.19

- **fixed** — Systems with older versions of the Visual C++ Redistributable would crash when starting debugging
- **fixed** — Pattern finding was completely broken
- **fixed** — Systems with AVX-512 would crash when using x32dbg
- **fixed** — CPUs with AVX support would always show 0 for XMM registers
- **added** — Support for AddressSanitizer to help prevent memory safety issues
- **changed** — Documentation moved to the docs folder in the x64dbg repository
- **added** — Support to search for intermodular calls in trace recordings
- **added** — Ability to specify a script to execute on debuggee startup with the -cf command line option
- **changed** — Scripting system rewritten from scratch to execute all script commands on an event loop for deterministic execution order

#### August 2025: Bug fixes and stability

This release has mostly been focused on fixing bugs and improving stability over the long term.

##### 🐛 Bugs

The migration to Visual Studio 2022 unfortunately caused some serious issues to slip through. The following bugs were fixed:

- Systems with older versions of the [Visual C++ Redistributable](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170) would crash when you started debugging.
- Pattern finding was completely broken.
- Systems with AVX-512 would crash when using x32dbg.
- CPUs AVX support would always show 0 for XMM registers (thanks to @CXVUSER).

To prevent critical issues like this from slipping through we are working on an automated test system. The _headless_ version of x64dbg introduced in the previous release was a first step in this direction, but much more work is required. This release also introduced support for [AddressSanitizer](https://learn.microsoft.com/en-us/cpp/sanitizers/asan), which helps prevent memory safety issues.

##### ❓ Documentation

The [documentation](https://help.x64dbg.com) has now been moved to the `docs` folder in the x64dbg repository. This streamlines development, but also makes the project much more LLM-friendly. Practically-speaking this means you can now ask questions about x64dbg in [DeepWiki](https://deepwiki.com/x64dbg/x64dbg) and expect reasonably-useful results!

[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/x64dbg/x64dbg)

Some example questions:

- [Can I log the call stack while tracing?](https://deepwiki.com/search/is-there-any-way-to-access-the_bfa81d28-091b-4d93-84e7-a1e8a89830d2)
- [Can I get a list of available commands?](https://deepwiki.com/search/give-me-a-list-of-available-co_5316fb4e-b0a9-4984-8ea9-819194c7c247)
- [How to set a conditional breakpoint on an RVA?](https://deepwiki.com/search/relevantcontextthis-query-was_08df641e-ec87-49e9-b73b-facb193f5bc3)
- [How to automate patching steps?](https://deepwiki.com/search/how-to-automate-the-following_18ec3f69-358f-4b9d-bfef-8df43b93e506)

Obviously this is no replacement for reading the documentation, but it might at least point you to some concepts to research!

##### 🔎 Tracing

There have been quite a lot of updates to the [trace recording](https://help.x64dbg.com/en/latest/introduction/ConditionalTracing.html) feature over the past few months by @torusrxxx. For those not familiar, trace recording allows you to capture the registers and memory accesses for every step of the program. Think [Time Travel Debugging](https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/time-travel-debugging-record), but on a much smaller scale. This feature can be helpful trying to understand the data flow or figuring out where a specific value first pops up when executing a function.

To start a trace recording, use _Help -> Trace into..._ and then enable the _Record trace_ checkbox:

![](https://github.com/user-attachments/assets/aa71daa4-b8bd-4673-983f-25ea171f0549)

You can see a reconstruction of the memory/stack (best effort, might be slow on larger traces):

![](https://github.com/user-attachments/assets/a5bda92c-432b-4d64-bd39-80aecfbfc8b3)

This version introduces support to search for intermodular calls in the trace, which can be useful to understand where APIs get called. A blog post with more details will follow!

##### 🤖 Scripting

**❗ You might want to check out [Analysis at Scale with x64dbg Automate](https://x64dbg.com/blog/2025/03/04/analysis-at-scale-with-x64dbg-automate.html), which introduces a Python library to automate x64dbg. There is also an [MCP Server](https://github.com/cycraft-corp/BinaryAnalysisMCPs) built on top of it, which allows LLMs to interact with x64dbg.**

The builtin scripting feature has always been a bit lackluster, but the need for testing automation has pushed things forward. Improved command line handling was intr

_[Truncated at 4000 characters — full notes: https://github.com/x64dbg/x64dbg/releases/tag/2025.08.19]_

### 2025.06.30 — 2025.07.04

- Date: 2025-06-30
- Version: 2025.06.30
- Original notes: https://github.com/x64dbg/x64dbg/releases/tag/2025.06.30
- Permalink: https://whatsnew.fyi/product/x64dbg/releases/2025.06.30

- **added** — Support for bitfields, enums and anonymous types in the type system
- **added** — Interactive type selection that instantly shows how data will look while selecting the type
- **added** — AVX-512 instruction set support for debugging modern applications
- **added** — Half-float (16-bit half-precision floating-point) support in the dump
- **added** — Copy function graph directly to clipboard
- **added** — Copy calling convention arguments from context menu
- **added** — Focus on window feature in handles view to bring target window to foreground
- **added** — Invoke display type action directly from register and stack views
- **added** — Checkboxes and uninstall option in the revamped launcher
- **added** — Headless version of x64dbg for automated testing
- **changed** — Character arrays are now automatically rendered as strings in type display
- **changed** — Struct widget performance improved drastically for browsing nested pointers and large data structures
- **changed** — Build system migrated to Visual Studio 2022 and CMake
- **changed** — Release versioning changed to CalVer (Calendar Versioning) format
- **changed** — Compilation instructions simplified from 13 steps to a single step
- **removed** — Windows XP support
- **deprecated** — Windows 7 and 8.1 now display an unskippable deprecation warning

#### June 2025: Type System and Modernization
We're excited to announce a major new release of x64dbg, the open-source user mode debugger for Windows. For those new to the project, x64dbg is designed to make reverse engineering and malware analysis faster and more intuitive. This release marks a significant step forward, overhauling our core type system and modernizing our entire toolchain to bring you a more powerful and stable debugging experience.

**NOTE**: There were some minor issues that made the 2025.06.30 snapshot unusable (signing issue causing a Windows Defender false positive, AVX-512 support crashed in x32dbg and the VC runtime was not loaded correctly). Because of this that snapshot has been deleted and a fixed one has been put here.

##### ✨ Revamped Type System
In previous versions, analyzing data structures was a tedious, manual process and many features were not supported. This release adds support for bitfields, enums and anonymous types, which allows all types in the Windows SDK to be represented and displayed.

The [ManyTypes](https://github.com/snowsnowsnows/ManyTypes) plugin by @snowsnowsnows (who also drove this revamp) allows you to import C header files and see the results directly in x64dbg. While we plan to streamline this workflow even further in future updates, this is a huge leap in making data inspection easier.

This isn't just about convenience; it's about speed. We've introduced **drastic performance improvements** to the struct widget, so you can now browse deeply nested pointers and large data structures without the lag.

https://github.com/user-attachments/assets/973d101c-5dab-4f66-ac10-fc68873d52f0

We’ve also added a host of quality-of-life improvements:
- **Interactive type selection**: While selecting the type you will instantly see what the data looks like, enabling a more interactive workflow.
- **Smarter Displays:** Character arrays are now automatically rendered as strings, saving you an extra step.
- **Better Integration:** You can now invoke the "Display type" action directly from the register and stack views, making it easier than ever to inspect data on the fly.

##### 💻 AVX-512 and Half-Float Support
This release introduces support for the latest CPU instruction sets, ensuring you can analyze even the most modern applications.
- **AVX-512 Support:** You now have the power to debug and analyze code that leverages the AVX-512 instruction set, a critical feature for high-performance computing and complex malware.
- **Half-Float Support:** We've added support for 16-bit half-precision floating-point numbers in the dump, a feature especially useful when reversing graphics applications or machine learning models.

##### ⚡ Small Changes, Big Impact
Sometimes it’s the little things that count. Based on your feedback, we've added several small but mighty workflow enhancements:
- **Copy Graph Image:** You can now copy the function graph directly to your clipboard, making it effortless to share your findings or add visuals to your reports.
- **Copy Calling Convention Arguments:** A new context menu option lets you quickly copy function arguments, streamlining the process of reconstructing code or documenting function calls.
- **Focus on Window in Handles View:** You can now bring a target window to the foreground directly from the handles view, which is incredibly useful for UI-heavy debugging.
- **Revamped Launcher**: The launcher now has checkboxes and an uninstall option.

![image](https://github.com/user-attachments/assets/2557aa1c-d5dc-416d-9825-c17b05ce9f33) ![image](https://github.com/user-attachments/assets/1a556c0b-85ac-49a4-a5a8-307695585297)

##### 🚀 Modern Tooling and a New Release Cycle
We've completed a monumental migration of our entire build system to **Visual Studio 2022 and CMake**. This massive undertaking provides a more stable foundation, makes it easier for new developers to contribute, and accelerates the pace of future improveme

_[Truncated at 4000 characters — full notes: https://github.com/x64dbg/x64dbg/releases/tag/2025.06.30]_

### snapshot — snapshot_2025-03-15_15-57.zip

- Date: 2025-03-15
- Version: snapshot
- Original notes: https://github.com/x64dbg/x64dbg/releases/tag/snapshot
- Permalink: https://whatsnew.fyi/product/x64dbg/releases/snapshot

snapshot

### Bitbucket — Bitbucket files

- Date: 2015-04-12
- Version: Bitbucket
- Original notes: https://github.com/x64dbg/x64dbg/releases/tag/Bitbucket
- Permalink: https://whatsnew.fyi/product/x64dbg/releases/bitbucket

Some old Bitbucket files, you can safely ignore them.