Exness Download for PC — Shutting the Terminal Down Properly · South Africa
What to settle before the desktop program closes, what the trading server keeps running while the computer is off, and what to check when the machine goes off without asking.
Open Exness Account →Closing the Exness desktop terminal does not close anything on the account. Positions, the stop and take-profit levels attached to them and pending orders sit on the trading server, so they stay live while the computer is off; only what lived inside the window — alerts, half-written orders, the connection itself — ends with it. A clean sign-off is therefore a short review of what is being left running, not a shutdown procedure.
What survives the computer being switched off
- An open position is held on the Exness trading server, not inside the program on the desk — closing the terminal, or losing power, leaves it open.
- A stop loss, a take profit or a pending order the server has accepted stays armed while the computer is off; none of them needs the window to be open.
- Anything that exists only inside the running window — a price alert, an order half-typed into a dialog — ends when the window does.
- Closing the window is not signing out: a terminal told to remember the account can reopen straight into it.
- A sudden shutdown changes nothing on the account record: the server keeps what was open, what closed and what it charged while the machine was dark.
- MetaTrader 4, MetaTrader 5 and the browser platform all end the same way on a computer — the window closes and the account carries on.
- Nothing on the account is closed by shutting the computer down; a position ends only on an instruction the server accepts.
Where each thing was left when the machine goes off
| What you left behind | Held by | State while the computer is off |
|---|---|---|
| An open position | The Exness trading server | Still open, still moving with the market |
| A stop loss or take profit on it | The Exness trading server | Still armed and still able to close the position |
| A pending order that has not triggered | The Exness trading server | Still waiting for its price |
| A price alert set inside the terminal | The program on that computer | Silent until the program runs again |
| An order half-typed into a dialog | The program on that computer | Gone |
| The account it was signed in to | The program on that computer | Remembered, unless the sign-in details were cleared |
Why closing the window changes nothing on the market
The program on the desk is a view onto an account that is kept somewhere else. Orders are sent from it and quotes arrive into it, but the position itself is a record on the Exness trading server, and that record does not depend on a window being open. It is why the same account looks identical when it is opened again on a different computer: nothing of substance was stored in the first one.
The consequence catches people out in both directions. A position left open at the end of the evening is still open in the morning, whatever happened to the machine in between. And a protective level attached to that position is enforced by the server as well, so it can close the trade at three in the morning with the computer unplugged.
What does end with the window is everything the program was doing locally. An alert set to sound at a price is a reminder held by that installation and nothing more; an order typed into a dialog but never sent was never anywhere else. Neither reaches the account, and neither survives the close.
Closing the window is not the same as signing out
There are two different acts here and usually only one of them is performed. Closing the program ends the connection between that computer and the trading server. Signing out removes the account from the program, so that starting it again asks for the account number, the password and the server before anything at all is shown.
On a machine only you use, the difference rarely matters. On a shared or borrowed one it matters completely: a terminal told to remember the account opens straight into it, and whoever starts the program next is looking at your open positions without having been asked for anything.
The browser side of the same visit has its own door and its own lock, and closing the program does not close it. Leaving a computer means ending both, because neither one ends the other.
When the machine goes off without asking
A power cut, a battery that runs out and a machine that suspends itself all produce the same result on the account side: nothing. The session stops. Positions carry on, the levels attached to them carry on, and the record of what happened while the screen was dark is written by the server rather than by the terminal that was watching it.
The difference is on the computer. A program closed from its own menu writes its state out before it goes; a program that loses power does not, so the next start can come back without whatever you were in the middle of. That is an inconvenience about the machine, not a change to the account.
The case worth treating seriously is a machine left running on purpose — one you expected to keep watching the market. If it stopped, it stopped silently, and the only way to learn what it stopped in the middle of is to sign in again and read what the server has, rather than to trust the first thing the screen shows on the way back up.
Coming back: what to compare on the next start
The first screen after signing in again is not the chart. It is the list of what is open: each position, the level attached to it and the orders still waiting. Against that list you compare what you remember leaving, and every difference is something the server did while the machine was off — a level that was hit, an order that triggered.
The second thing is the pair of numbers that says where the money is. Balance is what has settled; equity is that balance plus whatever the open positions are currently worth. If the two have moved apart since last night, the movement lives inside a position rather than in the settled account, and the position list is where to read it.
The account record settles the rest. Anything that closed while nobody was watching is listed there with the time it happened, which is quicker and more reliable than reconstructing the night from memory.
A sign-off in order
- Read the list of open positions and decide, one at a time, which of them should still be open when nobody is watching.
- Check that every position being left open carries the protective level you meant it to carry, because that level is enforced by the server and not by the window you are about to close.
- Look at the pending orders and cancel the ones that were meant for today only — an order left with the server will trigger while the machine is off.
- Note the balance and the free margin, so that the next start has a number to be compared against rather than a memory.
- Close the program from its own menu instead of cutting the power, so the session ends rather than merely stops.
- If the computer is shared or borrowed, clear the saved sign-in details and close the browser session before you stand up.
Nothing in this list closes a position. Ending a position is a separate instruction, and the terminal has to be open to give it.
Two ways a session ends
| What was left | Closed from the menu | Power cut or crash |
|---|---|---|
| Open positions | Untouched | Untouched |
| Levels attached to them | Still armed | Still armed |
| Pending orders | Still waiting | Still waiting |
| Alerts set inside the terminal | Silent until the next start | Silent until the next start |
| The program's own state | Written out before it goes | Not written |
| What you know about the account | What you checked before closing | Whatever the server can tell you afterwards |
The two columns differ only in what happens to the computer. The account side of the table is identical, which is the whole point.