MT5 closing on vps - how do you handle this?
breaking of windows update is a must to avoid such events. There are a few ways to do it, both for temporary period or permanent. just search google. Each method can have varying degrees of success or side effects to other parts of the OS, but after some researching, you can find the right method for your windows version and test it out before deploying it on your trading OS/vps.
i tried registry and group policy tweaks before but some vps providers still force reboots for "security patches" anyway.
my biggest issue isn't even the reboot, it's when the mt5 process stays open but the terminal is actually frozen (ghost state) an update can trigger that easily and you dont even notice until the next day.
I have been using headless linux VPS. Those are much cheaper and flexible. Albeit, aren't user-friendly or that easy to setup. However, once the setup is done, it's actually the most reliable one atleast for me
i tried registry and group policy tweaks before but some vps providers still force reboots for "security patches" anyway.
my biggest issue isn't even the reboot, it's when the mt5 process stays open but the terminal is actually frozen (ghost state) an update can trigger that easily and you dont even notice until the next day.
Forum on trading, automated trading systems and testing trading strategies
Alain Verleyen, 2026.03.23 19:09
Please give technical details :
1. Provide the Journal log file (attach the whole file, not an excerpt).
2. Clarify "unresponsive in the background" : what that means exactly ?
attached the relevant log parts. i removed the login lines for privacy as you can see, there are gaps where the terminal closes with reason 9 (terminalclose) i suspect the vps or windows updates are forcing the shutdown, but the real issue is that the process often stays active in the background without any activity. i don't get any crash dumps or "not responding" errors from windows, the event loop just stops until i manually kill the process and restart mt5.
attached the relevant log parts. i removed the login lines for privacy as you can see, there are gaps where the terminal closes with reason 9 (terminalclose) i suspect the vps or windows updates are forcing the shutdown, but the real issue is that the process often stays active in the background without any activity. i don't get any crash dumps or "not responding" errors from windows, the event loop just stops until i manually kill the process and restart mt5.
thanks for the link i'm checking that thread now, seems related to how mt5 handles gui threading during os shutdowns. my case is similar because the experts stop executing even if the process is running
- 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’ve been running EAs for a while and it’s crazy how much time we spend backtesting while ignoring the infrastructure.
Last week a silent windows update on my vps killed my mt5 right before a volatility spike since the terminal was offline my trailing stops didn't trigger and i took a loss that
shouldn't have happened. it's frustrating when the strategy is fine but the uptime fails.
Curious to hear from the veterans here... how do you actually ensure your terminal stays open 24/7?
Do you just trust your vps provider or do you use some kind of watchdog/monitoring setup?
Personally i don't think windows auto-restart is reliable enough for real capital. I’ve been working on a custom monitoring logic to force-restart the process if it hangs, but i’d love to know if there’s a "standard" way to handle these technical glitches.
What’s your setup for 100% uptime?