Google's support table gives several Chromebooks an update date of June 2036. Its new transition guide says regular ChromeOS updates stop in mid-2034. For a buyer choosing one of those machines today, the final two years now depend on a move to Googlebook OS that Google has not mapped to specific models. The dates are both on Google's website: the Auto Update policy lists 2036 deadlines, while the Googlebook transition FAQ names the 2034 cutoff.
Google says devices whose support periods run past 2034 will have help moving to its new operating system, provided they qualify. It also says many will have a direct migration path. Those words leave the purchasing question open. Google has not said which models qualify, what a direct migration requires, or what happens to a listed support date when a machine cannot make the move. OSnews called the mismatch a broken promise. The story had reached 338 points and 136 comments on Hacker News when the candidate was captured. The documents support a narrower conclusion: the ten-year promise has acquired an unpublished hardware condition.
The promise was attached to ChromeOS
Google made the ten-year policy unusually plain in September 2023. It said all Chromebook platforms would receive regular automatic updates for ten years after the platform was released. Machines released from 2021 onward would get the extension automatically; owners and administrators of some older devices would need to opt in. The announcement described security, stability, and feature updates, delivered on what was then a four-week cycle.
That clock starts with the platform, not the day somebody buys the laptop. A late retail sale can therefore include less than ten years of remaining support. Google's current Auto Update policy tells buyers to check the model's date before purchase and warns that technical support ends after the final automatic update. The model table is meant to turn a broad pledge into a date a school, business, or individual can plan around.
Google repeated the commitment this May while explaining its future laptop plans. Its enterprise blog said ChromeOS would continue to receive ten years of automatic updates and that organizations could keep buying and deploying Chromebooks. The same post promised several ways to move to the new experience later, but it did not put a cutoff on ChromeOS itself. That language remains visible in Google's May 2026 Chromebook statement.
The September guidance changes the practical meaning of those dates. Google now says ChromeOS devices will get regular updates and security patches only through mid-2034. For eligible hardware with a longer lifecycle, the remaining support will come through Googlebook OS. A customer may still receive updates for the full listed period, but the operating system delivering them can change along the way. That distinction matters because Google originally sold the duration as a ChromeOS update policy, while the new FAQ makes the final years conditional on migration.
A 2036 date now contains a handoff
The overlap is not hypothetical. Google's table lists the Acer Chromebook 311 C725 family through June 2036. Several Asus CL14 and CM14 variants carry the same date. Lenovo's Chromebook Enterprise m and the 500e 2-in-1 Gen 5 with MediaTek are also listed through June 2036. These are entries in the current approved-device table, not estimated dates supplied by retailers.
At the same time, Google's transition page says the Chromebooks people have today will receive updates through their supported lifetime. A few lines later, it limits ChromeOS updates to mid-2034 and offers a transition for qualifying devices bought today whose lifecycle extends beyond then. The only reading that makes all of those statements fit is that some support lifecycles will cross from ChromeOS to Googlebook OS. That is our synthesis of Google's two support statements, since the company does not spell out the handoff in those terms.
An operating-system migration is more consequential than an ordinary automatic update. Googlebook OS uses the Android technology stack beneath a desktop system. Google says it will run Android apps natively and retain a desktop web browser, while adding closer links with phones and tablets. The transition FAQ describes those planned capabilities, but it does not document compatibility for Linux development environments, peripherals, local data, or existing administrator policies during an upgrade from ChromeOS. Silence on those points is not evidence that they will fail. It is a reason not to treat migration as a routine patch yet.
Eligibility is the missing field
Google says many newer commercial Chromebook models will be able to upgrade. It will publish the device list and migration paths later. Until that list arrives, the public support table can answer when a model's update period ends but cannot answer which operating system will carry it there. That gap is most relevant to the models with dates after mid-2034, as set out in the Googlebook FAQ.
Fleet management adds another dependency. The first Googlebooks are consumer devices and do not support domain enrollment or centralized fleet management. Google expects a fuller management system to start rolling out in the second half of 2027, then expand in phases. Schools and companies can manage today's Chromebooks through the Google Admin console, but the new platform's institutional controls are still on a multi-year schedule.
Licensing will change too. Existing Chrome Enterprise Upgrade and Chrome Education Upgrade licenses remain supported for ChromeOS devices through their lifecycles. A migrated Chromebook or a new Googlebook will use a different licensing structure, whose terms Google says it will disclose before commercial availability. For an administrator pricing a fleet with a 2035 or 2036 retirement date, the undisclosed Googlebook licensing model belongs in the cost estimate now, even if no invoice arrives for years.
None of this means a Chromebook turns into an unpatched machine tomorrow. Models whose published dates fall before or during 2034 still fit inside the newly stated ChromeOS window. Google also says Googlebook OS will retain verified boot, sandboxing, automatic updates, and support for secure student assessments, although some security work is described as a phased roadmap. The transition plan places the uncertainty after the cutoff, rather than describing a present security failure across the installed base.
What buyers can verify today
The most reliable number remains the exact model's Auto Update Expiration date. Product family names are not precise enough because nearby variants can have different deadlines. In Google's table, for example, Asus Chromebook CX14 entries end in either 2033 or 2035 depending on the model code, while CL14 variants reach 2036. Google's own buying guidance says to check the published date, and that advice matters more during a platform transition.
For a device ending after mid-2034, the AUE date now answers only half the question. Buyers also need written confirmation of Googlebook OS eligibility, whether migration keeps local files and managed settings, and what license replaces the existing ChromeOS upgrade. Google's FAQ promises those answers later. Until it publishes them, a 2036 listing describes an intended support duration without defining the software path for its last two years.
Google's next useful document is therefore a model-by-model migration table, ideally beside the AUE column people already consult. Watch for that list, the migration procedure, and the commercial licensing terms as management features begin arriving in the second half of 2027. If a Chromebook keeps its 2036 date after those details appear, buyers will be able to judge the full support path. Until then, 2036 is a date with a 2034 asterisk.