It’s time for Chromebook users to have more control over Chrome OS automatic updates

The release of the Chrome OS 75 Stable Channel has opened my eyes to something: Chrome OS automatic updates may be a little too automatic, and not in a good way.

Chrome OS 75 was first delayed from its expected release date by about two weeks. Almost immediately after the update started hitting Chromebooks, it was paused, presumably to fix some major issue or issues, and then arrived on a single device, likely for testing purposes. Finally, it arrived for all still supported Chrome OS devices.

Here’s the thing. While automatic updates in the background are generally a good thing – heck, they’re one of the key selling points of a Chromebook – situations like this remind us that no system is perfect. Therefore, there needs to be some type of customer mitigation option.

I say that because I read dozens of complaints from Chromebook owners during this release rollout. Many had major issues during the Dev and Beta timeframe, which of course, is to be expected. But by major, I mean major: The Google Play Store couldn’t access the web, for example; a situation I myself experienced. Removing and re-installing the Play Store didn’t help and that process took several hours.

Some folks also lost access to their Crostini container, meaning they could run their Linux apps or get at any data files stored there.

What’s the recourse for problems like that? You can always hop on to the Stable Channel. But, as Google notes on its relevant support page, this is a “powerwash”:

Switching from an experimental channel to a more stable channel will delete everything from your Chromebook, like downloaded files, photos, owner permissions, and saved networks for all accounts.

So while it’s an option, it’s not ideal for some. This is the perfect time for me to raise a few of my pro-tips.

First, I wouldn’t run the Dev or Beta Channels on a primary device. I have several Chromebooks, so I run one with Dev or Beta and one with Stable, for example.

Second, don’t store any files locally that you just couldn’t live without. My Downloads folder is literally a temporary storage facility and each night, I clean it out. Anything I need to save beyond one day goes right up into Google Drive as soon as it can because that’s how I roll.

Back to automatic updates. Once they’re downloaded and you restart you Chromebook, you boot up into a drive partition with the updated platform. There’s no real recourse other than the powerwash. Well, I guess you could simply never shut down your Chromebook, but that’s not a great strategy.

So here’s what I’d like to see.

Similar to how managed Chromebooks can be flagged not to automatically update Chrome OS, non-managed devices should get that option too. By managed Chromebooks, I mean those tied to GSuite, not Google, accounts and are managed centrally in a work or education setting.

After all, not every consumer wants to immediately have their software platform changed; at least not for a few days or a week in case of any issues such as those we saw with Chrome OS 75. Give device owners a clearly explained setting to delay automatic updates for up to a week. Even if that setting expires after seven days, it’s a better option than not having an option.

And although I’m sure there’s more going on behind the scenes with the dual partition process that Google uses to “instantly” update Chrome OS, why not have a revert option? If the secondary partition holds the old Chrome OS system software, provide a user choice to reboot back into it; essentially flipping environments at boot time?

Again, there may be technical limitations in the way the update process is currently designed to handle this idea, but I’m sure it’s possible. And it would potentially eliminate any powerwashing or data loss, getting people back to their Chromebook activities in under a minute.

It seems to me, based on the Chromium OS documentation, that this could be part of the rollback protection after update flow. Currently, once there’s a successful boot up in the updated software partition, the old one is expired and can’t be used, as I understand it.

Am I off my rocker and only making the situation worse by adding complexity to one of the simplest operating systems on the market? Chime and let me know what you think or if the Chrome OS 75 rollout caused you any downtime or other issues. Maybe if there’s enough of us on board for some changes, we can open up a bug and make a good system even better.

11 thoughts on “It’s time for Chromebook users to have more control over Chrome OS automatic updates

  • July 12, 2019 at 12:40 pm

    I agree , it would be a good option . The 75 rollout didn’t cause me any problems . I run one cb in stable and one in dev .

  • July 12, 2019 at 3:15 pm

    Microsoft made the same mistake with Windows 10 , only in a massively bigger way.

    The option to upgrade or not upgrade your own property should never be made by a distant corporation that cannot know the reasons why or why not you update your software (and often people have perfectly valid reasons). It’s MY machine, not the corporations.

    Microsoft’s forced updates, trashed my laptops a total of 4 times and forced me to completely reinstall the OS. This cost me hours and hours of work–and cost Microsoft nothing. I’m lucky that it didn’t trash either of my development machines.

    When companies force things like this on people because “they know better” (when they usually don’t) it makes my far less likely to use their products.

    One-size-fits-all approaches like this do not work and ignore the realities of software development. Realities that were learned years ago sadly appear to have been forgotten.

  • July 12, 2019 at 3:54 pm

    I update my Chromebooks manually. Still running 74.0.3729.159

    Does it seem to you that OS 75 is OK to use now?

  • July 12, 2019 at 4:29 pm

    Yes, I agree.

    There should be a setting along the lines of:


    Automatic (happens while idle)
    User prompted (can be snoozed for x amount of weeks)

    Simple enough?

    • July 12, 2019 at 5:02 pm

      Not all supported Chromebooks….because the HP X2 releases are still a little…wonky.

      • July 12, 2019 at 6:39 pm

        What are you experiencing with your X2? I ask because I haven’t noted any issues in particular but I’m not a power user. I had OS 75 xxx.102 and experienced no connectivity issues or jank. Now have OS 75 xxx.129 and still see nothing.

        • July 12, 2019 at 10:14 pm

          I’m not the guy you asked but for me, it is tablet mode. It’s not a good experience at all, especially with Android apps and I don’t even use that many. Overview mode is very funky and scrolling sometimes glitches and other weird things happen. Chrome OS 75 102 was unusable in tablet mode for me.

  • July 12, 2019 at 6:06 pm

    I don’t remember if I have taken advantage of it or not, but there is a process to roll back to the previous update. It does involve a powerwash but it isn’t the end of the world.
    I have used Canary daily for the last 3 years and occasionally run into an unresolvable “issue”. I go back to beta or dev for a day or two, watch the bug I am experiencing and go back to Canary. Since Canary updates daily and sometimes more often, major bugs don’t usually hang around very long. I don’t usually see more than one or two issues a year that have forced me to move back a channel. Most things are barely an annoyance for a few days until an update smooths things out again. I generally use my Chromebook for eight to ten hours a day so regular bad things would be just . . . bad. Daily updates absolutely work for me.

  • July 13, 2019 at 5:06 am

    Really security updates should be completely separated from functional / bells and whistles updates. And that applies to chrome os, windows, android, iOS, Linux, modems etc. With highly connected devices – everything – a security vulnerability of some devices is a vulnerability to the whole internet.
    I had through that chrome os and new windows strategy was to enable security updates to be pushed quietly and with high uptake rates. Shame it’s not working.

  • July 13, 2019 at 3:04 pm

    I don’t know. Every option like that is an opportunity for somebody less computer savvy to make a problem.
    This is pretty rare. If anything they should just make the rollback easy to do.
    For people in anything but stable channel, double meh. They should read the tin before they make that leap. There is no reason for anyone to be using it unless they just are too curious to be first to get new stuff. And if you want to ride the wave then you must be prepared to get busted up now and again. They have no legit complaint in my book as they’ve no right to expect a problem free experience.

  • July 14, 2019 at 9:37 pm

    Totally agree, 100%. Users should always have the option when to download and install the update – delay or set a preferred time or date to download and install the update.


Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.