Skip to main content

Prerequisites

Before installing xAnalyzer, ensure you have the following:

Required Software

  • x64dbg debugger (latest version recommended)
  • Windows operating system (Windows 7 or later)
  • Approximately 50MB of disk space for the plugin and API definition files
xAnalyzer requires x64dbg to be installed and working properly. If you don’t have x64dbg installed yet, download it from the official x64dbg releases page before proceeding.

Download xAnalyzer

Get the latest release of xAnalyzer from the official GitHub repository:
1

Visit the releases page

Navigate to xAnalyzer releases and download the latest version
2

Download required files

You’ll need to download:
  • xAnalyzer.dp32 - Plugin for 32-bit debugging
  • xAnalyzer.dp64 - Plugin for 64-bit debugging
  • apis_def.zip - API definition files (essential for analysis)
Both the 32-bit and 64-bit plugin files are typically included in a single release archive. Download the complete package to ensure you have everything you need.

Installation Steps

Follow these steps to install xAnalyzer in your x64dbg environment:
1

Locate x64dbg plugin directories

Find your x64dbg installation directory. The plugin folders are:
x64dbg/
├── x32/
│   └── plugins/     # For 32-bit plugins
└── x64/
    └── plugins/     # For 64-bit plugins
2

Extract API definition files

Extract the contents of apis_def.zip. You should see:
apis_def/
├── headers/         # Header files with enum/flag definitions
├── kernel32.api
├── user32.api
├── shell32.api
└── ... (190+ .api files)
Do not rename the apis_def folder. xAnalyzer expects this exact folder name to locate definition files.
3

Copy plugin files to x64dbg

Copy the files to their respective locations:For 32-bit debugging:
Copy xAnalyzer.dp32 → x64dbg/x32/plugins/
Copy apis_def folder → x64dbg/x32/plugins/apis_def/
For 64-bit debugging:
Copy xAnalyzer.dp64 → x64dbg/x64/plugins/
Copy apis_def folder → x64dbg/x64/plugins/apis_def/
You need to copy the apis_def folder to both plugin directories if you want to use xAnalyzer for both 32-bit and 64-bit debugging.
4

Verify installation

Launch x64dbg and check for the xAnalyzer plugin:
  1. Open x64dbg (either x32dbg.exe or x64dbg.exe)
  2. Look for “Plugins” in the main menu bar
  3. You should see an “xAnalyzer” entry in the menu
  4. The plugin menu should also appear in the context menu of the Disassembly window

Directory Structure

After proper installation, your x64dbg directory should look like this:
x64dbg/
├── x32/
│   └── plugins/
│       ├── xAnalyzer.dp32
│       └── apis_def/
│           ├── headers/
│           │   ├── shell.h.api
│           │   ├── windows.h.api
│           │   └── ...
│           ├── kernel32.api
│           ├── user32.api
│           └── ...
└── x64/
    └── plugins/
        ├── xAnalyzer.dp64
        └── apis_def/
            ├── headers/
            └── ...

Troubleshooting

If you don’t see the xAnalyzer menu entry after installation:
Check the Log tab in x64dbg:
  1. Open x64dbg
  2. Navigate to the Log tab at the bottom
  3. Look for any error messages from xAnalyzer
Common issues:
  • Missing apis_def folder
  • API definition files not found
  • Plugin file corrupted or wrong version
Verify definition files exist:
plugins/apis_def/kernel32.api
plugins/apis_def/user32.api
plugins/apis_def/headers/
If these files are missing, re-extract apis_def.zip and ensure you copy the entire folder.
Check configuration:
  • Open xAnalyzer menu → Options
  • Ensure analysis options are enabled
  • Try manual analysis first (Analyze Selection or Analyze Function)
See the Configuration page for detailed settings.
Ensure correct plugin version:
  • Use xAnalyzer.dp32 in x64dbg/x32/plugins/ for 32-bit
  • Use xAnalyzer.dp64 in x64dbg/x64/plugins/ for 64-bit
Don’t mix the plugin files between architectures.
If you see errors about missing definition files, make sure the apis_def folder is in the correct location and contains the .api files. The plugin will not function properly without these definition files.

Verifying Installation

To confirm xAnalyzer is working correctly:
1

Load a test executable

Open any Windows executable in x64dbg (you can use a simple program like notepad.exe for testing)
2

Attempt manual analysis

  1. In the Disassembly window, select a few instructions
  2. Right-click and look for xAnalyzerAnalyze Selection
  3. Or use the menu: PluginsxAnalyzerAnalyze Selection
3

Check for analysis results

If installation is successful, you should see:
  • Comments added to API function calls
  • Parameter information in the disassembly
  • Function definitions and argument types

Configuration Files

xAnalyzer stores its configuration in:
x64dbg/x32/plugins/xAnalyzer.ini    # For 32-bit
x64dbg/x64/plugins/xAnalyzer.ini    # For 64-bit
These files are created automatically on first run with default settings.
You don’t need to manually create or edit these configuration files. Use the plugin’s built-in options menu to adjust settings.

Updating xAnalyzer

To update to a newer version:
  1. Backup your custom API definitions (if you’ve modified any)
  2. Download the latest release from GitHub
  3. Replace the old plugin files with the new ones
  4. Update the apis_def folder with new definition files
  5. Restart x64dbg
If you’ve customized any API definition files, back them up before updating. The update process will overwrite the apis_def folder contents.

Next Steps

Now that xAnalyzer is installed, you’re ready to start analyzing code:

Quick Start Guide

Jump straight into using xAnalyzer with a hands-on example

Configuration

Customize xAnalyzer settings to match your workflow

Build docs developers (and LLMs) love