Track Windows 10 Pro Resources with Performance Monitor

When a Windows 10 Pro computer feels slow, the cause is often hidden behind a vague symptom: an application takes ages to open, the fan runs constantly, or files copy at an unexpectedly low speed. Performance Monitor, also known as PerfMon, gives you a clearer view by recording processor, memory, disk, network and system activity over time.

This built-in Windows tool is more useful than a quick glance at Task Manager when you need to identify a pattern. It can show whether a slowdown occurs during a particular application, at a regular time of day, or whenever your internet connection, storage drive or security software is busy. The following steps are suitable for everyday users in Australia, whether the PC is at home in Perth, in a small office in Melbourne, or connected through an NBN service in regional Queensland.

Open Performance Monitor and understand its layout

Press Windows key + R, type perfmon, and press Enter. You can also open the Start menu and search for Performance Monitor. Windows 10 Pro may ask for administrator permission when you create a data collection set or change certain settings, so sign in with an account that has suitable rights.

The main window contains several areas. Monitoring Tools includes the live Performance Monitor graph, while Data Collector Sets can record information for a longer period. Reports stores the results of those recordings. The graph initially contains a processor counter, but you can add other measurements by selecting the green plus symbol.

The display can look technical at first because counters use terms such as instances, samples and objects. An object is a category of activity, such as Processor, Memory, PhysicalDisk or Network Interface. A counter is a specific measurement within that category, such as processor time or available memory. An instance identifies the individual processor core, drive, network adapter or application involved.

Add the counters that reveal a slowdown

Right-click the graph and select Add Counters. From the available list, choose a small group of relevant counters rather than adding everything. A useful starting set includes Processor % Processor Time, Memory \Available MBytes, Memory \Pages/sec, PhysicalDisk % Disk Time, PhysicalDisk \Avg. Disk Queue Length, and Network Interface \Bytes Total/sec.

For the processor, select the _Total instance to view overall CPU use. You can also select individual cores if you suspect one older application is placing an uneven load on the system. Sustained processor usage close to 100 per cent usually indicates that a programme is consuming CPU time, although short spikes while opening a browser or installing an update are normal.

Memory counters help distinguish a genuine RAM shortage from a processor problem. Available MBytes shows how much physical memory is immediately available, while Pages/sec indicates activity involving virtual memory. Frequent paging can occur when Windows is moving data between RAM and the page file. A computer with 4 GB of memory may reach this point sooner than a system with 8 GB or 16 GB, especially when many browser tabs, Teams calls and large spreadsheets are open.

Disk activity needs careful interpretation. A high % Disk Time value can mean the drive is busy, but it does not automatically prove that the disk is failing. An older mechanical hard drive may remain active for longer than a solid-state drive during the same task. A growing disk queue, slow response from File Explorer and frequent paging together provide stronger evidence of storage-related pressure.

Record activity with a data collector set

The live graph is helpful when you are watching a problem happen, but some faults appear only after several hours. To record them, expand Data Collector Sets, right-click User Defined, choose New, and select Data Collector Set. Give it a clear name such as Evening slowdown, select Create manually, and continue to the performance counter option.

Add the counters that match the problem and set a sample interval. A five-second interval provides detailed information but creates a larger log. Fifteen or thirty seconds is usually enough for general troubleshooting and is less demanding on the computer. Save the output in a folder with plenty of free space, such as a dedicated folder on the system drive.

Set a practical stop condition, such as a duration of 30 minutes or one hour. If the issue happens while a household member is gaming, streaming or using a school account, begin the recording shortly beforehand. For families sharing a Windows computer, parental controls can help identify which account or usage period matches the performance complaint, while Performance Monitor shows the technical load underneath it.

Start the collector set from the right-click menu and reproduce the problem if possible. When finished, stop it and open Reports, followed by User Defined and the name of your recording. Windows will generate a report containing the selected counters and system information. Compare the time of a visible slowdown with the highest readings instead of judging the entire report by a single peak.

Read the results without jumping to the wrong cause

A performance reading has meaning only in context. A CPU level of 90 per cent while exporting a video may be expected, whereas the same level while the computer is idle deserves investigation. Likewise, a disk that reaches 100 per cent for a few seconds during Windows Update is less concerning than a drive that remains at full activity while applications freeze.

Use the counter values to form a sequence of events. If available memory falls sharply, pages per second rises, and disk activity increases at the same time, Windows may be relying heavily on virtual memory. If processor time rises while memory and disk readings remain moderate, check which application or service is responsible in Task Manager. If the network counter shows traffic during an unexplained slowdown, investigate cloud synchronisation, backup jobs, large downloads or security scans.

Network readings are especially useful when a computer seems slow during a download. Performance Monitor shows traffic handled by the selected network adapter, not the advertised speed of an NBN plan. A busy connection in a Sydney apartment may reflect several devices sharing Wi-Fi, while a rural connection outside Toowoomba may have different latency and bandwidth limits. Test the same task at another time before blaming Windows or the local PC.

The System object can provide additional clues. Counters such as Processor Queue Length, Context Switches/sec and System Calls/sec are more advanced, but they can help when a machine feels busy without an obvious application. Add them only after checking the basic counters, because a crowded graph makes it harder to see the relationship between symptoms and resource use.

Turn findings into practical fixes

Once you identify the busiest resource, make one change at a time. For high CPU usage, close unnecessary applications, review startup entries in Task Manager and check whether a scan, installer or Windows maintenance task is running. Avoid ending unknown processes simply because their names look unfamiliar. Search the process name using a trusted source before disabling anything.

For low memory, close unused browser tabs and applications, then restart the computer if it has been running for many days. Check whether a particular programme has a steadily increasing memory footprint. If the same workload regularly exhausts available RAM, adding compatible memory may be more effective than repeatedly changing virtual memory settings.

For storage pressure, keep adequate free space on the system drive and remove temporary files through Settings > System > Storage. Confirm that Windows is fully updated, but schedule large updates outside important work periods. If a mechanical drive produces unusual noises, reports errors, or remains slow after software checks, back up personal files before considering replacement with an SSD.

High network use may come from cloud storage, game launchers, system updates or backup software. Pause or schedule these activities when practical, and test whether an Ethernet connection improves consistency compared with Wi-Fi. In the Australian market, routers supplied by providers such as Telstra, Optus or TPG can have different menus and firmware, so use the model’s support documentation when checking wireless channels or device limits.

Performance Monitor will not explain every visual or input fault. If applications appear normal but the pointer vanishes, freezes or behaves differently in one programme, review this guide to fix the missing cursor before treating the symptom as a processor problem. Display drivers, application compatibility and pointer settings can create issues that resource counters cannot detect.

Keep a short record of the date, application, counter values and action taken. This is particularly useful for a work PC in Adelaide or a home computer in Brisbane where the problem may occur only during hot afternoons, scheduled backups or peak household internet use. Repeat the same test after each change so you can see whether the system genuinely improved.

Open Performance Monitor the next time Windows 10 Pro becomes slow and begin with a focused set of counters. Record the activity if the fault is intermittent, compare the timing of spikes with what you were doing, and apply measured fixes rather than guessing. A small, repeatable log can turn an unexplained slowdown into a specific storage, memory, processor or network issue that is much easier to resolve.