Official source for MT5 build verification and MetaQuotes-Demo tick history

[MarwanMT5]

Hello,

Where can I request an official SHA-256 digest for the MetaTrader 5 build 6316 x64 terminal64.exe distributed through LiveUpdate?

I also need ordered EURUSD Bid/Ask tick history from MetaQuotes-Demo for 11 November 2026, from 14:00 to 14:22 UTC. What is the official way to retrieve it and check whether the returned history fully covers that interval?

Thank you.

[Sukamto]

Halo

[Sergey Golubev]

MetaQuotes Demo server is mostly used to update MT5 to beta build and to test beta builds for possible error on software in beta builds, means - MetaQuotes-Demo account should not be used for trading and testing; #1 and #3

[MarwanMT5]

Sergey Golubev #:
MetaQuotes Demo server is mostly used to update MT5 to beta build and to test beta builds for possible error on software in beta builds, means - MetaQuotes-Demo account should not be used for trading and testing; #1 and #3

Thank you. This explains why the terminal received a build newer than the latest published release.

For audit purposes, could you please clarify:

1. Does MetaQuotes publish an authenticated SHA-256 digest for beta build 6316 x64 terminal64.exe?

2. Can CopyTicksRange provide complete, ordered historical Bid/Ask ticks from MetaQuotes-Demo for a specified interval, or is continuity and completeness not guaranteed on that server?

3. For reproducible strategy testing and tick-history validation, should an account from a broker's Demo server be used instead of MetaQuotes-Demo?

Thank you.

[Sergey Golubev]

MarwanMT5 #:

Thank you. This explains why the terminal received a build newer than the latest published release.

For audit purposes, could you please clarify:

1. Does MetaQuotes publish an authenticated SHA-256 digest for beta build 6316 x64 terminal64.exe?

2. Can CopyTicksRange provide complete, ordered historical Bid/Ask ticks from MetaQuotes-Demo for a specified interval, or is continuity and completeness not guaranteed on that server?

3. For reproducible strategy testing and tick-history validation, should an account from a broker's Demo server be used instead of MetaQuotes-Demo?

Thank you.

Do not use MetaQuotes-Demo server for trading and testing. Because MetaQuotes is not a broker.
Use the broker's data for that (and for update MT5 to the official build - download and install MT5 from the brokers' website).

[Sayed Ali Ordibehesht]

I haven't tested that executable or retrieved ticks for the requested interval; the steps below are a verification procedure, not a result for build 6316 or that interval.

I couldn't find a public MetaQuotes SHA-256 reference for that exact build 6316 x64 terminal64.exe. For an audit, check the Authenticode status and signer on the actual executable with Get-AuthenticodeSignature, and record its SHA-256 with Get-FileHash. To verify an exact byte-for-byte match, you'd still need a trusted reference digest for that executable from MetaQuotes.

For the EURUSD interval, use CopyTicksRange with COPY_TICKS_INFO and a dynamic array. If 14:22 UTC is excluded, the inclusive upper bound is 14:21:59.999. Reset the last error before each call and log both the returned count and GetLastError() immediately afterwards. Once the history has synchronised, compare the full request with adjacent, non-overlapping chunks. Compare the returned records in order, including all ticks that share a millisecond.

Agreement tells you the terminal returned consistent history for that interval. Confirming that no source ticks are missing would require an authoritative record of the same feed.

[Sergey El]

No legal agreement promises this data consistency.

From a regulatory, contractual, and MetaTrader 5 API audit standpoint, client-side tick history carries no legal guarantee of consistency by design:

• MT5 Desktop EULA (explicit disclaimer of data warranties):
  
  
  • In the preamble and Section 4.2 , MetaQuotes states that it is a software development company and does not provide data feed services .
    
    
  • In the preamble and Section 2.4 , the company disclaims any warranties regarding data accuracy or the completeness, or timeliness of third-party content .
    
    
  • Under Section 4.1 (No Warranties) , the terminal is provided strictly "AS IS" , with no warranty that its operation will be uninterrupted or error-free, or that any communication or data transmission through MetaQuotes' software will be COMPLETE AND ACCURATE .
    
    
• Public Disclaimer ( [metatrader.com/en/about/disclaimer](https://metatrader.com/en/about/disclaimer) ): The Disclaimer and Technical Risks sections mirror the "as is" basis and disclaim liability for dropped quotes, delays, or feed desynchronization caused by network or server disruptions.
  
  
• Technical Contract of CopyTicksRange (MQL5 Reference): The documentation only defines MqlTick array addressing rules—inclusive range boundaries (>= from_msc and <= to_msc in milliseconds since 1970.01.01 ) and chronological ordering from oldest to newest (index 0 is the oldest tick). However, if history synchronization times out, the function can return an incomplete array ("all it had" synchronized so far) alongside ERR_HISTORY_TIMEOUT , and on a static array it truncates the output with ERR_HISTORY_SMALL_BUFFER (4407) . That is precisely why your verification procedure requires a dynamic array, checking GetLastError() immediately after each call, and performing an ordered record-by-record comparison across chunks—including bursts of ticks sharing the same millisecond.

For audit or regulatory verification (under MiFID II Art. 16(6) / RTS 25), the authoritative record referenced in the final sentence of your excerpt is not the local .tkc cache of a client's terminal64.exe , but the server-side quote and liquidity-aggregator log maintained by the broker itself (such as the MT5 Trade Server tick database and the Ultency Ticks stream), which the broker's Client Agreement designates as the sole authoritative record.