Customer Story: Moving an MT5 Expert Advisor to an AVX2 Node | VPS Mart
A forex trader running an MT5 Expert Advisor (EA) on an Express Windows VPS found that the EA needed AVX2 CPU instructions, while their current VPS node supported only AVX. Support gave two ways to move to an AVX2 node, the customer picked a full migration with their data, chose a maintenance window in their own time zone, and confirmed that everything worked on the new server less than eight hours after opening the ticket.
Submitted by user "a**@****.com" · Support ticket, July 23, 2026*
Application Scenario
The customer uses the VPS to run automated trading:
- Running a MetaTrader 5 (MT5) Expert Advisor on a Windows VPS that stays online
- Keeping the EA working around the clock without a local PC
- Needing the host CPU to support the instruction sets the EA was built for
Server Specifications
Product Name: Express Windows VPS
CPU: 2 CPU Cores
RAM: 4GB
Storage: 60GB SSD
IP Address: 1 Shared IPv4
Operating System: Windows
Software: MetaTrader 5, Expert Advisor
The EA needed AVX2, but the customer's current VPS node only supported AVX
At 20:38 on July 23, 2026, the customer opened a ticket with a short and precise request. Their MT5 Expert Advisor requires AVX2 CPU instructions, their current VPS only exposes AVX, and they asked to be moved to a node that supports AVX2.
The original ticket as submitted by the customer.
This kind of problem is easy to misread. An EA that can't run on a CPU without AVX2 doesn't always say so clearly, so it can look like a broken EA, a bad install or a faulty terminal. The VPS itself was healthy, and the cause sat in the processor of the host node it was running on.
Two ways to get to an AVX2 node
Joe from our Support Department, a human support expert, replied 26 minutes after the ticket was opened. He confirmed that we could move the VPS to a host node that supports AVX2, and he laid out two options:
- Migrate with data. The entire VPS moves as it is to the new node. This takes around 2 hours of downtime, and the IP address changes after the migration. All files, configurations and applications stay intact.
- Reinstall on a new AVX2 node. Faster, but a fresh VPS erases all existing data, so it only suits someone with nothing critical to keep.
The customer chose the first option at 21:10, because their EA, settings and terminal were already set up and they wanted to keep all of it.
Scheduling the maintenance window
Joe then asked for a preferred window, including the customer's time zone, and repeated what to expect: about 2 hours of downtime, a new IP address, and no change to the customer's data.
The customer replied at 22:00 with a specific slot: Philippine Time (PHT) UTC+8, 1:00 PM on Friday, July 24. Picking a quiet hour in their own time zone meant the downtime fell where it hurt least.
At 04:07 on July 24, Penny from the Support Department confirmed that the migration was complete. The new server was active, the login information was the same as on the previous server, and AVX2 was enabled and fully supported. She also reminded the customer that anything tied to the old IP address would need to be updated to the new one.
At 04:25 the customer wrote back that everything was working as expected on the new environment.
| Date and time (2026, ticket time) | What happened |
|---|---|
| Jul 23, 20:38 | Customer submits the ticket asking for a move to an AVX2 node |
| Jul 23, 21:04 | Joe replies with two migration options |
| Jul 23, 21:10 | Customer chooses to migrate with data |
| Jul 23, 21:44 | Joe asks for a maintenance window and restates downtime, IP change and data safety |
| Jul 23, 22:00 | Customer picks 1:00 PM Friday, July 24 (UTC+8) |
| Jul 24, 04:07 | Penny confirms the migration is done, with AVX2 enabled |
| Jul 24, 04:25 | Customer confirms everything works on the new server |
Before and after
| Before | After | |
|---|---|---|
| CPU instructions on the host node | AVX only | AVX2 enabled and fully supported |
| MT5 Expert Advisor | Could not get the AVX2 support it needed | Customer confirmed it works as expected |
| Data and settings | On the old node | Moved intact |
| Login | Existing credentials | Same login information |
| IP address | Previous IP | New IP after migration |
| Planned downtime | None | About 2 hours, in a window the customer chose |
| Time from ticket to confirmation | None | 7 hours 47 minutes |
The ticket doesn't record how long the downtime lasted in practice, only the estimate given beforehand.
If your EA needs AVX2, say so in your first message. The exact requirement is what turns a mystery into a scheduled migration.
Notes & Troubleshooting
- Check which CPU instruction sets your EA or terminal build needs before you pick a plan. If it needs AVX2, tell support before you order or as soon as you find out.
- A migration with data keeps your files, configurations and applications, but the IP address changes. Update anything that points to the old IP, such as remote access shortcuts, allow lists and external tools.
- Reinstalling on a new node is quicker but erases data, so only choose it if you have nothing to keep or you have your own backup.
- Choose a maintenance window in your own time zone and tell support which one it is. Downtime lands in the hours that suit you.
- After the move, log in and confirm the EA starts and trades as expected before you rely on it.
- Technical support is available 24/7 by ticket and live chat, and every ticket is answered by a person. In this case that was Joe and Penny, and the timestamps above come from the ticket itself.
Deploy Your Own Version of This Use Case Now?
Express Windows VPS for MT5
- CPU: 2 CPU Cores
- Memory: 4GB RAM
- Disk: 60GB SSD
- IP: 1 Shared IPv4 (dedicated IP available for $2/mo)
- OS: Windows
$8.99/mo
If your EA depends on AVX2, ask our team before you order. Running several terminals? See our Windows VPS sizing for MT5, or a dedicated server for 20 terminals or more.
Last Updated: 10/27/2026