When a computer function works in another app, user account or port, keep the repair inside the failing context. 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
ReversibleName the failing app, user account, port or peripheral and one that still works. 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. Swap only the app, account, cable, port or user profile while keeping the computer unchanged. 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. Repair the isolated app, user profile, driver binding or physical path.
Verify and stop safely
ReversibleRetest both contexts after sign-in and one cold restart. Do not Powerwash before local Downloads are backed up.
Evidence ledger
Sources behind this answer
Exact questions