Check CPU, RAM and disk use on Windows

Use Task Manager, Resource Monitor and a few PowerShell commands to find which program is using CPU, memory or disk.

  • Beginner
  • Windows VPS · Admin RDP
  • 2 min read

By RunRacks Team · Published

When a server feels slow, the first job is to find which resource is busy: CPU, memory (RAM), disk or network. Windows has everything you need built in.

Task Manager: the quick look

Inside your Remote Desktop session, right-click the taskbar and choose Task Manager (or run taskmgr). Click More details if you see the small view.

  • Processes tab: click the CPU, Memory or Disk column header to sort and see which program uses the most.
  • Performance tab: live graphs for CPU, memory, disk and network. A CPU line pinned near 100% or memory above about 90% for long periods points to the bottleneck.
  • Users tab: shows who is signed in or disconnected, and what each session is using.

Resource Monitor: more detail

Run resmon. The Disk tab shows which files are being read and written; the Network tab shows which programs talk to which addresses. This is how you find, for example, a backup job hammering the disk.

PowerShell checks

Top 10 processes by CPU time and by memory:

PowerShell
Get-Process | Sort-Object CPU -Descending | Select-Object -First 10 Name, CPU, @{n='RAM (MB)';e={[int]($_.WorkingSet64/1MB)}}
Get-Process | Sort-Object WorkingSet64 -Descending | Select-Object -First 10 Name, @{n='RAM (MB)';e={[int]($_.WorkingSet64/1MB)}}

Current CPU load and free memory:

PowerShell
Get-Counter '\Processor(_Total)\% Processor Time', '\Memory\Available MBytes'

Free disk space on each drive:

PowerShell
Get-PSDrive -PSProvider FileSystem | Select-Object Name, @{n='Free (GB)';e={[math]::Round($_.Free/1GB,1)}}, @{n='Used (GB)';e={[math]::Round($_.Used/1GB,1)}}

What to do with the result

  • One program uses all the CPU: check its settings, restart it, or update it. For trading terminals see Run several MetaTrader terminals.
  • Memory is always nearly full: close programs you do not need, reduce browser tabs, or move to a plan with more RAM on Pricing.
  • Disk is full: run Disk Cleanup (cleanmgr), empty old downloads and logs, or add space and extend the disk.

Next steps

Was this guide helpful?

Still stuck?

Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.

Troubleshooting

Fix Nginx 413 Request Entity Too Large

Nginx returns 413 Request Entity Too Large when an upload is bigger than client_max_body_size. Raise the limit for one site or the whole server, match PHP's limits, and test.

  • Beginner
  • Linux VPS
  • 5 min read

Troubleshooting

Is your ISP or router blocking port 12230? How to tell

Work out whether your internet provider, home router, parental controls or a proxy is blocking RDP port 12230, and collect the details support needs to help.

  • Intermediate
  • Windows VPS · Admin RDP
  • 5 min read