Slow computer: a 10-minute bench triage
When a computer feels slow, first pin down when the delay occurs, then compare that report with read-only views of startup impact, free space, memory pressure, update history, disk status, and heat. Record observations during the customer’s workload where possible. Ten minutes is a focused triage window, not a diagnosis or repair commitment.
Updated November 11, 2026
- Ask when the slowdown happens Record whether it starts at sign-in, during one app, on battery, or after the computer has been running. Ask what changed and whether the problem is constant or intermittent.
- Review startup items Use the operating system’s built-in startup or login-items view. Note enabled items and their displayed impact, but do not disable anything during this read-only pass.
- Check available storage Open the built-in storage view and note available space. If it is low, inspect the largest visible categories or folders without moving or deleting customer files.
- Look for memory pressure Use the built-in activity or task view while the reported workload is open. Record memory pressure and the busiest applications; a single snapshot may not explain an intermittent complaint.
- Review pending updates and disk status Read update status and history, then check the built-in disk health or storage status page if available. Record warnings as shown. Do not start repairs or infer a failing disk from one unclear reading.
- Check for heat and stop conditions Ask whether heat or fan noise accompanies the slowdown and check for blocked vents or unusual warmth without opening the device. Note the condition and stop if it is unsafe to handle.
What belongs in a ten-minute first pass?
Keep the intake focused. Ten minutes is a triage window, not a promise to find every cause. Ask when the delay starts, what the customer was doing, and whether it happens each time. Record the operating system, start date, and recent changes. Treat “sign-in takes longer” as a symptom, not a diagnosis.
What should I check first?
Read enabled startup or sign-in items and any displayed impact rating. An unfamiliar name is not proof an item is unwanted, so leave the list unchanged. Check free space and storage categories in the system view. Inspect large folder names and sizes only; do not delete files during triage.
How can I read memory, updates, disk, and heat?
During the reported workload, read memory pressure and the busiest applications in the built-in activity or task view. Record what is running because an idle snapshot may differ. Read update status and history without starting an install. Check the built-in disk health readout and copy its status without guessing at an unclear label.
Ask about heat and fan noise. Look for blocked vents or unusual warmth without opening the case. Stop if equipment is hot, damaged, swollen, wet, or otherwise unsafe.
When should I stop?
Stop if the built-in disk view warns of a problem, the computer becomes unstable or unsafe to handle, or important work is unsaved. Record the exact readings alongside when the slowdown occurs, then hand off for review. Do not start a repair, interrupt work, or change startup settings as part of this triage.
A technician can use CommandGate to collect read-only findings for the reported slowdown and review any proposed steps separately before deciding whether to proceed.