MetaTrader4 stopped working on OSX
Please consider which section is most appropriate — https://www.mql5.com/en/forum/172166/page6#comment_49114893
Try to extract the log from the terminal directory in the prefix ~/Library/Application Support/net.metaquotes.wine.metatrader4.
Provide the terminal and wine version from the log. Also, if there are errors in the log, provide them.
Try to extract the log from the terminal directory in the prefix ~/Library/Application Support/net.metaquotes.wine.metatrader4.
Provide the terminal and wine version from the log. Also, if there are errors in the log, provide them.
This is all the content of the last log:
0 14:07:16.641 LiveUpdate: update C:\Program Files (x86)\MetaTrader 4\MQL4 folder started
0 14:07:16.705 LiveUpdate: update C:\Program Files (x86)\MetaTrader 4\MQL4 folder finished
In one of the previously backupped logs I found this - I hope this is waht you asked for:
0 01:28:16.541 MetaTrader 4 build 1425 started (MetaQuotes Software Corp.)
0 01:28:16.543 Microsoft Windows 7 x64, 4 x VirtualApple @ 2.50GHz, Memory: 694 / 16383 Mb, Disk: 89 / 460 Gb, GMT+1
0 01:28:16.543 Data Folder: C:\Program Files (x86)\MetaTrader 4
For a few days not even the above mentioned wipe MT4 and reinstall works any more. MT4 totally stopped working in any way I try it.
I just tried to set up a clean install of OSX Ventura onto an external hard drive from a freshly downloaded OS installer. To the clean system I downloaded the MT4 installer, installed and it didn't start at all even on the clean installed OSX.
Just like I wrote above. I see MT4 and wine processess running in Activity Monitor, but it doesn't show up in the Force quit list and the MT4 window doesn't even appear.
I was able to install Parallels Desktop and install MT4 under a Windows11 running in Parallels. That version does run as expected and it is possible to quit and restart. Works normally - however I would prefer not using Parallels and stay with the Wine MT4 that I used previously. However that version of MT4 seems impossible to run in any way on this computer now.
Unfortunately I don't have access to any other computer so I cannot try to run it on any other computer and the clean OS install also seems to fail on this computer.
0 01:28:16.541 MetaTrader 4 build 1425 started (MetaQuotes Software Corp.)
0 01:28:16.543 Microsoft Windows 7 x64, 4 x VirtualApple @ 2.50GHz, Memory: 694 / 16383 Mb, Disk: 89 / 460 Gb, GMT+1
If you used the Metaquotes installer, you have a very old build. The prefix should be Windows 10 and the terminal should be version 1440.
Try deleting prefix files ~/Library/Application Support/net.metaquotes.wine.metatrader4 and the terminal itself. After that, install pkg from metatrader4.com.
If you used the Metaquotes installer, you have a very old build. The prefix should be Windows 10 and the terminal should be version 1440.
Try deleting prefix files ~/Library/Application Support/net.metaquotes.wine.metatrader4 and the terminal itself. After that, install pkg from metatrader4.com.
Thank you very much for the suggestion! I will try to download a new installer and upgrade.
It seems upgrading from Ventura to Sonoma solved my initial issue.
First I tried to make a clean install of Ventura onto an external hard disk, but MT4 didn't start on that system either.
Then I made a clean install of Sonoma onto that external disk and MT4 started running without any problem there.
Then I upgraded my working system to Sonoma and MT4 runs as a charm ever since.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
I have an Apple MacBook Air M1 with OSX Ventura 13.7.4 (22H420). My MT4 installer is straight from my broker's website, but I also tried using the installer from the MT4 website. Doesn't seem to be any different.
I have been using MetaTrader4 for about a year and never had any issues running it in the past. No updates or any other system affecting changes were made that could trigger my running issues. Just one morning when I started MT4 it did start and quit immediately and I was never able to restart it again.
I tried to force quit MT4 to allow a proper starting it, but doesn't show up on the force quit running apps list.
In the Activity Monitor I saw some processes (MT4 app and Wine) and can kill them there. But starting MT4 again just starts these processes again. MT4 doesn't start or if it starts then quits immediately, so the issue stays.
I tried restarting MT4, restarting OSX, no change with the issue.
I tried to run MT4 on a newly created user account on the computer. MT4 starts for the first time, but once I quit/restart MT4, it doesn't start ever again on that account either, just like with my main account.
I tried to run MT4 in a Guest user account. MT4 starts for the first time, but once I quit/restart MT4, it doesn't start ever again. When the Guest account is quit it deletes all newly created files and restarts the Guest account basic settings. Starting the Guest account again allows running MT4 once, but once I quit/restart MT4, it doesn't start ever again.
I found the user/Library/AppSupport/net.metaquotes folder with the app settings. Once it is deleted and MT4 is reinstalled anew then it runs for the first time, but once I quit/restart MT4, it doesn't start ever again. I need to delete all of it's files and make a new clean install every time I run MT4.
This also means I cannot keep my previous chart window layouts, profiles, chart drawings. I can copy them from backup, but MT4 doesn't recognize them unless it is restarted - and once I quit/restart MT4, it doesn't start ever again without reinstalling it. The installer starts MT4 after installation, so I cannot copy the settings before starting MT4.
Now I can run MT4 once without quitting or restarting, but needs to recreate manually all the settings after reinstallation once it quits. What is quite an unwanted hassle...
I don't know how I could update Wine that runs MT4 on OSX or what else I could try.
I'm considering upgrading from Ventura to Sonoma or Sequoia, but there is no guarantee it would solve anything.
Probably a clean installation of the entire system could solve the issue hopefully, but I would prefer not to make a clean install from scratch. What else could I try to solve the issue without a clean install?
Does anyone have any idea what may cause such behavoir and how to solve this issue?