bugs are best reported on the threads with headings such as "release build" or "beta build" with version close to the bugged version.
however the issue you reported is common with beta releases -- of which the versions you are reporting - are. this behavior tends to be reported to be fixed on the next proper release version.
i recommend that you try proper relase version 6090. i have it, but i dont intend to try out starting st while am trading. OR, disconnecting the internet while i am trading.
bugs are best reported on the threads with headings such as "release build" or "beta build" with version close to the bugged version.
however the issue you reported is common with beta releases -- of which the versions you are reporting - are. this behavior tends to be reported to be fixed on the next proper release version.
i recommend that you try proper relase version 6090. i have it, but i dont intend to try out starting st while am trading. OR, disconnecting the internet while i am trading.
Thank you, Michael, I reposted this on one of the associated threads, like you advised.
However, when i check the latest release version, MT5 tells me 6122 is actually a release build (in About i can see v5 build 6122) and in Journal > 2026.08.20 12:20:42.995 LiveUpdate you are using the latest version
Thanks
J.
Thank you, Michael, I reposted this on one of the associated threads, like you advised.
However, when i check the latest release version, MT5 tells me 6122 is actually a release build (in About i can see v5 build 6122) and in Journal > 2026.08.20 12:20:42.995 LiveUpdate you are using the latest version
Thanks
J.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hi,
Can anyone reproduce this on recent MT5 builds 6080 or 6122?
All historical/tick data is already downloaded locally, so this is not a history-data issue.
The behavior:
When it fails offline, the Tester log shows for example:
The history warning is misleading in this case because the required data is already present locally. The important behavior is that the tester does not actually initialize when MT5 was started without Internet.
I also observed that on the first successful tester start, terminal64.exe makes a short HTTPS request to a remote server. After this initialization succeeds, Internet can be disconnected and subsequent tests continue working until MT5 is closed.
This suggests recent builds require some kind of online initialization/validation after each fresh MT5 launch before allowing the local Strategy Tester to run.
Can anyone with build 6080 or 6122 reproduce this or know of a workaround?
And a request to the MQL5/MetaQuotes team: please allow the local Strategy Tester to operate completely offline when the required historical data is already stored locally. Backtesting should not require a live Internet connection, particularly when travelling or working without reliable connectivity.
Thank you
J.