Skip to main content
When Windows Server is slow, find which resource is the bottleneck before changing anything. Open Task Manager > Performance (or run resmon) and check CPU, Memory and Disk. CPU near 100 percent points to a busy process, memory near full points to too little RAM or a leaking program, and a disk at high active time or latency points to heavy I/O or a full C: drive. Updates installing in the background are a common temporary cause.

​
Before you start

  • If RDP is too slow to use, sign in through the VNC console on a VPS.
  • On a VPS, compare with the panel graphs in monitor VPS resource usage. They show the load from outside Windows.
  • Note whether the slowness is constant or happens at certain times. Scheduled backups, scans and updates cause regular slow periods.

​
How to find the bottleneck

Run this in PowerShell to take five samples, two seconds apart:
Then work through the matching cause below.

​
Cause 1: one process uses most of the CPU

Check: Task Manager > Details, sorted by CPU. Fix: see fix high CPU usage on Windows Server.

​
Cause 2: not enough free memory

Check: Task Manager > Performance > Memory. If In use is close to the total and Available is small, Windows starts paging to disk and everything slows down. Find the biggest users:
Fix:
  • Restart or reconfigure the program at the top. SQL Server, for example, claims memory up to its Maximum server memory setting, which by default is effectively unlimited; set a limit in Server Properties > Memory.
  • Sign out disconnected RDP sessions you don’t need: query user lists sessions with their ID and state, and logoff 2 signs out session ID 2.
  • If memory use keeps growing until a restart, the program probably leaks memory; update it or contact its vendor.
  • If normal use fills the RAM, the server needs more memory.

​
Cause 3: the disk is busy or slow

Check: run resmon and open the Disk tab to see which processes read and write the most. Compare with the % Idle Time and Avg. Disk sec/Transfer values above. Fix:
  • Move heavy jobs (backups, Defender scans, database maintenance) to quiet hours.
  • If paging causes the disk load, fix the memory problem first (cause 2).
  • If the disk is nearly full, see free up disk space on Windows Server.

​
Cause 4: updates or scans are running

Check: TiWorker.exe or Antimalware Service Executable near the top of Task Manager, or a pending restart in Settings under Windows Update. Fix: let them finish and restart if Windows asks. A server that hasn’t restarted for a long time with pending updates often feels slow. See Windows Update stuck or failing.

​
Cause 5: it only feels slow over Remote Desktop

Check: the counters above look normal, but the RDP session is laggy. Fix: the network path is the problem, not Windows. In Remote Desktop Connection, click Show Options and lower the settings on the Display and Experience tabs. Test the network with diagnose network latency.

​
How to check it worked

Run the Get-Counter command again during the time the server used to be slow. All four counters should stay inside the healthy ranges.

​
Frequently asked questions

​
Should I restart the server when it is slow?

A restart clears the symptom but not the cause. Note the top processes in Task Manager first, then restart if you must.

​
Can I record performance over a whole day?

Yes. Use a Performance Monitor data collector set; see monitor Windows Server performance.

​
Is the slowness caused by an attack?

High CPU from an unknown process, or thousands of failed logins, can be. Check failed login attempts and protect RDP from brute-force attacks.

VPS and dedicated server guides

Every guide in this section.

High CPU usage

Find and fix busy processes.

Monitor performance

Long-term performance logs.

Free up disk space

When C: is nearly full.

Event Viewer

Errors behind the slowdown.
Checked against Microsoft Learn: Troubleshoot issues using Performance Monitor, Troubleshooting high CPU usage, Troubleshoot Hyper-V virtual machine performance, Get-Counter , Get-Process and SQL Server memory configuration on 4 November 2026. Commands were not tested on a live Windows server for this page.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to upgrade your hosting? Use code KB20 at checkout for 20% off your first order!
Last Updated: November 2026