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 Update installation, first record the KB/error, free space and update history before running the troubleshooter.
What this covers
- Windows Update installation with this exact failure state
- Diagnosis across Microsoft service versus storage, network, component health and driver conflict
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: download, stage and restart into a compatible signed update.
Isolate the component boundary
ReversibleRecord the KB/error, free space and update history before running the troubleshooter. Compare the same task with unnecessary startup programs and background processes closed. Boundary to separate: Microsoft service versus storage, network, component health and driver conflict.
Correct only the proven cause
ReversibleRepair the specific update component, driver or space issue; pause only temporarily. 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. Back up before recovery or firmware changes and keep power connected during installation.
Evidence ledger
Sources behind this answer
Exact questions