A computer problem starting right after a Windows or macOS update, a new peripheral or a software install should be checked against that specific change before a factory reset. 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
ReversibleNote the exact update version or newly installed software, and confirm the prior working state. 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. Uninstall the new software or roll back the update in a controlled test, where the OS supports it. 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. Apply the vendor's fix for the update, or reconfigure the setting the new software changed.
Verify and stop safely
ReversibleConfirm stable operation with the update or new software present for one full session. Back up before recovery or firmware changes and keep power connected during installation.
Evidence ledger
Sources behind this answer
Exact questions