MT5 5.00 Build 6180 Command-Line Backtesting Error: "The procedure entry point WorldTransform could not be located in the dynamic link library"

New comment
 
Subject: MT5 5.00 Build 6180 Command-Line Backtesting Error: "The procedure entry point WorldTransform could not be located in the dynamic link library"


How to fix this bug????



Issue Summary:
When attempting to backtest via command line,  terminal64.exe  crashes immediately upon startup with exit code 0xC0000139 ( STATUS_ENTRYPOINT_NOT_FOUND  - The procedure entry point could not be located in the dynamic link library).



Specific Symptoms:
  • Launching  C:\Program Files\MetaTrader 5\terminal64.exe  via command line results in a crash within 0.1 to 37 seconds.
  • Exit code: 3221225785 (Decimal) = 0xC0000139 (Hex).
  • No logs are generated (no new files in the  logs  directory), indicating the crash occurs during early process initialization, before the main application logic loads.
  • Unable to run the Strategy Tester.
Troubleshooting Steps Attempted (In Order):
  1. Version Switching: Tested builds 6180, 5833, and 5200. All crashed identically. MT5 forces an auto-update back to build 6180.
  2. Portable Mode: Tested with and without the  /portable  flag. Both result in crashes.
  3. Config Encoding: Changed  .ini / .set  file encoding to UTF-16 (matching previous successful configurations). No effect.
  4. Registry Cleanup: Removed  WIN8RTM  compatibility flags from  AppCompatFlags\Layers . No effect.
  5. Account Data Check: Verified account data exists (confirmed). Not an account issue.
  6. DLL Hijacking Check: No private DLLs found in the MT5 directory;  PATH  environment variable is clean. Ruled out.
  7. Global Injection Check: Checked  AppInit_DLLs  and IFEO (Image File Execution Options). Both are empty. Ruled out.
  8. Static PE Analysis: Analyzed the import table of  terminal64.exe . All statically imported functions from  GDI32.dll ,  gdiplus.dll , etc., exist on the current system. No missing dependencies found.
  9. Crash Dump Configuration: Configured  LocalDumps  to capture crash dumps. The crash occurs too early; WER (Windows Error Reporting) fails to generate even a minidump.
  10. Digital Signature Verification: Official MetaQuotes signature is valid.
  11. Launch Method Comparison: Found a critical discrepancy:
    • Launching via  subprocess  (Python/bash) -> Always crashes.
    • Launching via  Start-Process  (PowerShell) -> Survived once, but subsequent identical tests crashed again (intermittent).
Core Contradiction (Critical for Official Support):
On the same machine, with the same executable, and using the same launch method, the results are unstable:
  • One instance of  Start-Process  (no arguments) allowed the process to survive for 5 seconds.
  • Immediately repeating the exact same operation resulted in consistent crashes with error 0xC0000139.

💡 Additional Note for Your Report

Based on your previous screenshot showing the garbled character "酃WorldTransform", you might want to add this specific observation to the report, as it strongly suggests a binary corruption or encoding mismatch in the specific build installed on your machine, rather than a missing system DLL.
Suggested addition to the report:
Observation: The error dialog displays a garbled character prefix (e.g., "酃WorldTransform") before the function name. This suggests potential binary corruption in the installed  terminal64.exe  or a locale/encoding mismatch during the auto-update process, rather than a genuine missing system API.
 
Update: After upgrading to Build 6182, the issue persists. However, the symptoms are now more stable and clearly defined.

Core Facts

terminal64.exe  (Build 6182, upgraded today at 08:34) crashes immediately whenever the Strategy Tester is triggered.
  • Exit Code:  0xC0000139  ( STATUS_ENTRYPOINT_NOT_FOUND ).
  • Logging: No logs are written (the crash occurs during early initialization, before the logging system starts).

Decisive Comparison (Same EXE, Different Launch Methods)

Launch Method Result
Double-click /  Start-Process  (no arguments) ✅ Normal startup, normal login
With  /portable  argument ✅ Normal startup
With  /config:xxx.ini  (containing  [Tester]  section, i.e., running backtest) ❌ Crash  0xC0000139
Python / Command Line direct launch ❌ Crash  0xC0000139

Conclusion

This is not a version issue (both builds 6180 and 6182 crash) and not an account issue (GUI login works fine).
The root cause is specifically the "Strategy Tester Engine Initialization" step crashing in this specific environment.

Environment Context

  • OS: Windows 11 Build 26200 (64-bit)
  • Environment: Remote / Virtualized environment (Virtual GPU)
  • History: Previously tested builds 5833, 5200, 6180, and 6182 — all exhibit the same crash behavior.
New comment