Summary: A practical walkthrough of troubleshooting MT4 EA load failures and DLL errors, with platform-specific observations on Windows 11 vs Windows 10 based on experience.




I've been running EAs on MetaTrader 4 for a handful of years now, and nothing kills your trading day quite like dragging a fresh expert advisor onto a chart and getting absolutely nothing in return. No smiley face, no parameters loading up, just a dead quiet chart and that little "expert" icon either greyed out or showing a sad face.

This happened again last Tuesday with a client's new hedging algorithm. I downloaded the EA files, dropped them into the Experts folder, compiled without errors in the MetaEditor, but when I attached it to the EURUSD chart? Nothing. Blank. The "Expert Advisor" button in the toolbar was lit green, but the chart corner showed that dreaded sad face.

If you're reading this, you probably already know the basics. You've placed the .ex4 file in MQL4/Experts, maybe you dropped a .dll in the Libraries folder too. You've restarted MT4, maybe even rebooted the whole VPS. But that EA just won't fire. So let me walk you through what I actually did to fix it, because the solution was in a place I almost overlooked.

Step 1: Stop trusting the "Common" tab completely



The first reflex is always to open the EA properties and check the "Common" tab. You'll see "Allow Automated Trading" and "Allow DLL Imports". You tick those boxes and hit OK, right? But here's the thing I've noticed over the last few years - that doesn't always stick. On some builds, especially newer ones, if the EA has external dependencies, checking those boxes on the chart isn't enough. You need to set them globally.

Go to Tools > Options > Expert Advisors and check two things:
"Allow automated trading" – obviously, this has to be on.
 "Allow DLL imports" – this one's tricky. Even if you allow it per-chart, the global setting can override it.

The official MQL4 documentation states clearly: "To allow the use of DLLs, you need to enable the corresponding option in the terminal settings and in the Expert Advisor properties" (docs.mql4.com). I've found that if these two aren't in sync, the EA will fail silently. No error message, no pop-up, just that sad face.

Step 2: The "DLL" tab is where the real story hides



Here's the part that got me. Most people don't even look at the second tab in the EA properties window. There's a tab literally named "DLL". And in that tab, you'll see a list of external functions the EA is trying to call. If you see any entries with a little warning icon next to them, or if the list is just blank when you know the EA uses a custom DLL, that's your problem.

On Windows 11, I've observed that the security permissions for the Terminal folder are more restrictive by default. This isn't documented anywhere on MetaQuotes that I could find, but it's something I've confirmed by testing on two separate Windows 10 machines and two Windows 11 machines. On Windows 10, if the DLL is in the right place and you allow imports, it usually just works. On Windows 11, the Terminal might not even have read permissions for that DLL file, especially if you've installed MT4 in Program Files.

Step 3: The reinstall trick that actually works



The common advice you'll see on forums is "just reinstall MT4" or "copy the DLL to System32". Don't do either of those yet. The System32 approach is a security risk, and reinstalling is a nuclear option that wastes time.

Here's what I did to get that client's EA running within 10 minutes:
  • I closed MT4 completely. Not just detached the chart, actually exited the application.

  • I navigated to the MQL4/Libraries folder. I deleted the existing DLL file and re-copied it from the original archive, making sure it wasn't blocked by Windows.

  • Right-click the new DLL file, go to Properties, and if you see an "Unblock" checkbox at the bottom, check it and hit Apply. This is crucial on Windows 11 – the OS flags downloaded DLLs from the internet as potentially unsafe, and MT4 respects that flag even if you've allowed DLL imports.

  • I reopened MT4 and went to the Navigator panel. Instead of dragging the EA, I double-clicked it. This forces the properties window to open before attaching, which is more reliable.


    • According to the MetaQuotes help center (help.metaquotes.net), the correct sequence is: place files, restart terminal, then attach. But I'll add my own insight – restarting is not enough. You need to ensure the file is unblocked by Windows first. That extra step is the difference between 10 minutes and 2 hours of head-scratching.

    Step 4: For persistent "load failed" errors – check the logs with a specific filter



    This is the part where most people give up and blame the EA developer. Open the Experts tab in the Terminal window. You'll see some generic messages like "Expert Advisor loaded successfully" or maybe "failed". But if you see nothing at all, click the Journal tab instead. Then right-click inside the journal and choose "Show All".

    I filter by "DLL" and "error" specifically. One time I found error code 126 – that's "The specified module could not be found". In plain English, that means the Windows system is looking for a dependency of your DLL, not the DLL itself. Microsoft's official documentation on DLL search order (learn.microsoft.com) confirms that Windows looks for dependencies in the same directory as the calling executable, then in System32, then in the PATH environment variable.

    So if your EA's DLL depends on something like msvcp140.dll (a Visual C++ runtime), and that's missing, your EA will fail to load even though the custom DLL is right there. The fix? Install the latest Visual C++ Redistributable from Microsoft. It's a 5-minute download and it solved the problem in three separate cases for me over the past year.

    Step 5: The Windows version difference I mentioned earlier



    This is my own observation and I haven't seen it in any official guide. On Windows 10, the terminal usually runs with user-level permissions. On Windows 11, especially with the 22H2 update and later, the terminal often runs under a more restricted AppContainer context. This changes the file access paths and the DLL search order slightly.

    To test this, I ran the same EA on a Windows 10 VM and a Windows 11 VM side by side. On Windows 10, the EA loaded in 2 seconds. On Windows 11, it gave a "load failed" error until I moved the DLL from MQL4/Libraries to the root Terminal folder (the one that contains terminal.exe). That's not a documented solution, but it worked consistently. I've since made this my first check when dealing with Windows 11 systems.

    The final configuration that worked



    For that particular EA last week, this was the winning combination:
    Global DLL imports allowed in Tools > Options.
     The DLL file unblocked in Windows Properties.
    The Visual C++ Redistributable 2015-2022 installed.
     The DLL placed in both MQL4/Libraries and the root Terminal folder (just to be safe).
  • The EA attached via double-click, not drag-and-drop.


    • After that, the smiley face appeared and the EA started placing trades as expected. The client was relieved and I was reminded why these small details matter more than the code itself half the time.

    Reference: MQL4 Documentation – Expert Advisors and DLLs (docs.mql4.com), MetaQuotes Help Center – Installation and Launch of Expert Advisors (help.metaquotes.net), Microsoft Learn – Dynamic-Link Library Search Order (learn.microsoft.com).

    This article is originally published on FXEAR.com, original content, reproduction without authorization is prohibited.