CXM Direct Download — Coming Back to the File
A trading terminal is fetched once, and then it is fetched again. This page counts the return visits: which events make a fresh copy necessary, and which parts of the setup you never do twice.
Open Account →Most people fetch the CXM Direct terminal once, then fetch it again months later without remembering the first time. The trigger is almost never the broker: it is a new machine, a reinstalled system, a second desk, a replaced phone or a folder someone cleaned out. A repeat download replaces the local program only. The account behind it keeps its number, its server name and its record of closed trades, which is why the second install is a much shorter job than the first.
Events that send you back for a fresh copy
- A new machine arrives while the old one keeps working, so two computers need the terminal
- The operating system is reinstalled and everything held locally goes with it
- A second desk, at home or at work, needs the same account in front of it
- The program folder was moved, cleaned out or emptied, and the shortcut now opens nothing
- A phone is replaced or reset, so the mobile copy has to be pulled down again
- A machine is passed on to someone else and the terminal is taken off it before it leaves
What a repeat download changes and what it leaves alone
| Event | Fresh copy needed | What carries over untouched |
|---|---|---|
| New computer beside the old one | Yes, one copy per machine | Account number, server name and the closed-trade record |
| Operating system reinstalled | Yes, nothing local survives it | The account itself; none of it is reset by the wipe |
| Shortcut broken, folder moved or emptied | Usually faster than tracing the folder | Login details, which do not change with the copy |
| Phone replaced or factory reset | Yes, from the app store | The account, which is where the trade record is kept |
| Machine passed on to someone else | Only on the machine you keep | Everything except the chart layout that lived on it |
How many returns to expect
Counting the returns is more useful than trying to avoid them. A computer that lasts a few years, an operating system reinstalled at least once in that time, a phone on a shorter cycle of its own, and a second machine that joins the desk at some point: that is four or five fresh copies over the life of one account, with nothing having gone wrong at all.
None of it is a fault in the terminal. It is a local program on hardware you own, and hardware changes far more often than accounts do. Treating this page as a maintenance page rather than a one-off first step is the whole difference between a short job and an afternoon spent looking for credentials.
Fetch again, or repair what is there
When a shortcut stops working the instinct is to find out why. In practice a fresh copy usually wins on time: the file is small next to the effort of tracing where a folder went, and it starts from a known state instead of an unknown one.
The exception is the part of the setup that is genuinely yours. Chart layouts and any indicator you added by hand sit on the machine, not on the account, and they are the only thing worth rescuing before a computer is wiped or handed on.
What you do not repeat on the second download
- You do not open a second account. One set of credentials covers every copy of the terminal you install, on as many devices as you use.
- You do not repeat verification. It belongs to the account, not to the machine the account is read on.
- You do not choose a new server. The server name from the first setup is the one every later install asks for, and it stays available in the client area.
- You do not lose the trade record. Closed positions sit with the account and reappear as soon as the fresh copy is logged in.
- You do repeat one thing: the local layout. Charts, saved views and hand-added indicators live on the machine and leave with it.
Keep the account number and the server name somewhere that is not the machine itself, and a repeat download stops being a search operation.