How to Install and Activate an EA in MT5: AtlasFX TrendGuard

Before you start

You need MT5 desktop, an internet connection, a working demo login and the ZIP linked above. An MT4 file ending in .ex4 will not work in MT5. This installation procedure does not apply to the MT5 mobile apps or web terminal. Use your existing compatible demo account if you have one; this download does not require opening or funding a new broker account.

1. Download and extract the EA

Save the ZIP, right-click it in Windows and choose Extract All. Open the extracted AtlasFX_TrendGuard folder. The main files are:

Do not rename the ZIP to EX5. Extract it first. The package also includes checksums and a software licence; keep the original package for reference.

2. Put the files in the correct MT5 folder

In the MT5 terminal you intend to use, select File → Open Data Folder. Open MQL5, then Experts, and create a folder named AtlasFX_TrendGuard. Copy the EX5 and, optionally, the MQ5 into it:

MT5 data folder
└── MQL5
    └── Experts
        └── AtlasFX_TrendGuard
            ├── AtlasFX_TrendGuard.ex5
            └── AtlasFX_TrendGuard.mq5

Keep Default_Demo.set somewhere easy to find; you will select it with Load later. If you have several MT5 installations, each may have a different data folder. Always open the folder from the correct terminal. MetaQuotes’ folder reference.

3. Make the EA appear in Navigator

Return to MT5 and open View → Navigator. Under Expert Advisors, right-click and select Refresh. Expand the new folder and find AtlasFX_TrendGuard. If it is still missing, restart that terminal and check the file location.

The supplied EX5 is already compiled. Recompilation is optional: open the MQ5 in MetaEditor, press F7, and resolve any compilation errors before using the new binary. This EA uses MT5’s standard trade library and needs no additional indicator installation, DLL imports or WebRequest permission.

4. Run an initial Strategy Tester check

Open View → Strategy Tester and select AtlasFX. Use your broker’s exact EURUSD symbol, including any suffix, and H1. This is a convenient tutorial example, not a validated pair recommendation.

Choose a historical period with available data, keep optimization off, and select Every tick based on real ticks where supported. Load Default_Demo.set in the tester’s Inputs tab. Use visualization to inspect behaviour, then run the test and read its journal. Verify the cost assumptions, including commissions and swaps; a smooth chart or a completed test alone does not prove profitability. Official tester instructions.

The toolbar’s Algo Trading switch controls EAs on account charts. It is not the start button for a historical Strategy Tester run. A short installation check and a full performance evaluation are separate tasks.

5. Attach it to a demo chart

Confirm that the connected account is Demo and that quotes are updating. Open its EURUSD chart and set the displayed timeframe to H1. Drag AtlasFX_TrendGuard from Navigator onto that chart.

Use one AtlasFX instance per symbol in one terminal. Keep this tutorial account free of other EAs and manual positions so that ownership checks and account-wide equity changes are easy to understand. MT5 permits only one EA on an individual chart; attaching another replaces it.

6. Load and review the settings

In the EA properties window, open Inputs, choose Load, and select the extracted Default_Demo.set. Check these values before continuing:

These are release defaults, not optimized profit settings. On a usual five-decimal EURUSD quote, 20 points equals 2 pips. Check your symbol’s convention. A 0.25% sizing input is an estimate before commission, swaps and slippage, not a guaranteed maximum loss. The daily brake does not close positions or guarantee a daily loss cap.

Leave MagicNumber at its default for this single-instance walkthrough. Changing it changes the scope of the stored daily state. Read the complete input table before adding charts or changing the configuration.

7. Enable the two MT5 trading permissions

For the demo-chart run:

1. In the EA’s Common tab, enable Allow Algo Trading or Allow algorithmic trading, depending on the build. Click OK.
2. Enable Algo Trading on MT5’s main toolbar. Its platform-level setting is also available under Tools → Options → Expert Advisors.

Both levels must permit trading. Keep DLL imports and WebRequest disabled for this EA. Keep the platform’s protective options for account/profile changes enabled, and recheck permissions after making such changes. Enabling the global switch also affects other EAs that already have individual permission. MetaQuotes’ permission controls and platform settings.

EnableLiveTrading is a third, AtlasFX-specific guard. Keep it false throughout this guide. On a real account it would have to be true for the EA to submit any trade request, including trailing-stop updates. That explains the switch; it is not a recommendation to deploy this research release with real funds.

The switches are on, but account trading is disabled

The terminal and EA switches do not override account access. An investor login can display account information and run analysis, but cannot trade. If the Journal identifies investor mode, check the intended login for your existing demo account using our platform connection guide. A moving chart or a loaded EA does not confirm trading rights.

If a diagnostic reports ACCOUNT_TRADE_ALLOWED=false, do not treat that value alone as proof of an investor password: MetaQuotes also lists a lost server connection, an archived read-only account and server-disabled trading. ACCOUNT_TRADE_EXPERT=false identifies a separate account-level restriction on automated trading at the server. Match the exact log message to the relevant restriction before changing strategy inputs; increasing risk cannot repair account access. See MetaQuotes’ permission checks and master versus investor access.

8. Confirm that it initialized, then let it wait

Check the chart’s EA label and open View → Toolbox → Experts. Look for AtlasFX’s initialization message and check Journal for connection or order errors. Successful initialization confirms loading, not a profitable strategy or a completed trade.

AtlasFX deliberately skips the current bar when attached. It then evaluates new H1 bars and only enters when its breakout, EMA, ADX, spread, session and other checks agree. No immediate trade is normal. Do not raise risk or remove filters to force activity.

Keep the terminal connected and the computer awake during observation. The EA cannot manage trailing stops while the terminal is offline. Record the broker, symbol, version, inputs, date and any error messages in a demo journal.

MT5 EA loaded but not trading: identify which stage stopped

“Not working” can describe three different events: MT5 cannot find the EA, the EA does not initialize, or a running EA has not submitted an accepted order. Diagnose the stage first. This is a troubleshooting workflow, not a report that this release passed runtime or profitability tests.

1. The EA is missing from Navigator

Open the data folder from the same terminal window you are using, then inspect MQL5/Experts. Check the extracted file’s full name and extension. A ZIP is a container; changing its extension to EX5 does not create an executable. An MQ5 source file also does not become a runnable EX5 until compilation succeeds.

If the EX5 is present, refresh the Expert Advisors branch or restart that terminal. If you have several installations, compare the folder opened by each terminal rather than guessing from a desktop shortcut. The correct file in another terminal’s folder cannot fix this terminal’s Navigator list. See MetaQuotes’ folder reference.

2. The EA appears, but attachment or initialization fails

Capture the exact message and timestamp from the Experts or Journal output when you attach the EA. Save the MT5 build, EA filename/version, symbol including suffix, timeframe and input file alongside that message. Change one relevant setting at a time, then compare the new output with the original. An error disappearing after several unrelated changes does not identify its cause.

Check package dependencies and accepted inputs against the release documentation. AtlasFX TrendGuard’s existing walkthrough states that this package needs no DLL import or WebRequest permission; enabling those permissions is not an installation fix for it. A source file compiling without errors is useful build evidence, but it does not establish correct chart behaviour. MetaQuotes explains the platform logs.

3. The EA initializes, but no trade appears

For a demo-chart run, distinguish permission from a qualifying signal. MT5 has both a platform-wide algorithmic-trading setting and the EA’s own trading permission. Either can block trading. An account switch can also trigger the platform’s protective disable setting. Read the platform settings reference before changing permissions.

AtlasFX also has its own EnableLiveTrading guard. Keep it false for this demo walkthrough. A real-account-lock message is a software restriction, not a reason to enable live operation while solving an installation problem.

If permissions are correct, check whether fresh quotes and a new qualifying H1 bar arrived. Compare the observed server time and spread with the saved session and spread settings. This EA skips the current bar after attachment and waits for its documented conditions. A successful load therefore need not produce an immediate trade. Increasing risk or removing filters would change the experiment rather than explain the original outcome.

4. A trade request is rejected

Record the actual rejection text or numeric result; absence of a filled position alone is not enough to identify an order error. Compare the requested volume and stop levels with the exact symbol’s permitted limits, then check account margin and whether that market is open. If a stop distance or volume must change, recalculate the resulting exposure rather than preserving the old lot size.

MetaQuotes separates volume limits, stop-distance rules and other symbol properties. These constraints are distinct from an EA’s signal rules.

What counts as an installation check?

• Found: the intended EX5 is visible in the intended terminal.
• Initialized: chart attachment completes and the relevant log does not report an initialization failure.
• Behaviour inspected: the observed actions or deliberate skips agree with the documented rules for that particular observation.

None of these establishes profitable trading. A historical evaluation needs its own date range, data, cost assumptions, inputs and results, while demo observation needs an actual recorded period. The toolbar switch is also separate from starting a historical test: use Strategy Tester for that task.

Use the position size calculator to inspect an illustrative plan, or follow the separate indicator installation guide if your file is a chart-analysis tool. A compatible demo account can be used without opening or funding another account.

Troubleshooting

How to stop or remove the EA

Turn off the toolbar’s Algo Trading switch to stop automated trade requests across the terminal, or disable the individual EA’s permission. To remove it, use the running EA’s context menu in Navigator or the chart’s Expert Advisor menu.

Disabling or removing the EA does not close an existing position. It also stops the EA’s protective modifications, including trailing updates. Inspect any open positions separately. Existing broker-side stop-loss and take-profit orders normally remain, subject to the broker’s order rules.

Your next step

Continue the demo evaluation using the AtlasFX testing protocol. Keep a later historical period untouched and compare expected behaviour with actual demo trades. Successful installation is the beginning of evaluation.

Need a compatible platform? Compare broker eligibility, MT5 access and costs before choosing an account. You can also install a chart indicator or browse the EA library. Broker reviews may contain clearly marked affiliate links; a referral can earn us a commission.

Checked 8 September 2026 against the downloadable source and official platform documentation. This is an installation guide, not a claim of tested trading performance.