A computer running slow for one task points to a specific resource — disk, memory, background process or thermal throttling — not a general failure. For Windows File Explorer, first open a local known folder, disable preview for one test and disconnect unavailable network paths.
What this covers
- Windows File Explorer with this exact failure state
- Diagnosis across local disk versus network/cloud path, preview handler and storage health
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleCheck Task Manager or Activity Monitor for CPU, memory and disk usage while the slow task runs, and note fan noise or heat. Expected behavior: enumerate folders and storage without hanging on one path or extension.
Isolate the component boundary
ReversibleOpen a local known folder, disable preview for one test and disconnect unavailable network paths. Compare the same task with unnecessary startup programs and background processes closed. Boundary to separate: local disk versus network/cloud path, preview handler and storage health.
Correct only the proven cause
ReversibleRepair the failed extension/path or storage device rather than resetting Windows. End or disable the resource-heavy process, free disk space, or improve cooling and airflow.
Verify and stop safely
ReversibleRepeat the same timed task with the fix applied and background load controlled. Stop for drive errors, clicking, disconnects or the only copy of important data.
Evidence ledger
Sources behind this answer
Exact questions