Windows VPS: updates and restarts
A Windows restart interrupts ISA Terminal. While the terminal is closed, bots cannot manage trading. On a server used around the clock, configure update notifications and choose your maintenance time.
Choose a mode
Windows Server 2016 and later: mode 7
Updates download automatically. Windows notifies you before installation and requests a restart afterwards
Mode 2: PowerShell below
Windows notifies you before downloading and installing updates
This changes Windows Update behavior. Install security updates during planned maintenance.
If Windows already says a restart is required, plan maintenance first. Changing the mode does not cancel a pending restart. Organization or VPS provider policies may impose additional deadlines and rules.
Option 1. Windows Server policy settings
For Windows Server 2016 and later, Microsoft recommends 7 — Notify for install and notify for restart.
On the server, open Start, find
gpedit.mscand run the Local Group Policy Editor as administrator.Go to Computer Configuration → Administrative Templates → Windows Components → Windows Update. On some versions, the setting is inside Manage end user experience.
Open Configure Automatic Updates.
Record the previous policy state and selected mode.
Select Enabled, choose 7 — Notify for install and notify for restart, then click Apply.
Open PowerShell as administrator and run:
gpupdate /forceIf the editor or mode 7 is unavailable, use the next option or ask your VPS provider.
Option 2. PowerShell: notify before download
Open PowerShell on the server running the terminal: Start → PowerShell → Run as administrator.
Check the current values and keep the result, for example in a screenshot:
If the values do not exist, there may be no output. Record whether AUOptions was absent or its previous value.
Paste the entire block and press Enter:
The existence check is important: New-Item -Force on an existing registry key can clear its values. This version creates the key only if absent, then sets AUOptions and refreshes Group Policy.
Verify the result
Repeat the value-check command. Expect AUOptions : 2 for the PowerShell option, or AUOptions : 7 for Server mode 7.
Open Settings → Windows Update and check the status. On Windows Server the route may be Update & Security → Windows Update. A notice that some settings are managed by an organization can also result from a local policy.
The registry value confirms it was saved, not that every possible restart is prevented. If it changes back, the setting has no effect, or NoAutoUpdate is already 1, ask your administrator or provider to review effective policies. Also check for restarts scheduled in the VPS control panel.
Windows active hours do not cover continuous 24/7 operation. An open or disconnected RDP window is not a substitute for update configuration.
Update the server during maintenance
Choose a time when you can personally check the server after restarting.
Stop bots and explicitly decide what to do with open positions. A stopped bot does not manage a retained position.
Check positions and active orders on the exchange. A “stopped” status alone is insufficient.
Close ISA Terminal, install Windows updates and restart as required.
Reconnect, sign in to Windows and open ISA Terminal.
Check connections, balance, positions, orders and logs. Resume the required bots and verify their status. Do not assume everything restarts automatically.
Restore the previous setting
If you used the policy editor, restore the recorded state and run gpupdate /force.
If you used PowerShell and AUOptions did not previously exist, remove only that added value:
If it existed, restore it using the configuration command with the previous number instead of -Value 2. Do not delete the entire Windows Update key. Check update settings and scheduled restarts afterwards.
Sources
Last updated