Windows Updates on your VPS
What this is
How updating works on a Windows Server VPS, and the two realities worth knowing in advance: updates are not optional on an internet-facing Windows machine (unpatched RDP/SMB holes are how these servers get owned in bulk), and the friction people actually feel, slowdowns and surprise reboots, is a reboot-management problem, not a reason to disable updating.
The rhythm
Microsoft ships the main security rollup monthly (Patch Tuesday, the second Tuesday), plus occasional out-of-band fixes for actively exploited holes. Windows Server downloads and installs these automatically by default, leave that on, and manage the two side effects below instead.
"My VPS is slow today", patch-day behavior
During and after update installation, TiWorker.exe (Windows Modules Installer) and the update service legitimately eat CPU and disk for a while, on smaller plans, noticeably. It finishes on its own; check Task Manager and if TiWorker is the one working, let it, interrupting servicing is how installs corrupt. If it's still grinding many hours later, a reboot usually completes what it's waiting on.
The pending-reboot state
Updates often finish only at the next restart, and a server that sits "pending reboot" for weeks accumulates weirdness: things half-installed, services misbehaving, the next update refusing to start. Settings → Windows Update tells you when a restart is pending, do it on your schedule (a quiet hour, after checking your services start automatically) rather than letting it happen on Windows' schedule. Active hours (Settings → Windows Update → Advanced) tells Windows when not to auto-restart; set it to your working window.
Driving updates by hand
- GUI: Settings → Windows Update → Check for updates.
- sconfig (in a terminal): the classic Server text menu, option 6 handles updates, handy over a laggy session.
- PowerShell: the community-standard PSWindowsUpdate module (
Install-Module PSWindowsUpdate, thenGet-WindowsUpdate/Install-WindowsUpdate) gives you scripted control, including update-then-reboot in one planned maintenance window.
What not to do
Don't disable the Windows Update service to "stop the interruptions", the interruptions move from scheduled to catastrophic, just later. Every mass-exploited Windows worm of the last decade feasted on servers patched months behind. Manage the reboot timing, keep the updates.
Still need help?
You can open a support ticket. So we can help on the first reply, it's worth mentioning:
- the VPS hostname or IP,
- what the Windows Update page shows (pending, failed, or a specific KB),
- whether a reboot has been pending, and for how long.
Related questions
- "Why is my Windows VPS slow after updates (TiWorker)?"
- "How do I control when my Windows VPS reboots for updates?"
- "How do I check for updates on Windows Server?"
- "Is it safe to disable Windows Update on a VPS?"
- "What is a pending reboot and why does it matter?"