Buying an Expert Advisor is the easy part. Getting it running correctly on MetaTrader 5 the first time — with the right permissions, on the right chart, without silently failing overnight — is where most retail traders lose an evening, or worse, lose money because a misconfigured EA opened trades it should never have opened. This guide walks through every stage of installation where things typically go wrong, with worked examples showing what a mistake costs and how to prevent it, whether you're installing a free script or a paid, verified system like an automated XAUUSD trading EA.

Why MT5 Installation Mistakes Are So Common

MetaTrader 5 is not a plug-and-play consumer app. It's a trading terminal built around a sandboxed file system and a permissions model that assumes you understand what you're authorizing. That's by design — automated trading on live capital needs guardrails. But it also means the platform will let you attach an EA to the wrong chart, save it to the wrong folder, or leave Algo Trading disabled without a clear error explaining why nothing is happening.

Compounding the problem, MT5's folder structure and permission dialogs changed enough from MT4 that traders coming over from the older platform often skip a step out of habit. A file that worked fine dropped anywhere on MT4 can silently do nothing on MT5 if it lands one folder off. Understanding this structural difference is the first real step toward a clean install, worth pairing with a broader look at how EA settings actually govern behavior once the file itself is correctly installed.

Mistake 1: Installing the EA File in the Wrong Location

Every MT5 terminal has its own private "Data Folder," separate from your Windows or macOS file system and from any other MT5 terminal installed for a different broker. EAs (.ex5 files) must sit inside MQL5 > Experts within that specific Data Folder — not in Program Files, not on the desktop, and not inside a different broker's terminal folder.

To find the correct folder, open MT5, go to File, then "Open Data Folder." This opens the exact directory tied to the terminal instance you're looking at. Drop the .ex5 file into MQL5\Experts, then right-click the Navigator panel's Expert Advisors list and choose "Refresh." If the EA still doesn't appear, you likely placed it in the wrong Data Folder — a common outcome when running more than one broker's MT5 terminal side by side, since each maintains a separate folder tree even though the desktop icons look identical.

This single mistake accounts for a large share of "my EA isn't showing up" support requests. The fix takes under a minute once you know where to look, and the official MetaTrader 5 terminal help documentation walks through the folder structure if you want the platform's own reference.

Worked Example: Two Brokers, Two Data Folders

Say you run a demo account with Broker A and a live account with Broker B, each with its own MT5 terminal. You correctly install an EA into Broker A's Data Folder while testing, confirm it runs, then go live with Broker B — and nothing happens, because the .ex5 file never made it into Broker B's separate folder. Traders who assume "installed once, works everywhere" waste real testing time here. Verify the Data Folder path per terminal every time you switch accounts or brokers.

Mistake 2: Never Enabling Algo Trading (Or Enabling It Only Once)

MT5 ships with automated execution disabled by default, both at the terminal level and per chart. You need the global "Algo Trading" button in the top toolbar switched on (it turns green when active), and each chart the EA is attached to needs its own "Allow Algo Trading" checkbox ticked in the EA's Common tab. Missing either one produces the same symptom: the EA appears attached, shows a neutral face icon, but never places a trade.

This gets worse after platform updates or a terminal restart, both of which can silently reset Algo Trading to off. If an EA that was working yesterday suddenly stops trading with no error in the Journal tab, check the global toggle first — before assuming the strategy logic broke. A well-built EA, including a selective one that only looks for a setup roughly once a day on the H4 chart, can also go quiet for entirely normal market reasons, so don't confuse "off" with "no qualifying setup"; the troubleshooting steps for each are covered in our guide to common EA problems and fixes.

Mistake 3: Attaching the EA to the Wrong Symbol, Timeframe, or Chart Type

Every EA is built and tested against a specific market and, usually, a specific timeframe. Attach a strategy designed for a H4 gold chart to a 5-minute EUR/USD chart and you haven't just reduced performance — you've run it entirely outside the conditions it was validated against. MT5 will happily let you do this; there's no built-in warning that the EA wasn't designed for this instrument.

Before attaching any EA, confirm three things: the exact symbol name (including broker-specific suffixes like "XAUUSD.m" or "XAUUSDm," which differ by broker and can cause an EA to silently fail its symbol-matching logic), the timeframe the developer specifies, and whether the strategy expects a standard or custom chart type. If the documentation says H4 XAUUSD, that's the only chart it should run on — not H1, not a "similar" gold CFD symbol, and not a demo symbol with different contract specifications. Reviewing your broker's exact symbol naming and spread structure ahead of time prevents this mismatch before it starts.

Mistake 4: Ignoring DLL, WebRequest, and MQL5 Permission Prompts

Some EAs and signal-copying tools need permission to import DLLs or send WebRequests to a specific URL — for example, to relay a trade alert to Telegram or pull a verification feed. MT5 blocks both by default, requiring you to explicitly whitelist the exact URL under Tools > Options > Expert Advisors, or tick "Allow DLL imports" in the EA's Common tab when attaching it.

Two mistakes happen here in opposite directions. The first is skipping the permission entirely, so the EA errors out or silently drops a feature. The second, far more dangerous, is granting DLL or WebRequest permission to an EA from an unfamiliar source without understanding what that access lets the code do on your machine, since DLL imports can execute code outside MT5's normal sandbox. Only grant that permission to sources you trust, and check the developer's documentation in the official MQL5 reference documentation if you're unsure what a specific import is for. A legitimate, professionally distributed EA states clearly, in writing, exactly which permissions it needs and why — vague or absent explanations are a signal to slow down.

Mistake 5: Running Multiple EAs With Clashing Magic Numbers

A "magic number" is the internal ID an EA stamps on every order it opens, letting it — and you — tell its own trades apart from manual trades or another EA's trades on the same account. If you run two EAs on one account without unique magic numbers, they can end up managing, modifying, or closing each other's positions by mistake.

Before running more than one strategy on a single account, confirm each EA's magic number is unique, and give it a value you'll recognize later. The mechanics of this are covered fully in our dedicated piece on EA magic numbers, and whether to combine strategies on one account at all is addressed in our guide to diversifying across multiple EAs.

Mistake 6: Account Type and Broker Settings That Break EAs Without Warning

MT5 supports both "netting" accounts (where all positions on a symbol combine into one net position) and "hedging" accounts (where you can hold opposing buy and sell positions at once). Many EAs are written with one model in mind, and installing a hedging-designed EA onto a netting account won't necessarily throw an error — it may simply merge positions the developer expected to track separately.

Beyond account type, broker-side settings matter too: minimum stop distances, execution mode, maximum lot sizes, and margin requirements vary by broker and can quietly distort what an EA is trying to do. Before installing any EA for live use, confirm your broker's account type and execution settings match what the developer tested against — the kind of due diligence worth doing for any broker before you connect a live EA.

Worked Example: A Risk-Sizing Mismatch After Installation

Suppose you install a risk-based EA on a $10,000 account configured for 1% risk per trade under a Normal risk mode, expecting roughly $100 at stake per position. If the account's leverage or minimum lot step differs from what you assumed, the EA might round up to the nearest allowed lot size, silently pushing real risk well above what you intended. The table below shows how a lot-step mismatch compounds across three sample trades on the same $10,000 account. This is why checking your broker's lot step and margin requirements is part of installation, not an afterthought, and why understanding risk management principles matters before you ever click "Attach to Chart."

Mistake 7: Skipping Backtests and Demo Verification

It's tempting to install an EA and attach it directly to a funded live account, especially after reading a compelling backtest or a verified live result. Resist that. MT5's Strategy Tester lets you run the EA against historical data before you risk anything, and a demo account lets you confirm the live-market installation — permissions, symbol, timeframe, broker connection — behaves the way the backtest suggested it would.

Backtesting and demo forward testing catch different problems: a backtest confirms the strategy logic behaves as expected across historical price action, while a demo run confirms your specific installation doesn't introduce execution issues the backtest never modeled, like slippage or a permission you forgot to grant. Our walkthrough for backtesting an EA on MT5 covers the Strategy Tester setup, and pairing that with a genuinely verified live track record — not a self-reported screenshot — is worth the extra five minutes. Independent services like Myfxbook connect directly to a live account via read-only investor access, and their verification process documentation explains what "verified" does and doesn't guarantee — the numbers are real, not that future results will repeat them.

Mistake 8: VPS, Connectivity, and Update Mistakes That Undo a Clean Install

An EA installed correctly on your desktop still needs to run continuously to catch setups on higher timeframes — and a desktop that sleeps, updates, or loses internet overnight breaks that continuity just as effectively as a bad install would. This is why most serious EA users move to a VPS (virtual private server) that stays online 24/7 with a stable connection to the broker's server. If you're new to this step, our VPS setup walkthrough covers picking a provider and configuring MT5 to run headless.

Two related mistakes show up constantly on VPS deployments: installing the EA once and never checking back, missing a terminal update that silently reset Algo Trading or a Windows update that rebooted the VPS without MT5 set to auto-launch; and running the VPS in an unintended timezone, which throws off any manual review of trade timing relative to news releases. Set the VPS clock deliberately, confirm MT5 auto-starts after any reboot, and check the terminal weekly even after a clean install.

Mistake 9: Confusing "Installed" With "Verified Working"

An EA can be installed, permissioned correctly, and attached to the right chart, yet still be misconfigured in ways that only show up once real trades start opening. After every install, before scaling up capital, confirm the EA's actual behavior lines up with its stated risk settings: correct lot sizing relative to account equity, a stop-loss or safety mechanism present on open positions, and no unexpected duplicate trades from a leftover second instance of the EA on another chart.

It also helps to know what "acceptable" drawdown — the decline from an equity peak to a subsequent trough — looks like for the strategy before you go live, so a normal losing streak isn't mistaken for a broken install. Our explainer on how drawdown works and what's normal gives you a frame of reference before your first live trade.

Red Flags: When "Installation Help" Is Actually a Scam

Because MT5 installation genuinely trips people up, it's also a favorite entry point for scams — "installation support" that asks for remote desktop access to your trading terminal, unsolicited messages offering to "fix" your EA for a fee, or sellers who guarantee a specific win rate if you let them configure the software for you. None of that is normal. Legitimate EA developers publish clear installation documentation and verified results; they don't need your account password or remote control of your machine to help you enable a checkbox.

The CFTC's guidance on forex fraud and the FTC's overview of common investment scam patterns both flag the same warning signs: pressure to act immediately, guaranteed-return language, and requests for account access outside the platform's own investor-password system. A real EA install never requires your main trading password to be shared with anyone — MT5's investor password exists specifically so third parties can view an account without being able to trade or withdraw from it.

A Pre-Installation Checklist Before You Go Live

Running through a short checklist before every EA install catches most of the mistakes above before they cost you a trading session. Treat it like a pre-flight check: fast, boring, and non-negotiable.

How This Applies to a Selective, Risk-Managed Gold EA

The mistakes above apply to any MT5 Expert Advisor, but they matter even more for a strategy that trades selectively — where a single missed permission or wrong-symbol attachment can mean weeks pass before you notice nothing is happening. A H4 XAUUSD system that targets roughly one qualifying setup a day won't generate an obvious flood of activity that tips you off to a broken install the way a high-frequency scalper might. That makes the checklist above more important: confirm the symbol is exactly right, Algo Trading is on, and the account's risk mode (Conservative, Normal, or Aggressive) is set as you intend, before assuming "quiet" means "working."

It's also worth separating installation correctness from strategy performance. A correctly installed EA with sound, risk-based position sizing and no martingale or grid-style averaging can still have losing trades and periods of drawdown — that's normal, not a sign of a broken install. A clean installation only guarantees the EA is doing what it was built to do, on the market and timeframe it was built for, with the risk controls you selected actually in force. Judging the strategy itself is a separate question, best answered by a genuinely verified, independently tracked live record such as an MQL5 signal or a connected Myfxbook account rather than a screenshot — the kind of background worth reviewing on the about page of any EA before you install it.

Risk Disclosure

Trading foreign exchange and commodities such as gold carries real risk, and automated systems do not remove that risk. Past performance, including verified historical results, does not guarantee future returns. Losses are possible, and you should only trade with capital you can genuinely afford to lose. Nothing in this article is personalized investment or financial advice.

Frequently Asked Questions

Why doesn't my EA show up in the Navigator after I install it?

The most common cause is placing the .ex5 file in the wrong location. Open the specific terminal's Data Folder via File > Open Data Folder, confirm the file sits inside MQL5\Experts, then right-click the Expert Advisors list in the Navigator panel and choose Refresh.

Why does my EA attach to the chart but never place a trade?

Check whether Algo Trading is enabled both globally (the toolbar toggle) and on the specific chart (the "Allow Algo Trading" checkbox in the EA's Common tab when you attach it). Also confirm the EA is on the correct symbol and timeframe — a selective strategy may simply be waiting for a qualifying setup rather than malfunctioning.

Do I need to enable DLL imports for every EA?

No. Most EAs never need DLL access. Only enable it for EAs that explicitly document why they need it, and only from developers you trust, since DLL imports can execute code outside MT5's normal sandbox.

What's the difference between installing on MT4 and MT5?

The folder structures and file extensions differ (.ex4 versus .ex5), and MT5's permissions dialogs for Algo Trading and WebRequest URLs are separate from MT4's. Refer to the platform-specific help documentation from MetaTrader 5 when moving between the two rather than assuming identical steps.

Can two EAs run on the same MT5 account without conflicting?

Yes, as long as each EA uses a unique magic number so they don't manage each other's trades, and you've confirmed your account's margin and lot-size limits can support multiple strategies running simultaneously.

Should I backtest an EA before or after installing it live?

Always before. Use MT5's Strategy Tester to review historical performance, then run the EA on a demo account for at least a few live sessions to confirm the actual installation — permissions, symbol, broker execution — behaves as expected, before funding a live account.

Why did my EA stop trading after a platform update?

Terminal and Windows updates can silently reset the Algo Trading toggle to off, especially on a VPS that reboots automatically. After any update, check the toggle and confirm the terminal auto-launched and reconnected to your broker's server.

Is it safe to give someone remote access to install an EA for me?

Be cautious. Legitimate developers provide written installation instructions; they don't typically need remote control of your trading terminal or your live account password. The CFTC's fraud guidance flags unsolicited "installation help" requesting account access as a common red flag.

What does a "netting" versus "hedging" account mean for installation?

Netting accounts combine all positions on one symbol into a single net position; hedging accounts allow simultaneous opposing positions on the same symbol. Some EAs are built for one model specifically, so confirm your account type matches the developer's documentation before going live.

How do I know if my EA's risk settings installed correctly?

Compare the lot size on your first few live trades against what your intended risk percentage and account equity should produce. A mismatch usually points to a broker-side lot-step or leverage difference the EA rounded around, which is worth confirming with your broker directly.