Some Chromebooks mistakenly declared themselves end-of-life last week

Source: Ars Technica

Article note: So the planned obsolescence thing is gross but not unexpected, but then second thought ... is there a list of Chromebooks going out of support, and whether or not it's easy to unlock their boot-loaders, because the EOL'd machines seem like a nice source of dirt cheap terminals...
If your new Chromebook told you it's past EOL, don't panic—as long as you were running Canary or Dev, that is. (If you were running Stable or Beta, you may continue panicking.)

Enlarge / If your new Chromebook told you it's past EOL, don't panic—as long as you were running Canary or Dev, that is. (If you were running Stable or Beta, you may continue panicking.) (credit: Valentina Palladino)

A lot of Chromebook and Chromebox users don't realize this, but all ChromeOS devices have an expiration date. Google's original policy was for devices to be supported for five years, but the company has recently extended that time to 6.5 years.

When your Chromebook or Chromebox approaches its built-in expiration date, it will warn you that it's time to go buy a new device entirely. Not long after that, it will refuse to apply any further security or feature updates. In addition to leaving users vulnerable to unpatched security exploits, this means that constantly evolving services such as Gmail will eventually stop working entirely.

Google has been working on a way to warn users six months ahead of time that their device's EOL date is approaching to allow them to plan with a little less time-sensitive desperation. But users running the Canary and Dev early-preview ChromeOS builds discovered a bug in the new code the hard way. After any reboot, brand-new devices started warning "this is the last automatic software and security update for this Chromebook. To get future updates, upgrade to a newer model."

Read 3 remaining paragraphs | Comments

This entry was posted in News. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *