Subject: MetaTrader 5 Build 6290 – Strategy Tester historical data failure

New comment

Hello,

Following an MT5 update on 28 October 2026, my Strategy Tester has stopped working correctly.

Platform: MetaTrader 5, Build 6290 (27 October 2026)

Server: MetaQuotes-Demo

Symbol: EURUSD, M15

Problem:

Strategy Tester repeatedly fails to synchronise historical data, despite historical bars being available in the Symbols window.

The Journal reports:

  • bad container found, must be resynchronized

  • EURUSD: there is no history

  • cannot get history EURUSD,M15

  • cannot load indicator 'Moving Average' [4805]

  • cannot load indicator 'Average True Range' [4805]

The issue occurs with both my custom Expert Advisor and the standard MT5 Examples → Moving Average Expert Advisor.

I have tested using both Every tick based on real ticks and 1 minute OHLC. The tests fail or finish almost immediately without processing trading ticks.

I have restarted MT5, reloaded historical data and rebuilt the EURUSD chart-history cache, but the problem persists.

Historical EURUSD M15 bars can be retrieved through Symbols → Bars → Request.

The Strategy Tester was working before the recent platform update.

Could you please investigate whether build 6290 has a historical-data synchronisation or Strategy Tester compatibility issue, and advise how to resolve it?

Thank you.

I can confirm the same issue! Please fix it with the next update.
Alain Verleyen #:

The "bad container found" issue also exists after I updated to build 6292, at least I can confirm this for custom symbols. The previous build I used (16th of October) had not such problems.
Bernhard Stremayr #:
The "bad container found" issue also exists after I updated to build 6292, at least I can confirm this for custom symbols. The previous build I used (16th of October) had not such problems.

If you want something to be fixed, it should be reported correctly so it can be reproduced.

Insufficient information are being reported up to now.

Alain Verleyen #:

If you want something to be fixed, it should be reported correctly so it can be reproduced.

Insufficient information are being reported up to now.

I was just referring to the issue described in the the initial comment (by Shaun Boyd, see above), confirming that I experienced the exact same issue. The latter persisted with the latest build 6292, however, after an additional restart of the MT5 application, everything works flawless again (I have no idea why this is the case).
New comment