A computer feature or peripheral that has completely stopped should be separated into driver, permission and physical-connection layers before assuming component 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 Device Manager or System Information for whether the hardware is even detected, and whether an error code is shown. 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. Test the peripheral on a different port or user account, and test a different peripheral on the same port. 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. Reinstall or roll back the driver, or grant the missing app permission.
Verify and stop safely
ReversibleConfirm the feature works after a full restart in at least two different applications. Back up before recovery or firmware changes and keep power connected during installation.
Evidence ledger
Sources behind this answer
Exact questions