Safe launch — installing your first EA without live-account risk
Installing an Expert Advisor takes 3 clicks in MT5. Running it safely takes a professional protocol. This lesson gives you both: the mechanical steps that get the EA running, and the demo-first validation sequence that separates professional EA operators from gamblers.
Last reviewed:
The 60-second version
Installation is mechanical. Safety is professional. The 48-hour demo validation catches every category of silent error that destroys live accounts before any money is at risk.
- MT5 stores EAs as .ex5 files — compiled, non-editable, ready to run; place them in File → Open Data Folder → MQL5 → Experts
- After file placement, always Refresh the Navigator before trying to attach — MT5 does not auto-scan on a timer
- The EA dialog has two tabs that matter: Inputs (your parameters) and Common (Allow Automated Trading toggle — must be enabled)
- The Expert Journal is your first-48-hours oracle: if it logs nothing after the EA attaches, the EA is not processing ticks
- FundedNext built a real-time monitoring dashboard in 2024 to track EA launches on funded accounts — because the first 48 hours reveal more than any backtest
FundedNext's decision to build real-time EA launch monitoring was driven by a single observation: funded traders who lost their accounts in the first week almost always made the same error — live account, wrong inputs, no demo validation.
FundedNext launched a live monitoring dashboard in 2024 showing funded traders their EA's equity curve, daily drawdown, trade count, and win rate in real time — reducing the support-ticket volume on 'why was my account breached' by 40%.
SourceInstallation wizard — 5 steps
Work through each step in order. Mark each step complete as you finish it. All five steps must be completed before you move to a live account.
The installation and validation protocol
The installation sequence — 5 steps, in order
An Expert Advisor is distributed as a compiled .ex5 file — the output of the MQL5 compiler in MetaEditor. The .ex5 format is binary: you cannot read or edit it without the source .mq5 file. When you download an EA from a marketplace, a developer, or the built-in MetaTrader library, you receive this .ex5 file. Getting it from a file on your computer into a running state on a live chart takes exactly five steps, each of which has a common failure mode.
Step 1: Copy the .ex5 file into the correct folder. MT5 looks for EAs in a specific directory: File → Open Data Folder, then navigate to MQL5 → Experts. Any .ex5 file placed here is available to MT5. If you place the file elsewhere — on the Desktop, in Downloads, in any other subfolder — MT5 will not find it. Subfolders inside Experts work fine for organisation; the critical requirement is that the file is within the Experts directory tree.
Step 2: Refresh or recompile via the Navigator panel. Open the Navigator (Ctrl+N) and look under Expert Advisors. If you just placed the .ex5 file in the Experts folder while MT5 was already running, right-click anywhere in the Navigator and select Refresh. The EA name will appear. If the EA came with an .mq5 source file, you can instead open it in MetaEditor (F4), compile it (F7), and return to MT5 — the compiled output automatically appears in Navigator.
Step 3: Attach to a chart. Drag the EA from the Navigator onto a chart of the correct symbol and timeframe. A dialog opens. This dialog has three tabs: Common, Inputs, and Dependencies. On the Common tab, you will find the 'Allow Automated Trading' checkbox — it must be enabled. On the Inputs tab, you configure every parameter the EA exposes: lot size, stop-loss distance, risk percentage, indicator periods, session filters. Take time here. A misconfigured input is the most common cause of unexpected live behaviour.
Step 4: Verify the first log entry. Immediately after attaching the EA, open the Terminal (Ctrl+T) and click the Experts tab. Within one incoming tick, a well-coded EA should write its first log entry — typically something like 'EA initialised' or the parameter values it loaded. If after 60 seconds you see nothing, the EA is either not logging (a code quality issue) or not receiving ticks (a data feed issue from Lesson 2's Layer 1). Either way, this is the moment to diagnose — not after you have deployed to a live account.
Step 5: Switch to demo first. Before any live capital, the EA must run on a demo account — an environment that mirrors live market conditions but uses simulated balance. The demo account provides real tick data, real spreads, real broker execution logic, and real slippage. What it eliminates is real financial loss. This is where the professional protocol begins.
Demo-first protocol — why 48 hours before going live
The 48-hour demo validation is not a ceremonial step. It is a structured observation period designed to catch the categories of error that backtests cannot detect: misconfigured inputs, unexpected trade frequency, lot sizes deviating from the configured risk percentage, time-filter behaviour during session boundaries, and broker-specific execution quirks.
What a 48-hour demo run reveals: First, trade frequency. If your EA is expected to trade 2–3 times per week and it opens 40 trades in the first day, you have a misconfigured input — likely a lot size or signal sensitivity parameter. Second, lot size consistency. Open the Terminal → Trade History and verify that every trade opened with the lot size you configured. Unexpected lot sizes indicate an error in the EA's position-sizing calculation. Third, Expert Journal entries. A professionally coded EA logs every significant decision: when it evaluates a signal and rejects it, when it opens a trade and why, when a risk gate blocks a trade. Scan these entries for error messages, unexpected states, or suspiciously long silences. Fourth, slippage baseline. In demo conditions, slippage is minimal or zero. Record the average difference between intended entry price and actual fill price. This becomes your live-trading benchmark: if live slippage consistently exceeds the demo baseline by more than 2–3 pips, your broker is a Layer 4 problem (see Lesson 2).
The 48-hour window specifically is chosen because it spans at least two London/New York session overlaps and one Asian session — the three liquidity environments your EA will encounter in live trading. A session-boundary filter or news blackout that appears correct in backtest may produce unexpected trade blocks or unexpected openings when it encounters a real economic calendar event for the first time.
Red flags in the first 48 hours
Most installation failures are detectable within the first few hours. Train yourself to recognise these specific red flags immediately.
No Expert Journal entries: The EA attaches to the chart and nothing appears in Terminal → Experts. This is not normal. It means either the EA was written without any logging (a quality deficiency that makes it undiagnosable) or the EA failed to initialise — check the Journal tab for an initialisation error. Remove the EA, verify the input parameters, and re-attach.
Unexpected trades opening: The EA opens positions you did not expect — wrong direction, wrong symbol, or at times when the strategy should be inactive. In almost all cases this points to an input misconfiguration. Compare the parameters in the EA Inputs panel against the EA's documentation. Check whether a directional filter (trade only longs, trade only shorts) has been toggled incorrectly.
Lot sizes deviating from configured risk: You set risk to 1% per trade with a $10,000 demo balance, expecting approximately 0.10 lot per trade. Instead, you see 0.50 lot positions opening. This is a critical red flag — it means the EA's risk calculation is either broken or the stop-loss distance input is set to near-zero, making the calculated lot astronomically large. Do not proceed to live until this is resolved.
Error messages in the Experts tab: Any line beginning with 'Error' or 'order send failed' in the Expert Journal must be investigated before going live. Common causes include attempting to trade a symbol the broker requires minimum margin for, attempting to open outside broker trading hours, or a volume below the broker's minimum lot size. These will also cause failures on live accounts.
Key terms
A story from 2024
FundedNext's 2024 EA monitoring dashboard was built in direct response to a pattern their support team kept seeing: funded traders losing their accounts in the first week, almost always because they had skipped demo validation and deployed an incorrectly configured EA directly to a funded live account.
FundedNext launched a live monitoring dashboard in 2024 showing funded traders their EA's equity curve, daily drawdown, trade count, and win rate in real time — reducing the support-ticket volume on 'why was my account breached' by 40%.
The dashboard showed funded traders their EA's equity curve, daily drawdown, trade count, and win rate in real time from the first trade. The unexpected effect: traders who could see these metrics live were 40% less likely to contact support with 'I don't know why my account was breached' — because the dashboard made the answer visible. The EA was trading too frequently, or with lot sizes that exceeded the funded account's drawdown limit, or at times the strategy was never designed to trade. Every one of these errors would have been caught in a 48-hour demo run. The monitoring dashboard was a proxy for a validation protocol most traders had skipped.
SourcePractice: install the MACD Sample EA
Install the MACD Sample EA on a demo chart
MT5 ships with a built-in EA called 'MACD Sample' — a simple moving-average crossover with MACD confirmation. It is already compiled and available in your Navigator. You are going to install it using the full professional protocol. Do not skip steps.
- 1
Open MT5 on a demo account (File → Open an Account if you do not have one yet). Open Market Watch (Ctrl+M) and confirm EURUSD is showing live bid/ask prices. Open a chart: right-click EURUSD → Chart Window. Set the timeframe to H1.
- 2
Open the Navigator (Ctrl+N) and expand 'Expert Advisors.' You should see 'MACD Sample' listed. If not, right-click → Refresh. The entry MACD Sample should appear. Note: it has an icon with a small cog — that is the compiled .ex5 indicator.
- 3
Drag MACD Sample from the Navigator onto the EURUSD H1 chart. The EA dialog opens. Click the 'Common' tab. Verify 'Allow Automated Trading' is checked. Also verify 'Allow DLL Imports' is checked if prompted. Do not change any other settings on this tab.
- 4
Click the 'Inputs' tab. You will see parameters like 'Lots' (lot size), 'TakeProfit', 'TrailingStop', 'MACDOpenLevel', 'MACDCloseLevel', 'MATrendPeriod'. Set Lots to 0.01 (minimum lot size — smallest possible position). Leave all other parameters at defaults. Click OK.
- 5
Open Terminal (Ctrl+T) → Experts tab. Wait up to 60 seconds. You should see a log entry from MACD Sample. Typical entry: 'MACD Sample loaded successfully' or similar. The presence of any log entry confirms the EA is active and processing ticks. If nothing appears after 2 minutes, remove the EA and check that 'Allow Automated Trading' is enabled in Tools → Options → Expert Advisors.
Mastery check
Four questions. Pass at 75% (3/4). Each question tests a core installation or validation concept.
Mastery check — Lesson 5
Test your understanding with 4 questions. Pass with 75/4 correct.
Reflect
Reflection
Type your honest answers — saved on this device only. Use them next week to spot patterns in your trading thinking.
Pro deep dive
The 5-step installation sequence and 48-hour demo protocol are the craft minimum. Professional EA operators running multiple EAs at scale add several layers on top.
VPS deployment for always-on EA operation
Running an EA on a home computer creates a silent risk: the EA stops trading every time the computer sleeps, restarts, or loses internet connection. For daily or weekly timeframe trend EAs, a missed session is an annoyance. For scalpers or news-reaction EAs, a missed session can mean a missed stop-loss and a gap through a protection level. A VPS (Virtual Private Server) is a cloud-hosted Windows machine that runs 24/7 regardless of your local infrastructure. MT5 runs on the VPS as if it were a local install. Recommended specifications for EA deployment: 2 CPU cores, 4GB RAM, Windows Server 2019, located in the same data centre city as your broker's server. IC Markets recommends NY4 (New York) for US traders and SY3 (Sydney) for Asia-Pacific. Latency from co-located VPS to broker server is typically 1–5ms versus 40–200ms from a home connection. For scalping EAs and anything that depends on precise entry timing, this latency difference is operationally significant.
Silent failures — when the EA stops without telling you
A silent failure is the hardest EA problem to catch: the EA remains attached to the chart, the face icon is still visible, but it has stopped processing ticks. This can happen due to an unhandled MQL5 error that puts the EA in a stopped state without removing it from the chart. The only reliable detection method is active monitoring: (1) check the Expert Journal at least once per day for the last log entry timestamp — if the timestamp is more than 15 minutes old during active market hours, the EA has stopped; (2) set up a trade activity alert in MT5 (Tools → Alerts) to notify when no trade activity has occurred for a defined period; (3) use a monitoring EA (a separate EA whose only job is to verify that the primary EA is logging at defined intervals and alert if it goes silent). Professional shops run dedicated monitoring processes alongside their strategy EAs — the monitoring never trades, it only watches.
EA versioning — managing updates without losing trade history
When an EA developer releases an update, the temptation is to immediately replace the old .ex5 with the new one. This breaks two things: first, the running EA is interrupted mid-position, potentially leaving open trades without a managing process; second, the inputs panel resets to defaults, wiping your configured parameters. Professional EA versioning protocol: (1) do not replace a running EA — wait for it to close all positions or add a position-closure step to your change management; (2) before installing a new version, export your current inputs to a .set file (Inputs panel → Save button); (3) install the new .ex5 file under a different filename (e.g. MyEA_v2.ex5) rather than overwriting; (4) load the saved .set file in the new version's Inputs panel to restore your parameters; (5) verify the new version's parameter list matches the old — new parameters that default to zero or to an unexpected value are a common source of live-version surprises.
Emergency stop procedures — removing an EA from live without losing open positions
The fastest safe way to stop an EA from opening new trades without closing existing positions: click the MT5 toolbar button 'Stop Automated Trading' (the robot icon). This disables all EAs globally but leaves all existing positions open for manual management. For surgical removal of a single EA while leaving all positions open: right-click the chart → Expert Advisors → Remove — the EA detaches but all positions it opened remain managed by MT5's internal order management. Both methods preserve existing positions. What they do not do: place protective stops on positions that were opened without stops. Before any emergency removal, check the Terminal → Trade tab and manually verify each open position has a stop-loss set. If it does not, set one manually before removing the EA. An EA that opens positions without stop-losses is not operating to professional standards — but many do, and understanding how to manage the exposure they leave behind is essential knowledge.
Sources
Show answer
Steps: (1) Copy .ex5 to MT5 Experts folder; (2) Refresh Navigator; (3) Drag onto chart, configure Inputs and enable Allow Automated Trading; (4) Verify first Expert Journal entry; (5) Run 48 hours on demo. The demo validation checks: trade frequency vs expectation, lot size consistency with configured risk, Expert Journal logging and error messages, and slippage baseline vs live deployment.
Educational material only — not investment advice. Trading carries risk of capital loss. Always practice on demo and use a stop-loss. ← Back to Automated Trading