List of Articles Icon

Knowledge Base

Guides and answers for your VPS, the client area, and billing

My Windows VPS is slow. How do I find out why?

What this is

"Slow" on a Windows VPS is one of three different problems, the path to it, the machine itself, or your expectations of the plan size, and each has a quick test. Same method as the Linux version, Windows tooling.

Step 1: is it the server, or the connection to it?

An RDP session that feels laggy, choppy screen, delayed typing, while the server itself is idle is a network path symptom, not a server one. The discriminator: open Task Manager on the VPS, if CPU/memory/disk are quiet while the session feels bad, test the path, ping.pe from outside, and the network problems guide with mtr. Long international routes make RDP feel heavy at peak hours with nothing wrong on either end.

If things are slow on the server (apps take forever, disk grinds), continue.

Step 2: Task Manager, then Resource Monitor

Task Manager (Ctrl+Shift+Esc) → Details tab, sort by CPU, then by Memory, the consumer is usually staring at you. For the deeper view, Resource Monitor (resmon, or the link at the bottom of Task Manager's Performance tab) breaks out disk and network per process, which catches the "CPU is fine but the disk is pinned" cases.

The usual suspects

  • TiWorker.exe / Windows Modules Installer grinding CPU and disk: patch-day servicing, legitimate, let it finish. The full story (and the pending-reboot state) is in Windows Updates.
  • MsMpEng.exe (Microsoft Defender) busy: a scheduled scan. Normal in bursts; if it's constantly hot, exclude your heavy data folders (databases, backup targets) from real-time scanning rather than disabling Defender, that's the sanctioned tuning.
  • A process you don't recognize at 100%, around the clock: assume a cryptominer until proven otherwise, which means a compromise. Don't just kill it; the recovery doctrine applies on Windows exactly as on Linux.
  • Memory pressure: Windows Server itself is comfortable at 4 GB, but Windows plus a real workload wants 8 GB and up, and an over-committed box pushes into the pagefile, which converts RAM shortage into constant disk grind (visible as high disk activity on pagefile.sys in Resource Monitor). The fix is less workload or more plan; shrinking the pagefile just converts slowness into crashes.
  • Disk full produces spectacular, misleading slowness on Windows too, ten seconds to rule out: the Windows disk guide.

"What even is this process?"

For anything ambiguous, Microsoft's free Process Explorer (Sysinternals) is Task Manager with answers: full paths, signing info, and a built-in VirusTotal check per process (Options → VirusTotal.com → Check). Pasting a suspicious process name and path into an AI chatbot is also a fast sanity check, it knows the legitimate Windows processes cold.

History, and when to escalate

Your VPS's Graphs hold the long view, does the slow period line up with a CPU/disk plateau, or are the graphs flat (which points back at the network path)? If you've localized something you can't explain, the ticket recipe applies: what you measured, when, and what Task Manager showed, in your own words.

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 sits at the top of Task Manager while it's slow,
  • when it started, and whether it lines up with anything on the Graphs.
  • "Why is my Windows VPS so slow?"
  • "What is TiWorker.exe and why is it using all my CPU?"
  • "Why is MsMpEng using CPU on my server?"
  • "How much RAM does a Windows VPS need?"
  • "How do I check what's using disk on Windows Server?"
  • "Is my RDP lag the server or my connection?"
Last reviewed: 2026-07-02