Skip to main content

​
Common Issues

This guide covers common problems you might encounter when using xAnalyzer and how to resolve them.

​
Plugin Not Appearing in Menu

If you don’t see xAnalyzer in the Plugins menu after installation:
1

Check the Log tab

Navigate to the Log tab in x64dbg and look for any error messages from xAnalyzer that might provide hints about the issue.
2

Verify installation

Ensure you’ve copied both the plugin file (xAnalyzer.dp32 or xAnalyzer.dp64) and the apis_def folder to the correct x64dbg plugin directories.
3

Check dependencies

Make sure you’re running the latest version of x64dbg and that all required dependencies are present.

​
Analysis Performance Issues

Extended Analysis mode can consume significant time and memory resources, especially on large executables.
If analysis is taking too long or x64dbg becomes unresponsive:
  • Disable Extended Analysis: Turn off the Extended Analysis option in plugin settings if you don’t need to analyze the entire code section
  • Use Targeted Analysis: Instead of analyzing the entire module, use “Analyze Selection” or “Analyze Function” for specific code sections
  • Check System Resources: Monitor RAM usage during analysis - large executables may require substantial memory

​
Multiple Dots in Executable Name

Analysis may fail if the executable being debugged has multiple dots in its filename (e.g., my.app.v2.0.exe).
Solution: Rename the executable to have only one dot before the extension (e.g., my_app_v2_0.exe).

​
Undefined Function Detection

If generic undefined functions are not being analyzed:
  1. Check that Analyze Undefined Functions is enabled in plugin options
  2. Verify that the function is not at the very beginning of a function block (see Known Limitations)
  3. Ensure the call follows a supported pattern

​
API Definition Not Detected

If a specific API call is not being recognized:
1

Check definition files

Look in the apis_def folder to see if the API is defined in the corresponding .api file for that DLL.
2

Verify file format

If the definition exists, ensure it follows the correct INI structure with all required keys (ParamCount, argument definitions, etc.).
3

Add missing definition

If the API is not defined, you can add it yourself. See the API Definition Files guide for the proper format.

​
Incorrect Argument Order

For x64 executables, if you notice arguments are in the wrong order:
  • Ensure you’re using the x64 version of the plugin (xAnalyzer.dp64)
  • Verify that the API definition file has the correct argument order for the x64 calling convention
  • Check that you’re running the latest version of xAnalyzer

​
Loop Detection Issues

Loop detection only works within function boundaries (between function prologs and RET instructions).
If loops are not being detected:
  • Ensure the code is within a recognized function
  • Check that the function doesn’t have a RET instruction in the middle of its code
  • Be aware that non-conditional jumps inside a section may cause incorrect loop detection

​
Nested Call Problems

Nested calls may not work correctly unless:
  1. The inner call is defined in API definition files, OR
  2. The inner undefined call uses no more stack arguments than needed by the outer call

​
Getting Help

Report an Issue

Open an issue on GitHub with detailed information about your problem

Check Existing Issues

Search existing issues to see if your problem has already been reported

​
When Reporting Issues

To help resolve your issue quickly, please provide:
  • xAnalyzer version: Check the About dialog for version information
  • x64dbg version: Ensure you’re running the latest version
  • Other plugins loaded: Try reproducing the issue with only xAnalyzer loaded
  • Steps to reproduce: Clear instructions on how to trigger the issue
  • Error messages: Any relevant log output or error messages
  • Sample: If possible, provide a sample executable that demonstrates the issue

Build docs developers (and LLMs) love

Get started for freeTalk to us