Skip to main content
xAnalyzer provides several configuration options to customize the analysis behavior and control how the plugin processes your executable. Access these options through the xAnalyzer menu in x64dbg.

​
Analysis Options

​
auto_analysis
boolean
default:"false"
Automatic AnalysisWhen enabled, xAnalyzer automatically launches a full analysis over the executable code every time it reaches the entry point when loading in the debugger.Impact:
  • Provides OllyDbg-like initial analysis behavior in x64dbg
  • Analysis runs automatically at entry point
  • No manual intervention required to start analysis
  • May increase initial load time for large executables
Use case: Enable this if you want xAnalyzer to analyze every executable automatically upon loading.
​
extended_analysis
boolean
default:"false"
Extended AnalysisForces xAnalyzer to perform an extended analysis over the entire code section of the debugged executable, rather than just the entry point region.
Enabling this option may significantly increase analysis time and resource usage. Large executables may consume substantial RAM depending on the code section size and the amount of extra data added to the static disassembly.
Impact:
  • Analyzes the entire code section instead of just around the entry point
  • Provides more comprehensive API call detection
  • Significantly longer processing time
  • Higher memory consumption
  • More detailed function and loop detection
Use case: Enable for deep analysis of entire executable when you need complete coverage.
​
undef_funtion_analysis
boolean
default:"false"
Analyze Undefined FunctionsEnables generic analysis and argument detection for API calls and functions that are not defined in the API definition files.Analyzes calls such as:
CALL {REGISTER}
CALL {REGISTER + DISPLACEMENT}
CALL {DYNAMIC_POINTER}
Impact:
  • Detects and analyzes undocumented API calls
  • Applies generic argument types to unknown functions
  • Provides partial information for calls not in definition files
  • May produce less accurate type information
Use case: Enable when analyzing executables with custom or uncommon API calls.
​
track_undef_functions
boolean
default:"false"
Track Undefined FunctionsEnables smart tracking of undefined function calls, including indirect calls through registers and pointers.Impact:
  • Tracks function pointers and indirect calls
  • Follows CALL → REGISTER patterns
  • Follows CALL → DYNAMIC_MEMORY → API patterns
  • Improves detection of dynamically resolved functions
Use case: Enable for executables with dynamic API resolution or indirect calling patterns.

​
Display Options

These options control what existing analysis data should be cleared before performing a new analysis.
​
clear_usercomments
boolean
default:"false"
Clear User CommentsRemoves all user-defined comments before analysis.Impact:
  • Clears comments you manually added
  • Prevents conflicts between manual and automatic comments
  • Cannot be undone
This will permanently remove your manual comments. Disable if you want to preserve custom annotations.
​
clear_autocomments
boolean
default:"true"
Clear Auto CommentsRemoves all automatically generated comments from previous analysis runs.Impact:
  • Cleans up old xAnalyzer comments
  • Ensures fresh analysis data
  • Recommended for re-analysis
Use case: Keep enabled to avoid duplicate or stale auto-comments.
​
clear_userlabels
boolean
default:"false"
Clear User LabelsRemoves all user-defined labels before analysis.Impact:
  • Clears labels you manually created
  • Prevents conflicts between manual and automatic labels
  • Cannot be undone
This will permanently remove your manual labels. Disable if you want to preserve custom labels.
​
clear_autolabels
boolean
default:"true"
Clear Auto LabelsRemoves all automatically generated labels from previous analysis runs.Impact:
  • Cleans up old xAnalyzer labels
  • Ensures fresh label data
  • Works seamlessly with map loader plugins like SwissArmyKnife
Use case: Keep enabled to avoid duplicate or stale auto-labels.

​
Configuration File

xAnalyzer stores configuration settings in an INI file located in the x64dbg plugin directory: 
x64dbg/x32/plugins/xAnalyzer.ini  (32-bit)
x64dbg/x64/plugins/xAnalyzer.ini  (64-bit)

​
Example Configuration

[Settings]
auto_analysis=0
extended_analysis=0
undef_funtion_analysis=0
track_undef_functions=0
clear_usercomments=0
clear_autocomments=1
clear_userlabels=0
clear_autolabels=1
Best for: Fast analysis with minimal resource usage
auto_analysis=0
extended_analysis=0
undef_funtion_analysis=0
track_undef_functions=0
clear_autocomments=1
clear_autolabels=1
Best for: Complete analysis of entire executable
auto_analysis=1
extended_analysis=1
undef_funtion_analysis=1
track_undef_functions=1
clear_autocomments=1
clear_autolabels=1
This configuration may take significant time on large executables.
Best for: Working with manually annotated code
auto_analysis=0
extended_analysis=0
clear_usercomments=0
clear_userlabels=0
clear_autocomments=1
clear_autolabels=1
Configuration changes take effect immediately when modified through the xAnalyzer menu. You can also manually edit the INI file, but you’ll need to restart x64dbg for changes to take effect.

Build docs developers (and LLMs) love

Get started for freeTalk to us