Connector/Remote Repository

x64dbg.portable 20250819.1940.0

An open-source binary debugger for Windows, aimed at malware analysis and reverse engineering of executables you do not have the source code for.

This package appears to have a custom/proprietary license agreement, and ProGet cannot be automatically determine the license type. You'll need to assign a license type to the URL to allow or block packages with this license.

Usage Instructions

To install x64dbg.portable from the command line, run the following command:

choco install x64dbg.portable --version 20250819.1940.0 --source http://choco.csdesiles.qc.ca/nuget/ChocoCSI/

Description

An open-source binary debugger for Windows, aimed at malware analysis and reverse engineering of executables you do not have the source code for. There are many features available and a comprehensive [plugin system](https://plugins.x64dbg.com/) to add your own. You can find more information on the [blog](https://x64dbg.com/blog)! ## Features * Open-source * Intuitive and familiar, yet new user interface * C-like expression parser * Full-featured debugging of DLL and EXE files (TitanEngine) * IDA-like sidebar with jump arrows * IDA-like instruction token highlighter (highlight registers, etc.) * Memory map * Symbol view * Thread view * Source code view * Content-sensitive register view * Fully customizable color scheme * Dynamically recognize modules and strings * Import reconstructor integrated (Scylla) * Fast disassembler (Capstone) * User database (JSON) for comments, labels, bookmarks, etc. * Plugin support with growing API * Extendable, debuggable scripting language for automation * Multi-datatype memory dump * Basic debug symbol (PDB) support * Dynamic stack view * Built-in assembler (XEDParse/Keystone/asmjit) * Executable patching * Yara Pattern Matching * Decompiler (Snowman) * Analysis ## Notes * This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s), to let the know the package is no longer updating, using: * The 'Contact Maintainers' link on the package page, or * The 'Package Source' link on the package page and raising an issue.