# Stop Factory Resetting Your Chromebook: How to Fix the 'Couldn't Update' Error > Resolve the 'Couldn't update your Chromebook' error by checking your Auto Update Expiration date, network restrictions, and ChromeOS administrator policies. - Canonical URL: https://coreiten.com/en/article/stop-factory-resetting-your-chromebook-how-to-fix-the-couldnt-update-error - Language: en - Section: ChromeOS - Author: Sami - Published: 2026-09-17T18:02:17+03:00 - Modified: 2026-09-17T18:02:17+03:00 - Publisher: CoreITen (https://coreiten.com) - Keywords: Couldn't update your Chromebook, ChromeOS, Google Play Store, Android, Powerwash ## Summary When your Chromebook says it cannot update, avoid a factory reset until you check if the device has actually reached its expiration date. - Google provides ten years of updates for ChromeOS devices, but the countdown starts from the platform's original release date rather than the purchase date. - Users can find their final update month by navigating to Settings, selecting About ChromeOS, and opening Additional details. - Chromebooks released before 2021 that qualify for extended updates will permanently lose Android support and the Google Play Store if that toggle is enabled. - Users can check for network or administrator restrictions by typing chrome://policy into the browser address bar. - Wiping an expired Chromebook with a Powerwash or USB recovery will not change its expiration status and will only delete local data. **Why it matters:** Understanding these ChromeOS update rules prevents users from unnecessarily wiping their devices or losing Android apps due to hardware expiration. --- When a Chromebook displays the "Couldn’t update your Chromebook" error, the most common culprit is not a broken Wi-Fi connection, but an expired support lifecycle. ChromeOS users encountering this generic failure message can save their local data from unnecessary factory resets by identifying which of the four distinct causes is blocking the download. The operating system uses the exact same alert for network blocks, administrator restrictions, stalled downloads, and permanent hardware expiration. Google provides ten years of updates for ChromeOS devices, but that countdown begins on the platform's original release date, not the day the hardware was purchased. This means second-hand buyers often encounter the expiration block much sooner than anticipated. Before attempting any destructive fixes, users must verify their device's official support status. ### How to Check the Auto Update Expiration Date The expiration date is hidden one level deep in the system menus, which is why many users assume their update is simply glitching. If this date has passed, the update is not failing; it has permanently stopped being offered. 1. Select the time in the bottom right corner, then select Settings. 2. At the bottom left, select About ChromeOS. 3. Select Additional details. 4. Read the Update schedule section to find the month your Chromebook receives its final update. If the date is in the future, the device is still supported, and the error is caused by a network or software block. If the date has passed, retrying the update will never work. ### The Extended Updates Trade-off Some Chromebooks released before 2021 qualify for extended updates, which push security and stability patches up to the ten-year mark. Google marks these specific models with an asterisk in its official Auto Update policy list. If a device qualifies, the opt-in toggle appears in the About ChromeOS menu. However, enabling this feature comes with a severe, irreversible penalty. Turning on extended updates permanently removes Android support from the Chromebook. The Google Play Store disappears, all installed Android apps are deleted, and local app data is erased. Users who rely on Android applications must back up their data and weigh this trade-off carefully, as Google offers no way to reverse the decision. ### Bypassing Network and Administrator Blocks If the device is still within its support window, the network itself may be filtering Google's update servers. Mobile hotspots, metered connections, and public Wi-Fi networks with captive portals (like hotels or airports) frequently block system-level downloads. Switching to a standard home Wi-Fi or Ethernet connection usually clears the error. For devices issued by a school or employer, an administrator might have intentionally disabled updates or pinned the hardware to a specific ChromeOS version. Users can verify this by checking the system policies directly. ```text chrome://policy ``` Type the command above into the browser address bar and press Enter. Look for entries named `DeviceAutoUpdateDisabled`, `DeviceTargetVersionPrefix`, or `DeviceUpdateScatterFactor`. If any of these are active, the block is enforced at the server level, and the user must contact their IT administrator to request an update. ### When to Use Destructive Fixes A stalled download is the least common cause of the update error, but it is the easiest to fix on a supported device. Restarting the Chromebook clears most hanging downloads. If a standard reboot fails, users can initiate a Powerwash, which erases all local files and accounts, or perform a full recovery via a USB drive. Crucially, users must never run a Powerwash or a full recovery on an expired Chromebook. Because update eligibility is tied to the hardware profile, wiping the device does not change its expiration status. The Chromebook will simply boot back up, erase all local data, and continue to reject the update. ### The Hidden Cost of ChromeOS Longevity Google’s shift to a ten-year update cycle is a massive win for e-waste reduction, but the implementation of the "extended updates" toggle forces a harsh compromise on consumers. Stripping Android app support to maintain basic OS security fragments the user experience on older hardware. While this is a non-issue for enterprise fleets or schools that rely strictly on web apps, it severely downgrades the functionality for everyday consumers. Many users purchased pre-2021 Chromebooks specifically to use them as affordable Android tablet alternatives. By forcing these users to choose between critical security patches and their entire library of Android apps, Google highlights the architectural friction between ChromeOS and the Android subsystem. Until the company can decouple Android container updates from the core OS kernel, older Chromebooks will continue to face this frustrating ultimatum. ## Sources - [chromestory.com](https://chromestory.com/2026/09/couldnt-update-chromebook-fix/)