MT5 5.0.0.6182: restoring a specific build, and starting without applying a downloaded update

New comment

Hello,

We run MetaTrader 5 build 6182 (distributed by our broker). The build 6230 update has been downloaded by Live Update but not yet applied. We need written, documented answers to the following. Please cite official documentation where it exists.

1. Installer behaviour

The installation help describes mt5setup.exe as a web installer. If an mt5setup.exe has version resource 5.0.0.6182, does it install build 6182, or does it always download and install the current release? Can it install without an Internet connection?

2. Specific build

Is there any official way to obtain or reinstall a specific earlier build (for example 6182), such as an offline or standalone distribution, or an archived build?

3. Broker-distributed terminals

For a terminal installed by a broker's own installer into its own folder: are the program binaries identical to the generic MetaQuotes build of the same number, or do they differ? To restore that terminal to a given build, must the broker's installer be used?

4. Downloaded update not applied

The Live Update help states that the system cannot be deactivated and that a postponed update is applied at the next start. For a terminal whose update is already downloaded:

  • Is there any supported method to start it without applying that update (for example, starting without a network connection, or removing the downloaded packages)?
  • Is that method documented?

Please distinguish documented behaviour from observed behaviour. We will not test anything on a live trading account.

Thank you.

What necessitates the use of a specific build?
Vladislav Boyko #:
What necessitates the use of a specific build?

Thank you for your reply.

We need to preserve a validated, fixed software configuration for an automated-trading safety review. The relevant program binaries are hash-verified, and applying a different build would invalidate the existing verification until the new build has been assessed.

Could you please clarify the specific technical questions in the original post, particularly Question 4?

For a terminal running build 6182 with build 6230 already downloaded but not yet applied:

  1. Is /skipupdate a recognized and supported startup parameter for preventing the downloaded update from being applied at startup?
  2. If so, is this behavior documented, and does it apply when the update package is already staged?
  3. If not, is there another documented, supported way to prevent the staged update from applying until verification is complete?

If no such method is supported, please clarify the supported procedure for restoring a specific earlier build.

We are seeking documented behavior and will not experiment on a live trading account. Thank you.

As far as I am aware, if you do not connect to the MetaQuotes demo server, your already-installed terminals will not update to beta builds.

Bhavesh R #:
We need to preserve a validated, fixed software configuration for an automated-trading safety review. The relevant program binaries are hash-verified, and applying a different build would invalidate the existing verification until the new build has been assessed.

This is just some vague AI slop; I don’t see an answer to my question here.

From what I’ve seen on the forum, I can recall only one reason why someone might need a specific terminal build other than the latest release version: when they are trying to use pirated MQL applications.

Bhavesh R #:
Could you please clarify the specific technical questions in the original post, particularly Question 4?

I am just a forum moderator; I don’t have enough knowledge to answer all the questions.

Bhavesh R #:

Thank you for your reply.

We need to preserve a validated, fixed software configuration for an automated-trading safety review. The relevant program binaries are hash-verified, and applying a different build would invalidate the existing verification until the new build has been assessed.

Could you please clarify the specific technical questions in the original post, particularly Question 4?

For a terminal running build 6182 with build 6230 already downloaded but not yet applied:

  1. Is /skipupdate a recognized and supported startup parameter for preventing the downloaded update from being applied at startup?
  2. If so, is this behavior documented, and does it apply when the update package is already staged?
  3. If not, is there another documented, supported way to prevent the staged update from applying until verification is complete?

If no such method is supported, please clarify the supported procedure for restoring a specific earlier build.

We are seeking documented behavior and will not experiment on a live trading account. Thank you.

Restoring a specific build is not supported. 

Do it on your own and at your risks.

New comment