Measure a Task Manager baseline Guided Practice

Lab brief

Know the problem and the evidence you need

The situation

A Windows PC feels slow, but the learner does not know whether CPU, memory, disk, startup load, or one application is responsible.

Your finished record

An idle-versus-slowdown resource comparison

Capture idle and active readings and identify the resource that changes most during the slowdown.

Why this matters

Comparing idle and problem-state readings separates a real resource bottleneck from a slowdown caused by drivers, heat, storage health, or the network.

Safety and setup

Prepare before changing anything

Have this ready

Save open work before reproducing freezes or heavy workloads.
Do not end Windows processes or disable security software during this lab.
Use an administrator account only if Task Manager requests elevation.

Field checks

Run the lab

Complete one check at a time. Record the evidence before moving on.

0 of 5 checks complete

Check 1 of 5 Open Task Manager Do thisUse Ctrl+Shift+Esc, select More details when shown, and open Processes. Record thisThe Processes tab displays overall and per-process CPU, memory, and disk usage.
Check 2 of 5 Capture an idle baseline Do thisWait two minutes and record total CPU, memory, and disk percentages. Record thisA stable idle reading recorded before reproducing the slowdown.
Check 3 of 5 Reproduce the slowdown once Do thisPerform the smallest action that reliably triggers the problem. Record thisThe symptom appears without adding unrelated workload.
Check 4 of 5 Sort one resource at a time Do thisInspect CPU, Memory, and Disk columns and record the top process for each. Record thisA short table of the leading process for each resource during the symptom.
Check 5 of 5 Compare idle and active readings Do thisIdentify which resource and process changed most. Record thisOne evidence-backed candidate bottleneck, or a conclusion that resource usage did not materially change.

Interpret results

Match the evidence to the next action

If you seeNext action

One application rises with the symptom

Update, repair, reduce its workload, or test it in isolation before changing Windows.

Disk remains near 100 percent with low throughput

Check free space and drive health before running repair commands.

Memory remains above 85 percent

Reduce startup/background load and compare committed memory before adding hardware.

No resource changes materially

Continue with Event Viewer, temperature, power, or network evidence instead of forcing a performance diagnosis.

Decision point

Choose the next action

Choose one measured bottleneck and run one reversible test; return to the same workload to verify the result.

Completion

Confirm the evidence you produced

Finished record: An idle-versus-slowdown resource comparison

I recorded idle CPU, memory, and disk percentages.
I recorded the top process during the slowdown.
I selected one measured bottleneck rather than guessing.

I recorded the evidence and selected a next action.