angusdevgo/IDM_Pro_Tool

English | 简体中文

Feature-Rich Native C# Activation & Lifecycle State Maintenance Toolkit for Internet Download Manager

Key Features • Functional Overview • Core Mechanisms • Quick Start • CLI Support • Verified Versions • Project Structure • License • Disclaimer

• 🚀 Zero External Dependencies · Native Toolchain Execution
  No heavyweight .NET SDK, Visual Studio, or runtime prerequisites required. Compiles within milliseconds using the built-in Windows native C# compiler (csc.exe), producing a standalone executable of approximately 240 KB.
• 🎨 Code-First Modern WPF Interface
  Constructed entirely in pure C# code without any XAML overhead. Integrates native Windows Desktop Window Manager (DWM) immersive dark-mode titlebars and built-in Per-Monitor High-DPI dynamic scaling.
• 🛡️ Byte-Level Preflight Safety Gating
  Validates both structural PE headers and redundant expected byte sequences prior to any modification. Aborts immediately with a zero-byte-written fail-closed guarantee upon any fingerprint or layout mismatch.
• 💾 Version-Aware Atomic Backup & Restoration
  Automatically archives clean original binaries to IDMan.exe.BAK. Inspects embedded version metadata to detect stale backups from past updates, preventing rollback version misalignment.
• ⚡ Multi-Paradigm Activation Strategies
  Consolidates deep binary patching, Windows ACL registry evaluation freezing, and personalized identity registration into a single modular solution.

• 🛡️ Hosts Loopback Shield: Intelligently toggles 127.0.0.1 loopback mappings in the Windows hosts file for 8 primary verification servers (e.g., tonec.com, registeridm.com), severing network-layer telemetry and serial blacklisting.
• ⚙️ Official Update Policy Control: Toggles the CheckUpdtVM registry policy to silence automated update prompts or re-enable them on demand.
• 🧰 Registry & Path Utilities:
  • 📍 Custom IDM Path Resolution: Full support for non-system drives (D:, E:, etc.) and portable installations with automatic polling, interactive file selection dialogs, and persistent configuration memory.
  • One-click navigation to the IDM installation directory.
  • One-click launch and deep-navigation to HKEY_CURRENT_USER\Software\DownloadManager in Windows Registry Editor.
  • Complete one-click registry configuration export to the desktop (IDM_Reg_Backup.reg).
• ⚡ Process Control: Safe single-click termination, execution, and restart of the IDM core process.

[Stock IDMan.exe] ──> [PE Structural Integrity Check] ──> [AOB Dual-State Signature Scan]
                               │
                               ├──> 1. AOB Signature Scan & Patch (15 sites / 31 bytes)
                               ├──> 2. Zero Authenticode Directory & Truncate 10,608-byte Overlay
                               ├──> 3. Standard PE Checksum Recomputation (Microsoft Algorithm)
                               ├──> 4. Pre/Post-Write Dual PE Validation with Atomic Rollback
                               └──> 5. Purge Counterfeit Serial & Register Valid Entitlement

Legacy solutions (v2 and earlier) relied on hardcoded file offsets. Each minor IDM maintenance release involves full re-compilation, inducing non-uniform code relocations (e.g., shifts ranging non-linearly from −896 to +64 bytes between 6.43 build 10 and build 11). Fixed offsets inevitably corrupt executable code sections, triggering fatal Win32 errors such as 0x80004005: The specified executable is not a valid application for this OS platform.

The v3 architecture transitions to an Array of Bytes (AOB) Pattern Signature Scanning Engine:

1. Each patch target defines both Pristine (SigOriginal) and Patched (SigPatched) byte signatures.
2. The engine scans for SigPatched first to ensure seamless idempotency across multiple runs.
3. Signatures require strict unique matching across the entire binary image, coupled with redundant Expected byte checks at the computed relative offset.
4. If any required site fails to match, the engine aborts with zero disk modifications.
5. Signatures are derived from cross-version common invariant regions, filtering out compiler-generated relocation pointers.

Current signatures are validated across five releases: 6.43 build 10, build 11 (6.43.11.2), build 11 (6.43.11.3), build 12 (6.43.12.3), and build 15 (6.43.15.3).
The 14 required sites match uniquely across all five versions.
The 15th site is an optional version-adaptive patch targeting the build 11.3+ anti-piracy behavior (see §0.2); it does not exist in build 10 / 11.2 and is skipped automatically.

When a user updates IDM, an existing IDMan.exe.BAK in the target directory often contains the stock binary of the previous version. Unconditionally reusing this file leads to version skew:

• Rollback snapshots point to an outdated release.
• Restoring the backup overwrites the updated installation with obsolete binaries, creating runtime DLL interface mismatches.

This toolkit enforces a Version-Aware Backup Protocol:

Additionally, the restoration module enforces a Version Consistency Guard, rejecting restore operations if the backup version differs from installed companion components.

Certain anti-piracy branches only exist in specific compiler builds (e.g., defensive checks introduced in newer maintenance revisions). Requiring unanimous matching across all points causes the engine to falsely reject legacy releases.

Version 1.4.0 introduces the AobPoint.Optional flag:

Preflight gating requires that all required sites are satisfied: requiredOk == requiredCount.

Multi-Version Adaptability Matrix:

Observed failure mode: IDM's built-in updater silently replaced the already-activated IDMan.exe with a freshly downloaded stock build 15 binary, resetting the entitlement state back to v6.43b15 Trial (CWE-602 — the privilege decision is enforced entirely client-side).

The v1.4.0 engine correctly refused to write (9 of 15 signatures missed, zero bytes flushed), leaving the user with an unactivated but uncorrupted binary. Extending coverage to build 15 required two non-trivial adaptations:

1. Shrinking common-invariant region — build 15 re-compiled a substantial portion of .text, so the byte region shared verbatim by all five releases contracted. Signatures were regenerated from the five-version intersection, which naturally narrowed them (e.g. 授权分支检测 118 B → 24 B) while every site retained dual-state uniqueness (1/1).
2. Non-uniform padding drift in .data — the trial-flag/day-limit constant block gained two extra zero-padding bytes ahead of the 01 00 00 00 / 1E 00 00 00 pair. Naive sliding-Hamming matching therefore locked onto a near-miss location two bytes early (Hamming distance 2, wrong patch offset 0x379546). The site was re-anchored by exact byte search to 0x379524 and confirmed by capstone disassembly.

Verification discipline applied: every located site was cross-checked by (a) exact expected-byte match, (b) capstone semantic disassembly compared side-by-side against the build 11.3 baseline, and (c) an end-to-end patch whose diff offsets were asserted to fall only within patch sites ∪ PE checksum ∪ security directory.

Remediation guidance for users: disable automatic updates (CheckUpdtVM = 0, written by Mode 1) so a future silent update does not invalidate the entitlement state again.

IDM performs asymmetric cryptographic signature checks on the Serial registry value. Supplying an arbitrary or synthetic serial triggers counterfeit detection alarms.

Registry Layer (Policy Surface):

1. Purge the Serial key to bypass public-key validation routines.
2. Clean telemetry tracking keys: scansk, tvfrdt, radxcnt, ptrk_scdt, LastCheckQU, scTime, NextCheck, BList, md5pks.
3. Populate identity keys: FName, LName, and Email.

⚠️ Key Insight (v1.4.0): Deleting Serial alone is insufficient in build 11.3.
Build 11.3 introduced a defensive check: if the Serial key is absent on launch, IDM immediately forces the registration modal dialog (Dialog Resource ID 138).
Version 1.4.0 adds Site #15 at the binary decision level (je → jmp), forcing execution down the "Serial present and verified" path, establishing a dual-layer defense.

Architectural Principle: Registry keys represent a volatile policy surface subject to vendor modification; binary conditional branches represent the invariant decision surface.

Patching code sections invalidates the official Authenticode digital signature, causing security subsystems to flag the executable as tampered.
This toolkit parses the PE image dynamically:

• Clears VirtualAddress and Size in IMAGE_DIRECTORY_ENTRY_SECURITY (Data Directory index 4).
• Truncates the physical 10,608-byte digital certificate block appended to the file overlay (e.g., resizing build 11.3 from 6,200,176 to exactly 6,189,568 bytes, or build 15.3 from 6,201,712 to exactly 6,191,104 bytes — both matching pe.ImageEnd).
• Recomputes the PE Checksum using the standard Microsoft folding addition algorithm, restoring binary structural compliance.

1. Download the latest archive from the Releases Page.
2. Extract the archive, ensuring app_icon.png resides alongside IDM_Pro_Tool.exe.
3. Right-click IDM_Pro_Tool.exe and select Run as administrator.
4. Select your desired mode from the interface and click execute.

Compiles natively on any modern Windows environment (Windows 10 / 11 includes .NET Framework 4.x out of the box). Clone the repository and run build.bat:

# 1. Clone the repository
git clone https://github.com/angusdevgo/IDM_Pro_Tool.git
cd IDM_Pro_Tool

# 2. Execute the native build script
.\build.bat

Build Details: build.bat invokes %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\csc.exe directly, completing compilation in 1–2 seconds with zero toolchain overhead.

The toolkit features full headless command-line support for automation scripts, unattended deployments, and CI/CD pipelines:

# Execute Mode 1: Rapid Deep Unlock (AOB binary patch + registration)
IDM_Pro_Tool.exe -patch

# Execute Mode 2: Permanent Trial Freeze (Windows ACL evaluation lock)
IDM_Pro_Tool.exe -freeze

# Execute Mode 3: Custom Identity Registration
IDM_Pro_Tool.exe -register "VIP_User" "vip@domain.com"

# Revert to clean stock installation from BAK
IDM_Pro_Tool.exe -restore

# Explicitly configure and persist custom IDM installation path
IDM_Pro_Tool.exe -setpath "D:\Software\Internet Download Manager"

# Display CLI help documentation
IDM_Pro_Tool.exe -help

IDM_Pro_Tool/
├── src/
│   ├── Program.cs          # Unified source (~3000 lines, code-first WPF vector UI & patch engines)
│   ├── app.ico             # Multi-resolution application icon asset (16–256px)
│   ├── app_icon.png        # 256x256 high-resolution vector interface asset
│   └── app.manifest        # Windows UAC execution level & Per-Monitor DPI awareness manifest
├── tests/
│   ├── PatchEngineTests.cs # Automated regression harness (61 assertions across all versions)
│   ├── QuickPatch.cs       # Minimal engine CLI harness for rapid validation
│   ├── build_tests.bat     # Regression harness build script
│   └── build_quick.bat     # Standalone driver build script
├── build.bat               # Native batch compilation and asset assembly script
├── IDM_Pro_Tool.exe        # Compiled x64 Windows GUI application
├── app_icon.png            # Runtime window icon dependency
├── LICENSE                 # GNU General Public License v3.0
├── README.md               # English documentation (Default)
└── README.zh.md            # Simplified Chinese documentation

This toolkit is rigorously tested against official retail distribution binaries:

Note on Historical Hashes: Legacy crack releases (e.g. v20.7) populated the PE checksum field with 0x005F0BEA. Exhaustive algorithmic analysis proves this value corresponds to no valid Microsoft checksum standard. This toolkit writes the mathematically valid standard checksum.

Signature Invariance: AOB patterns are anchored in multi-version invariant byte sequences, naturally immune to relocation noise. The 14 required sites match uniquely across all five tested releases; Site #15 automatically activates on build 11.3+ via the Optional subsystem.

1. This project, including all associated source code and compiled executables, is provided strictly for reverse engineering, Windows operating system internals, PE file structure analysis, and educational security research.
2. Users should delete all downloaded files within 24 hours of testing. Commercial use or unauthorized redistribution is strictly prohibited.
3. If you regularly use Internet Download Manager, please support software developers by purchasing an official license at the Official IDM Website.
4. The author assumes no liability for software conflicts, data loss, or system instability arising from the use of this software.

This project is licensed under the GNU General Public License v3.0 (GPL-3.0).

• ✅ Commercial Use — May be used for any purpose, including commercial endeavors.
• ✅ Modification — Full freedom to inspect, research, and alter source code.
• ✅ Distribution — Freedom to copy, share, and redistribute.
• ✅ Patent Grant — Express patent grant from contributors.

• 📌 Copyleft (Reciprocal License) — Any modified or derivative works must also be released under GPL-3.0 with full source code made available.
• 📌 License and Copyright Notice — Original copyright headers and license text must be preserved in all copies.
• 📌 State Changes — Modified files must carry prominent notices documenting that changes were made.
• 📌 No Additional Restrictions — Downstream distributors may not place terms that restrict freedoms granted by GPL-3.0.

• ⚠️ No Warranty — The software is provided "AS IS", without warranty of any kind, express or implied.
• ⚠️ Research Purpose — Please consult the Disclaimer above; do not use for copyright infringement.

For full terms and conditions, consult the LICENSE file or visit https://www.gnu.org/licenses/gpl-3.0.html.

Issues and Pull Requests are welcome!

• LINUX DO Community: https://linux.do