How to Update MetaTrader 5: A Complete Guide for EA Traders

Why Updates Matter (and Why EA Traders Should Care)

MetaQuotes pushes MT5 updates every few weeks. Most traders hit "Remind me later" and forget about it. That works until your EA stops opening trades one morning because the new build changed something under the hood.

Two real examples:

• Build 5320 (September 2025) was the final MT5 desktop update for Windows 7, 8, 8.1, and Server 2008. Those systems stop receiving future updates — meaning no security patches, no new features, and eventually no broker compatibility.
• Build 5572 (January 2026) changed how ONNX libraries load and added CUDA GPU acceleration. EAs using ONNX models should be retested; recompilation may be needed if the source uses old flags like ONNX_CUDA_DISABLE or you want the new GPU-selection options.

Updates bring genuine improvements — faster backtesting, better charting, new MQL5 features. But they can also break things. This guide covers how to update safely, what to check before and after, and how to roll back if something goes wrong.

Check Your Current Build Number

Before updating, know where you stand.

1. Open MT5
2. Click Help → About
3. Note the build number (e.g., "Build 5800")

You can also see it in the title bar or the Journal tab when MT5 starts — it logs something like Terminal MetaTrader 5 x64 build 5800 started.

Method 1: Automatic Update (Default)

MT5 checks for updates every time it connects to your broker's server. If a new build is available:

1. A popup appears: "A new version is available. Restart to update?"
2. Click Restart — MT5 closes, updates, and reopens automatically
3. Check Help → About to confirm the new build number

That's it. This is how most updates happen, and it works fine for 90% of cases.

If the popup doesn't appear: MT5 checks for updates via the connected trade server, so availability can lag depending on your broker's distribution path. This doesn't mean the broker strictly caps your build version — a newer terminal can usually still connect to an older server — but you may not see the absolute latest build immediately.

Method 2: Manual Update (Run as Administrator)

If automatic update gets stuck or doesn't trigger:

1. Close MT5 completely
2. Right-click the MT5 shortcut → Run as administrator
3. MT5 will detect the newer version and download it automatically
4. Wait for the restart prompt

The "Run as administrator" step matters because MT5 needs write access to its installation folder (usually C:\Program Files\MetaTrader 5\). Without sufficient privileges, Windows may prompt for elevation; if that elevation is blocked or skipped, the update may not complete.

Method 3: Fresh Install Over Existing

If both methods above fail:

1. Download the latest installer from metatrader5.com or your broker's website
2. Run the installer — it detects your existing installation and updates in place
3. Your profiles, chart templates, EA files, and account logins are preserved

Important: Do NOT uninstall MT5 first — or at least, do not enable "Delete user personal data" during uninstall. MT5's uninstaller has an optional checkbox that removes history, MQL5 applications, settings, and other user data. If you skip that option, reinstalling to the same directory restores your previous setup. But the safest path is simply installing over the existing one without uninstalling at all.

The EA Trader's Pre-Update Checklist

This is the part broker help pages skip. Before you update:

1. Back up your MQL5 folder

Use File → Open Data Folder in MT5 to locate your data directory. On modern Windows, it's usually at C:\Users\<you>\AppData\Roaming\MetaQuotes\Terminal\<instance_id>\MQL5\ (not inside Program Files). Copy the entire MQL5 folder. This includes:

• Experts\ — your EA .ex5 and .mq5 files
• Indicators\ — custom indicators
• Profiles\Tester\ — your .set files (optimization settings)
• Files\ — any data files your EAs read/write

2. Note which EAs are running and on which charts

Write down: EA name, chart symbol, timeframe, and any input parameters you've customized. After the update, you may need to reattach them.

3. Check the release notes for breaking changes

Go to the MT5 Release Notes and scan for:

• Changes to MQL5 language syntax
• ONNX or OpenBLAS library changes (if your EA uses machine learning)
• Removed features or deprecated functions

4. Make sure no positions are running naked

The update process can take a few minutes. During that time, your EA isn't running — if you have open positions managed by EA logic (trailing stops, conditional exits), no one is watching them. Positions with fixed SL/TP set at the broker level are fine. Safest approach: make sure all open positions have fixed SL/TP before updating, or just wait until you're flat.

Post-Update: What to Check

AutoTrading button

After an update, verify the AutoTrading toggle is still enabled. Check the toolbar — the button should be green (enabled), not red. It's a quick sanity check that costs nothing.

EA smiley face

Look at the top-right corner of each chart. A smiley face means the EA is loaded and running. A blank space or frowning face means it failed to load.

Experts and Journal tabs

Click the Experts tab at the bottom of the terminal. Any load errors, missing DLL warnings, or "recompile required" messages will show here. The Journal tab shows platform-level errors.

Recompile your EAs

If you have the source code (.mq5 files), open MetaEditor (F4), and recompile:

1. Open the .mq5 file
2. Press Compile (F7)
3. Check for errors in the output window

New builds occasionally introduce stricter compiler checks. Code that compiled fine on the old build may throw warnings or errors on the new one. Fix these before running live.

If you only have .ex5 files (no source): You depend on the developer to release an updated version. Check MQL5 Market or contact the seller.

How to Roll Back to a Previous Build

MT5 has no supported rollback feature. Live Update cannot be deactivated, and updates include not just executables but also DLLs, libraries (e.g., openblas.dll since Build 5660), help files, and compiler/runtime components. Swapping only .exe files back risks version mismatches that can cause crashes or silent data errors.

The safe approach is prevention:

Before updating: archive the full installation

1. Copy your entire MT5 installation folder (not just executables) to a backup location
2. Also copy the data folder (find it via File → Open Data Folder)
3. Now update your main installation

If the update breaks something:

1. Install a second MT5 into a separate folder (e.g., C:\MT5-Stable\)
2. Copy your archived files into that folder
3. Use this installation for live trading while you troubleshoot the updated one
4. The "Later" button in the Live Update dialog postpones the update to the next restart, but it is not a permanent block — the update will eventually be applied

What NOT to do:

• Don't swap only .exe files back — component mismatches are worse than the original bug
• Don't rely on firewall blocks to prevent updates — this can break Market access, signal subscriptions, and other platform services
• Don't disconnect/reconnect tricks — update checks trigger on trade server connection

Bottom line: If rollback matters to you (e.g., running live EA on a funded account), maintain a separate MT5 installation for testing new builds before updating your production terminal.

2026 Build Timeline: What Changed and What It Means for EAs

Build	Date	Key Change	EA Impact
5830	Apr 24, 2026	Help system dark theme fixes, UI polish	None
5800	Apr 16, 2026	Redesigned trading dialog, Depth of Market integration, web-based help, ONNX/OpenBLAS update verification, new OpenBLAS methods, CopyRates fix, expanded CUDA support, WebRequest Keep-Alive improvement	Low for most EAs; medium for ML/OpenBLAS or WebRequest-heavy EAs
5660	Feb 27, 2026	SOCKS4 proxy dropped, OpenBLAS separated into openblas.dll	Medium — networks using SOCKS4 must migrate to SOCKS5/HTTP. ML/OpenBLAS users should verify library loads correctly
5640	Feb 20, 2026	Dark theme improvements, symbol fundamental data expanded	None
5572	Jan 29, 2026	ONNX CUDA GPU acceleration, new ONNX logging flags, ONNX loads on first MQL5 program use (not platform start)	Medium-High for ML EAs — retest ONNX EAs; recompile if using old flags or want new GPU options
5430	Nov 13, 2025	Charts engine replaced (GDI → Blend2D), BLAS matrix methods added	Medium — custom indicator rendering may look different. New matrix methods available
5320	Sep 25, 2025	Final update for Windows 7/8/8.1/Server 2008 (except Wine). New input(name="...") syntax added	High for old Windows — no future updates on those OS versions. Input syntax: old comment-based syntax still works, no forced migration

How to Update MT5 on Mobile

Android

1. Open Google Play Store
2. Search "MetaTrader 5"
3. Tap Update (if available)

iOS

1. Open App Store
2. Search "MetaTrader 5"
3. Tap Update (if available)

Mobile updates are independent of desktop builds. A new desktop build doesn't mean a new mobile version, and vice versa.

FAQ

Q: Will updating MT5 delete my EAs? No. Updates preserve your MQL5 folder. But always back up before updating, just in case.

Q: My broker seems to be on an older build. Can I still get the latest? MT5 checks for updates via the trade server, so broker-branded terminals may lag behind the official release. However, a newer terminal can generally still connect to an older server — you may just see a compatibility warning rather than being blocked.

Q: Do I need to update MetaEditor separately? No. MetaEditor updates automatically with MT5.

Q: My EA shows "recompile required" after updating. What do I do? If you have the .mq5 source, open it in MetaEditor and press F7 to compile. If you only have the .ex5 binary, contact the EA developer for an updated version.

Q: Can I run two different MT5 builds simultaneously? Yes, by installing MT5 into separate folders. Each installation has its own data folder and can run simultaneously. Some components (like openblas.dll) may be shared at the system level, but for practical purposes they are independent. This is the recommended approach for testing new builds while keeping live trading on a stable installation.