The Same Ten Years, Measured From Two Different Days
A Chromebook bought new eighteen months ago announces that it will stop getting software updates. The owner remembers the headline, and it is real: Google's The Keyword post "Chromebooks will get 10 years of automatic updates" says "All Chromebook platforms will get regular automatic updates for 10 years — more than any other operating system commits to today." Eighteen months is not ten years.
The sentence does not say what the ten years are counted from, and it reads two ways. Reading one: ten years counted from the day the device was bought, or at worst from the day the model went on sale. Reading two: ten years counted from the first release of the platform inside the device, a date that can sit years before the model reached a shelf and that no sticker on the box mentions.
Reading two is the rule. And a second fork inside it, marked by one asterisk in a table, decides whether the last stretch of those ten years arrives on its own or costs the owner every Android app on the machine, permanently.
What Google Counts From, in the Policy's Own Words
The controlling document is Google Chrome Enterprise and Education Help, "Auto Update policy". Its summary line is short, and it carries its own caveat: "ChromeOS devices receive 10 years of updates. For devices prior to 2021 that will receive extended updates, some features and services might not be supported." The first sentence alone supports either reading. The companion page for administrators, Google Chrome Enterprise and Education Help, "Extended updates support", closes the fork: "ChromeOS devices receive OS updates for 10 years after a device platform is first released."
After a device platform is first released. Not after purchase, not after the model's launch, not after first sign-in. The policy page defines the unit: "A platform is a series of components that are designed to work together—something a manufacturer selects for any given device." The clock belongs to a board, and a manufacturer can build a new laptop around a platform that has already been shipping for years. The consumer page, Google Chromebook Help, "Extended updates support", repeats the anchor in the phrase "from the platform's release."
The policy page then says where the answer lives: "Google will publish how long platforms will receive automatic updates on this page after its release, giving buyers time to make purchase decisions." That is the crux. The ten-year figure is a policy. The date is a lookup. Only one of them is about your device.
Read Your Own Device's Date Before You Read Anything Else
There is no arithmetic to do here; doing it is how people get this wrong. The machine knows its own answer. Google Chromebook Help, "Check your Chromebook's update schedule" gives four steps: "At the bottom right, select the time and then Settings." Then "At the bottom left, select About ChromeOS." Then "Select Additional details." Then "In the "Update schedule" section, you'll find when your Chromebook will receive its last update."
That date is the number that matters. It is not a prediction and not a warranty term. For a device whose published date carries no asterisk it is the end of the ten-year window that started when the platform was first released, resolved for the board in front of you. For an asterisked device it is the day the automatic updates stop, which is not the day the ten years end.
The same page defines the banner: "If you get a "Final software update" notification, your device won't receive ChromeOS and browser updates anymore." The sentence covers two things at once, the operating system and the browser, so the assumption that Chrome keeps patching itself afterwards does not survive it. What stops is listed in two bullets, and the second is the one owners notice first: "Security updates, bug fixes, and new features for Chromebooks. Existing features may stop working." and "Support for certain apps that require specific ChromeOS or browser versions." Both bullets stop together. It is the same trap as a phone reporting one figure while the vendor published two, the subject of the September bulletin that carries two patch levels.
The Asterisk Is the Second Reading of the Same Date
Now the part that catches people who looked up the right date. The Auto Update policy page publishes a long table under the heading "Google approved ChromeOS devices". The date column is headed "Automatic updates until". Some dates carry an asterisk, and the footnote attached to it is the only text on the page that defines it: "*These ChromeOS devices must opt in to receive extended updates. For details, see Extended updates support".
Must opt in. Not may. For an asterisked row the printed date is conditional. A row reading "Jun 2027*" under "Automatic updates until" does not promise updates through that month. It says the month is reachable by someone who takes an action, and that without the action the device stops earlier.
The Chromebook Help page states the condition from the owner's side: "For some Chromebook models, you must opt in to receive extended updates during the final years of support" and "These systems are denoted with a * next to the support date." On timing it adds, "You'll have the option to opt-in at any time once extended updates are available."
Google's announcement hides the schedule in a parenthetical: users and administrators "will have the option to extend automatic updates to 10 years from the platform's release (after they receive their last automatic update)." After. The opt-in is not an alternative to the original end date, it sits on the far side of it. An asterisked device stops, shows the final-update notice, and only then offers the extension.
What the Opt-In Costs, Listed by Google
The extension has a price, and it is not a setting that can be put back. The Chromebook Help page lists it. "Extended updates include continued support for security, performance, and stability for your Chromebook." Then: "Devices that receive extended updates will no longer have the ability to run Android apps." Then the reason: "Android apps and the Google Play Store will be removed to maintain security, performance, and stability on your ChromeOS device."
The specifics: "All Android-related data will be erased from your device." "You'll lose access to the Google Play Store from your ChromeOS device." It adds that "Google Play Store subscriptions must be managed through the web." One thing survives, and it is the part people later report as a bug: "Better Together features such as Nearby Share and Smart Unlock between Chromebook and Android smartphones will continue to function." Pairing survives; the ability to run Android software does not.
The door swings one way only: "After you've opted in to receive extended updates, this process won't be reversible." The alternative is stated too: "If you don't opt-in, automatic updates won't continue" while "Android apps and Google Play Store will remain on your device, but app developers may choose not to support these devices over time." So an asterisked Chromebook offers a choice between two losses: keep the Android layer and stop receiving security updates, or keep the updates and lose the Android layer for good. A device that keeps working while an update removes a capability is the shape of the printer that still prints after Protected Print Mode removed its custom options.
On managed fleets the choice is not the user's. The administrator page says "Most devices update automatically, but for a subset of older devices, an administrator must opt in to extended updates". It happens "via a policy (called Extended auto-updates) in the Google Admin console", and it "Requires having the Mobile Device Management administrator privilege." A school laptop never presents the choice to the student holding it.
Four Google Pages Draw the 2021 Boundary Four Ways
Everything above turns on which side of 2021 the device sits on, and four Google documents draw that boundary four ways. A 2021 model falls inside one wording and outside another.
The administrator page says "All ChromeOS devices released in 2021 or later automatically receive extended updates." The announcement says "Starting in 2024, if you have Chromebooks that were released from 2021 onwards, you'll automatically get 10 years of updates." The consumer page comes from the other direction: "Eligible Chromebooks released before 2021 will have the option to receive extended updates for a total of 10 years of automatic updates from the platform's release." Those three agree. Then Google's one-page summary "Keeping Chromebooks useful and secure for longer" says "All Chromebooks released after 2021 will receive 10 years of automatic updates – no action required." After 2021 is not the same set as from 2021 onwards. The same one-pager swaps the anchor for a different one: "A device's release date determines when it will receive its last automatic update". A device's release date is not the platform's first release, and read alone that sentence licenses the wrong reading of the whole policy.
This is why the resolution is the table and the device's own Update schedule screen, not the prose. The table gives a month, per model, with or without an asterisk. No sentence about 2021 overrides a row that names your machine.
Nine Years Apart on the Same Published Table
The rows show the size of the effect better than any explanation. In the Auto Update policy table the HP "Chromebook 11 G6 EE" reads "Jun 2027*", asterisk included. "Pixelbook Go" reads "Jun 2029". "Chromebook 512 (C852, C852T)" reads "Jun 2031". "Samsung Galaxy Chromebook 3 360" reads "Jun 2035". The "Acer Chromebook 311 (C725/C725T/C725-TCO/C725T-TCO)" reads "Jun 2036". The oldest rows are already historical: "Cr-48" reads "Dec 2015" and "Chromebook Series 5 550" reads "Jun 2017".
All of them are covered by the same ten-year policy, and the dates on that one table run from "Dec 2015" to "Jun 2036", with the rows still in support spanning "Jun 2027" to "Jun 2036". Look at the asterisked cluster and the platform rule becomes visible on the page itself. "Acer Chromebook 11 (C732, C732T, C732L, C732LT)", "Asus Chromebook C202XA", "Chromebook 11 G6 EE", "Lenovo Flex 11 Chromebook" and "Lanix Chromebook C116" all carry the identical date, "Jun 2027*". Five manufacturers, one month. Brands do not share a launch date. Platforms do.
One thing the table does not give is a day. The column heading is "Automatic updates until" and the values are a month and a year. No note on that page converts "Jun 2027" into a calendar day, which is why the per-device Update schedule screen is the answer of record.
What Still Works After the Last Update
The final-update notice is not a shutdown notice, and three Google pages say so in three different phrasings. The Auto Update policy page says "Even if a Chromebook is no longer receiving automatic updates, it still comes with secure mode." The update-schedule page says "Even if your Chromebook no longer gets automatic updates, it still comes with a verified boot." The announcement says "Even if a Chromebook no longer receives automatic updates, it still comes with strong, built-in security features." Three sentences, one point: some hardware-rooted protection persists.
What does not persist is anyone's obligation to help. The policy page is explicit: "After devices receive their final automatic update, existing and future policies may not work as intended, and technical support will not be provided." The older page Google Chromebook Help, "Use or upgrade an old Chromebook" is direct: "If your Chromebook is working well, you can keep using it. Just keep in mind that it won't get any more software updates."
Two federal documents explain why the date outranks the branding. The Cybersecurity and Infrastructure Security Agency catalog "Bad Practices" lists "Use of unsupported (or end-of-life) software in service of Critical Infrastructure and National Critical Functions is dangerous and significantly elevates risk to national security, national economic security, and national public health and safety", and NIST Special Publication 800-40 Rev. 4, "Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology" states that "Preventive maintenance through enterprise patch management helps prevent compromises, data breaches, operational disruptions, and other adverse events." Neither was written about a household Chromebook, and neither says a device past its date is unsafe to own.
When This Doesn't Apply
None of this is a warranty question. The ten-year figure is an update commitment about a software platform, not a promise from the retailer, and crossing the date creates no claim against anyone. A screen that fails in month fourteen is a hardware matter under whatever written warranty came with the device. A device that stops updating in month fourteen because its platform is old is behaving exactly as the policy describes.
It also does not apply outside ChromeOS. The platform-anchored clock and the asterisk are specific to the Auto Update policy; nothing here transfers to a Windows laptop or a phone.
And the asterisk branch does not apply to devices on the 2021-or-later side of the boundary, on the administrator page's wording, because those "automatically receive extended updates." For those machines the printed month is unconditional and there is no Android trade to consider.
The wider pattern is documented. The Federal Trade Commission press release "Smart Products Surveyed Fail to Provide Consumers with Information on How Long Companies will Provide Software Updates" reports that "nearly 89% of products surveyed failed to disclose on their websites how long the products would receive software updates". The release adds that the staff paper "noted that manufacturers' failure to inform prospective purchasers about the duration of software updates for products sold with written warranties may violate the Magnuson Moss Warranty Act". Publishing a per-model table at all puts ChromeOS on the better side of that finding, which is why the table beats the headline.
The Check That Takes Two Minutes
Open Settings, choose About ChromeOS, then Additional details, then the Update schedule section. That gives the last update date directly. Then find the model in the policy table and look for an asterisk on the date. No asterisk means the month arrives on its own. An asterisk means the month is conditional on an opt-in that comes after the last automatic update, removes Android apps and the Google Play Store, and "won't be reversible."
If the plan is to buy used, do both lookups before paying. The listing will repeat the ten-year figure because it is true. The table row is the only place that number becomes a date, and the asterisk beside it is the only place the date becomes a decision.
Comments
Post a Comment