MT5 build 5833 disconnects after update on Windows 11 ARM / Apple Silicon / Parallels

New comment
 

Hello

After updating MetaTrader 5 to build 5833, my desktop terminals can no longer connect to my prop firm account.


I updated five separate MT5 installations and all of them became disconnected after the update. At least one of those installations is clean, with no EAs, indicators, trade copiers, or custom tools installed.

Before the update, the terminal was connecting successfully using build 5660. After LiveUpdate to build 5833, the issue started.

Environment:
- MetaTrader 5 x64 build 5833
- Windows 11 ARM
- Apple Silicon Mac
- Running through Parallels
- The same account still works normally on the mobile app

Relevant sanitized Journal extract:

Before the update, connection worked:

[time] Network     '[ACCOUNT_ID]': authorized on [BROKER_SERVER] through Access Server [X] (ping: ~210 ms, build 5660)
[time] Network     '[ACCOUNT_ID]': terminal synchronized with [BROKER_NAME]
[time] Network     '[ACCOUNT_ID]': trading has been enabled - hedging mode
[time] LiveUpdate  new version build 5833 (IDE: 5833, Tester: 5833) is available
[time] LiveUpdate  downloaded successfully
[time] LiveUpdate  start "[REDACTED_PATH]\terminal64.exe" /update /path:"[REDACTED_MT5_INSTALL_PATH]"

After the update:

[time] Terminal    MetaTrader 5 x64 build 5833 started for MetaQuotes Ltd.
[time] Terminal    Windows 11 build 26200, Apple silicon, x64
[time] Terminal    [REDACTED_TERMINAL_DATA_PATH]
[time] Terminal    crashlog generated
[time] Network     '[ACCOUNT_ID]': disconnected from [BROKER_SERVER]

When trying to add/login to the existing account again, the Journal repeatedly shows messages like:

[time] Broker      [BROKER_SERVER_1]: no demo/preliminary groups on server side
[time] Broker      [BROKER_SERVER_2]: no demo/preliminary groups on server side
[time] Broker      [BROKER_SERVER_3]: no demo/preliminary groups on server side

Notes:
- Account ID, broker name, server name, IP address, and local file paths were redacted.
- The issue started immediately after updating to build 5833.
- It happens on five different MT5 installations.
- It also happens on a clean installation without any EA or custom plugin.
- The same account works on the mobile app, so the credentials and account itself seem valid.

Questions:
1. Is there a known issue with MT5 build 5833 on Windows 11 ARM / Apple Silicon / Parallels?
2. Could this be related to x64 emulation on Windows ARM?
3. Is the “crashlog generated” line enough to identify the problem, or should I provide a specific crash dump file?
4. Is there a safe way to roll back to the previous MT5 build?
 
Transmitted to MetaQuotes.
 
Update: a fresh installation from the official MT5 website also installed build 5833, but this fresh installation connects correctly and shows “trading has been enabled - hedging mode”.

So the issue seems to affect installations updated from build 5660 to build 5833, not build 5833 itself. It may be related to migrated data folder/config/account/server cache after LiveUpdate.
 
Same, cant login to Exness accounts on my Mac parallel.
 
It's working now after upgrading to build 5834. Thank you community.
New comment