A computer feature or peripheral that has completely stopped should be separated into driver, permission and physical-connection layers before assuming component failure. For ChromeOS update, first check version, update policy/support date and free space on stable Wi-Fi.
What this covers
- ChromeOS update with this exact failure state
- Diagnosis across Google update service versus storage, network, managed policy and support lifetime
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 and apply the supported channel build with enough storage and power.
Isolate the component boundary
ReversibleCheck version, update policy/support date and free space on stable Wi-Fi. Test the peripheral on a different port or user account, and test a different peripheral on the same port. Boundary to separate: Google update service versus storage, network, managed policy and support lifetime.
Correct only the proven cause
ReversibleFree space, change to the approved channel or contact the administrator. 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. Do not Powerwash before local Downloads are backed up.
Evidence ledger
Sources behind this answer
Exact questions