Quick Answer: The update_engine is the background system daemon that downloads and applies ChromeOS updates; when it fails, you’ll typically see an update that won’t progress past a percentage, silently fails and reverts, or an “update failed” notification with no clear code. Restarting, freeing up storage, and forcing a manual check clear the large majority of cases.
What the Update Engine Does (and Why It Fails)
- ChromeOS keeps two system partitions and updates the inactive one in the background, then switches to it on restart; if that switch or the download itself is interrupted, the update_engine can get stuck in a broken state
- Low free storage space can prevent the update from downloading or staging correctly
- A weak or dropping Wi-Fi connection during a large update download is one of the most common failure points
- On managed (school or work) Chromebooks, an admin policy can block or delay specific updates, which looks identical to a stuck update engine from the user’s side
- Corrupted update state left over from a previous failed attempt can block new updates from starting cleanly
How to Fix It
Step 1: Restart the Chromebook
A simple restart lets the update_engine daemon reset its state and often clears a stuck download or a failed partition switch on its own.
Step 2: Check your Wi-Fi connection
Updates can be a gigabyte or more. A weak or unstable connection is a common cause of repeated failures; connect to a stronger network if possible before retrying.
Step 3: Free up storage space
The update needs room to stage the new system image before switching over. See Chromebook storage full? Free up space if you’re anywhere near your storage limit.
Step 4: Force a manual update check
Go to Settings, then About ChromeOS, then Check for updates. See how to update ChromeOS manually for the full walkthrough, including what to do if the check itself hangs.
Step 5: Powerwash as a last resort
If updates repeatedly fail after ruling out storage and network, a factory reset clears any corrupted update state. See how to Powerwash a Chromebook; back up your files first since local data will be erased.
Step 6: Use the recovery utility if the device won’t boot normally
If a failed update leaves the Chromebook unable to start, see how to create a ChromeOS recovery USB to reinstall the system image directly.
Still Not Fixed?
If this is a school or work Chromebook, check with the IT admin before troubleshooting further; the update may be intentionally held back by policy, which looks identical to a stuck update from the user’s side. If it’s a personal device and Powerwash and recovery both fail, the Chromebook may have reached its AUE (Auto Update Expiration) date and can no longer receive new updates at all.
FAQ
Why does the update bar freeze at a specific percentage?
This is usually the download stalling due to a network drop, or the staging step waiting on free storage that isn’t available; both are addressed in steps 2 and 3 above.
Will Powerwash delete my downloaded update along with everything else?
Yes, Powerwash resets ChromeOS to factory state, which also clears any corrupted or partially downloaded update data, letting the device start the update process cleanly afterward.
Could my Chromebook just be too old to update?
Yes. Every Chromebook has an AUE date after which Google stops shipping new ChromeOS versions to it entirely, even though the device keeps working with its last supported version.
