MetaQuotes has pushed MetaTrader 4 Build 1492 after a software regression caused Expert Advisors and custom indicators to fail to load or display correctly for some traders, turning what initially looked like isolated chart problems into a broader automated-trading infrastructure issue.
Japanese broker Goldenway Japan, which operates FXTF, said on October 7 that MetaQuotes had confirmed the newly released Build 1492 resolves the problem affecting MT4 Builds 1490 and 1491.
FXTF is now instructing customers running either affected build to update to 1492.
The broker had warned on October 5 that customers upgrading MT4 could encounter indicators and Expert Advisors that did not display normally. In related cases, MT4 itself could fail to start correctly or crash.
MetaQuotes separately acknowledged the underlying software problem publicly on October 5. Administrator Renat Fatkhullin said the company had introduced a bug that appeared in some cases when loading EX4 files, the compiled format used for MT4 Expert Advisors, indicators and scripts. MetaQuotes then made Build 1492 available through its Demo environment and automatic web update.
That makes this more consequential than a graphical display glitch at one Japanese broker. The affected code sits inside MetaTrader 4 itself, a platform distributed through brokers around the world.
Build 1491 Could Leave Software Loaded but Not Actually Working
The unusual part of the failure was that MT4 did not always make the problem obvious.
Users reported custom indicators appearing normally in the Navigator or indicator list while failing to draw on the chart. In other cases, only some instances of the same indicator loaded after a restart or template change.
Forum testing also pointed to problems beyond visual rendering.
One user created a minimal EA using a two-second timer and attached it to nine charts. The EA registered its timers successfully on all nine, but several instances failed to receive timer events. Running the same setup on an older build did not reproduce the behavior.
Another trader reported that an EA relying on a Heiken Ashi indicator entered a continuous error loop after the Build 1491 upgrade and would not trade. The same report said the strategy tester also stopped progressing normally.
Those reports do not establish that trades were missed in real funded accounts, nor do they quantify any financial damage. They do show why the distinction between an indicator-display bug and an automated-trading failure matters.
An EA can depend on indicator calculations, timer callbacks or other events before deciding to place, modify or close an order. If those components fail silently, the terminal may remain connected while the strategy itself is no longer functioning as intended.
MetaQuotes Had Just Released Build 1490 With Trading Changes
The issue came immediately after a significant MT4 update.
MetaQuotes announced Build 1490 for October 2 with security improvements, bug fixes and changes to how Stop Loss and Take Profit levels behave under FIFO trading rules.
Dave Finances previously examined how Build 1490 changed FIFO Stop Loss and Take Profit behavior, including automatic propagation of protection levels across positions on the same instrument.
The new problem then surfaced across Builds 1490 and 1491 in FXTF’s environment.
MetaQuotes’ own explanation is narrower: the company said it introduced a bug that could appear while loading EX4 files. It did not publicly specify every condition required to trigger the issue or explain whether Builds 1490 and 1491 contained exactly the same faulty code path.
That distinction is important. FXTF has confirmed which versions caused problems for its customers; MetaQuotes has confirmed the underlying EX4-loading defect and its fix.
The Evidence Points Beyond One Broker
Independent trader reports suggest the regression was not limited to FXTF.
MQL5 forum logs submitted by one user showed a Darwinex-branded MT4 Build 1491 installation loading Expert Advisors during troubleshooting. Another trader said they temporarily reverted a Forex.com MT4 installation after indicators stopped displaying correctly.
Those are user reports, not formal incident notices from Darwinex or Forex.com, so they should not be treated as confirmation that either broker suffered a platform-wide outage.
They do, however, support the more important technical point: MT4 client builds are distributed across many broker-branded installations. A defect in a MetaQuotes terminal release can therefore surface independently at unrelated firms.
This is different from a broker-specific backend outage such as the recent CMC Markets order-processing incident, where the affected infrastructure sat within one provider’s trading environment.
With MT4, one upstream software regression can potentially reach traders through numerous brokers.
The Biggest Question Is Whether EAs Missed Live Trades
Build 1492 appears to have resolved the immediate software problem. Multiple users reported that indicators and startup behavior returned to normal after installing the patch.
But the more important forensic question remains unanswered.
Did any live Expert Advisors fail to execute trades, exits or risk-management actions while traders believed they were operating normally?
So far, there is no verified evidence of specific monetary losses caused by the regression.
That does not mean none occurred.
The failure mode makes the question difficult to investigate because an EA that never receives an expected event may simply do nothing. There may be no rejected-order message because no order was ever generated.
For a trader running a strategy around the clock on a VPS, the terminal remaining online does not prove the automation remained operational.
That is why execution records, EA logs and expected-versus-actual trade signals from October 2 through the Build 1492 upgrade window could matter more than screenshots showing missing indicators.
The broader problem resembles the execution uncertainty seen when Propr users recently alleged lag and disappearing orders on a beta trading platform. A visible platform problem is frustrating; a platform problem that creates uncertainty over whether an instruction ever executed is materially more serious.
FXTF Users Also Face a Separate Minimum-Build Deadline
FXTF’s October 7 instructions include a second issue that should not be confused with the Build 1490/1491 bug.
The broker says MT4 installations below Build 1440 are now considered obsolete and cannot log in to its service.
Customers therefore cannot simply solve the new regression by remaining indefinitely on an old version.
FXTF says some installations may require several update attempts before reaching Build 1492. If that fails, customers may need an overwrite installation or full reinstall.
The broker recommends backing up the MT4 data folder first because templates, chart profiles, third-party EAs and indicators can be reset during reinstallation.
That creates an awkward update path for algorithmic traders. The newest affected builds needed to be replaced because of the EX4-loading regression, while sufficiently old builds can no longer connect.
For users with complex automated setups, version management is therefore part of operational risk rather than merely software maintenance.
Build 1492 Fixes the Immediate Bug, Not the Infrastructure Question
The rapid patch is the positive part of the story.
MetaQuotes reproduced the problem, acknowledged that it had introduced a bug and released Build 1492 shortly afterward. FXTF has now independently confirmed receiving MetaQuotes’ assurance that the fix resolves the issue and is directing affected customers to upgrade through its official Build 1492 notice.
But the episode exposes a structural risk in retail FX infrastructure.
Many traders think of their broker as the company providing the trading platform. In reality, an MT4 account often depends on at least two technology layers: the broker’s own servers and configuration, and MetaQuotes software running on the trader’s machine.
A failure in either can interrupt trading.
And for automated traders, “platform available” is not a sufficient health check. The terminal can launch, connect to prices and appear functional while an EA, indicator or event callback underneath it is not behaving normally.
That is the part brokers should now investigate.
Build 1492 appears to have fixed the software regression. What remains unknown is how many brokers pushed Builds 1490 or 1491 to customers, how many live EAs were affected before the patch arrived and whether any users can document trades that should have occurred but never did.
If those cases emerge, the MT4 incident stops being merely a bad software update.
It becomes an execution-risk event distributed through one of retail FX’s most widely used infrastructure layers.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape.