I still remember the frustration of spending hours trying to get a commercial EA to load on my MT4, only to be greeted by a cryptic "dll not found" error. After digging through logs and testing different setups, I found that the issue was rarely what it seemed at first glance. Let me walk you through what actually works.
Understanding the Core Problem
When an EA fails to load, the culprit is almost always one of three things: incorrect file placement, 32-bit/64-bit mismatch, or security software blocking the DLL. The MQL4 documentation clearly states that "the corresponding module (ex4 or dll) is loaded during the program load" and that "MQL4 libraries are loaded from the terminal_dir\MQL4\Libraries folder" .
Here's where most tutorials get it wrong. They tell you to simply drop files into the Libraries folder and call it done. But I've seen cases where even after doing everything "right," the EA still wouldn't load.
Step 1: Locate the Correct Folder
Forget about the Program Files directory. On modern Windows systems, MT4 stores user files in the AppData folder. Here's the path you actually need:
``
C:\Users\[YourUsername]\AppData\Roaming\MetaQuotes\Terminal\[TerminalID]\MQL4\
The is a random alphanumeric string. Each MT4 installation gets its own. You can find this by opening MT4, going to File > Open Data Folder. This opens the exact folder your terminal is using.
Step 2: Place Files in the Right Places
The EA file (.ex4 or .mq4) goes into the Experts folder. The DLL file goes into the Libraries folder.
But here's the crucial detail most people miss: if your DLL depends on other DLLs, those dependent DLLs must go into the terminal's root folder – the one containing terminal.exe`. I learned this the hard way when a C# DLL kept throwing exceptions. The MQL5 forum discussion confirms this behavior: when you "load DLL inside your MQL4 script or EA it looks inside Librarys folder and then add that dll to the assembly of the terminal application (MT4) so the dll is now dynamicly loaded into terminal.exe and when you try to load another dll inside that dll it looks to its root directory which is where terminal.exe is" .Step 3: Check the Architecture
MT4 is a 32-bit application. This means your DLL must be 32-bit. A 64-bit DLL will cause the EA to fail silently or throw a cryptic error. I've seen traders waste days on this issue. To verify your DLL's architecture, use Dependency Walker or check the file properties in Windows.
Step 4: Enable DLL Imports in MT4
Even with files in the right place, MT4 won't load DLLs unless you explicitly allow it:
If you skip this step, the EA will load but won't function. The Experts journal will show "Expert Advisor stopped" with no further explanation .
Step 5: Handle Security Software
Windows Defender and other antivirus software often quarantine or block DLL files from unknown sources. I've seen this happen repeatedly with commercial EAs. Check your antivirus quarantine and add your MT4 data folder to the exclusion list.
My Personal Discovery on Windows Versions
Here's something I discovered after testing across multiple machines: Windows Server and Windows 10 handle DLL permissions differently. On Windows Server 2016, I found that DLLs placed in the Libraries folder sometimes failed to load despite working perfectly on Windows 10. The solution was to place the DLL in both the Libraries folder AND the terminal root folder. I suspect it has to do with how Windows Server handles dynamic link library search paths versus desktop Windows.
Step 6: Check the Experts Journal
Open the Experts tab in the Terminal window (press Ctrl+T if it's hidden). This shows real-time error messages. Common errors include:
Step 7: The Nuclear Option
If nothing works, try these:
I've had cases where MT4 cached the EA state and a simple restart wasn't enough – a clean reinstall was necessary.
Step 8: VPS Considerations
If you're running on a VPS, the same rules apply – but watch out for the VPS operating system. Some EAs require specific Windows versions. According to industry sources, "many EA temporarily only support these versions: Windows Server 2008/2012/2016" . Windows Server 2019 or 2022 might cause compatibility issues.
---
Reference:
本文首发于FXEAR.com，原创内容，未经授权禁止转载