Can an EX4 or EX5 file be repaired without source code?
Not as a normal source-code repair. Protected or compiled files should not be decompiled. A clean reimplementation requires a separate behavioural specification and authorization.
Free diagnosis guide
A reproducible MQL4 or MQL5 bug report format that helps separate source-code logic, broker constraints and terminal configuration.
Include the MQ4 or MQ5 files and every non-standard include or custom indicator required to compile.
Describe the single highest-priority fault before adding unrelated improvements.
State exactly what the EA, indicator or script should do in the reproducible case.
State what happened instead, including visible values and the time of the event.
List symbol, timeframe, date range, input set and the shortest sequence that triggers the issue.
Include the relevant Experts and Journal lines around the failure, preserving return codes and timestamps.
Provide account mode, digits, filling mode, volume step, stop level and terminal build when execution is involved.
Mark the expected event and actual event without relying on the image as the only specification.
Identify the last known working version and what changed before the issue appeared.
Define the exact check that will prove the agreed repair is complete.
Not as a normal source-code repair. Protected or compiled files should not be decompiled. A clean reimplementation requires a separate behavioural specification and authorization.
Order filling, symbol digits, minimum volume, stop levels and account mode can change whether an otherwise valid trade request is accepted.
Not automatically. A bounded bug fix proves corrected behaviour for the agreed case. Strategy optimization and new features should be scoped separately.
Free diagnostic resource
Mark Compile, Load, Initialize and Runtime in order, then copy a source-safe evidence brief without uploading code or credentials.
Open the free toolReady for a feasibility check?