Disable Auto-Update?

Comments

36 comments

  • Daniel Chun

    Those tips from that article are not to be implemented in the OS. They are URLs that you would need to block on your local network through your firewall or router. This won't help with blocking updates when you are connected to a different network.

    Here is another way to disable updates:

    https://docs.google.com/document/u/1/d/17mBp_D62BOYnBdMhHHsYoEopb02rwXyHjBUzu7O8zUw/pub

    2
    Comment actions Permalink
  • Andre du Toit

    Nice thank you! 

    I've just had to figure this out first

    https://cloudreadykb.neverware.com/s/article/Disabling-RootFS-Verification

    0
    Comment actions Permalink
  • Peter Watt

    Daniel, does the method to disable updates you shared in the Google Doc still work? Are the steps in the doc all I need to do?

    Thank you.

    Peter

    0
    Comment actions Permalink
  • Peter Watt

    Daniel, I tried your method and it was working great until I got to step 6 of part 10 - when it's time to save. I get an error message at this point - I could get the exact message if it would help.

    0
    Comment actions Permalink
  • Forrest Smith

    Those steps should still work.

    If you're seeing an error, it'd be best to take a picture of what error you see. 

    Often, the problem is that parts 5 and 6 were not successfully done if part 10 step 6 fails

    1
    Comment actions Permalink
  • Peter Watt

    Hi Forrest,

    I just tried Daniel's method again. I noticed that when I get to step 8, I am not getting a password prompt, as it said I would. I've included an image:

    0
    Comment actions Permalink
  • Peter Watt

    Hi Forrest,

    I was finally able to use this method to disable auto-updates. I had to use ":x" to save and quit. I tested it tonight and when I click on check for updates, I get the message that "your Chrome device is up to date," even though it's version 83.4.27

    When I went to install the proprietary media components, the install never finished, which makes me wonder if I have also blocked this feature? Does this mean that I need to install the media components before I make the changes?

    0
    Comment actions Permalink
  • Peter Watt

    Forrest,

    I used "rollback" to go back to 85.4. Then I turned off auto-updates using the method described above. So now the laptops are working well but locked at 85.4. I'm hoping that a solution will be found to the issue I had at the start of this thread.

    Thank you,

     

    Peter

    0
    Comment actions Permalink
  • Michael Walter

    Thanks for all the help Peter! I had the exact same issue with a few donated Lenovo L440s I was using in my classroom. They are a certified option, but the moment version 87.3.41 hit they just stopped working with Wifi. As you said, the very odd x over the wifi icon as well.

    How does the rollback command work?  That was the only thing I was unsure of. I was lucky, I had an image of version 85 downloaded on a computer that I used to get mine working again. 

    1
    Comment actions Permalink
  • Peter Watt

    Hi Michael,

    I'm happy you found some of my information helpful. Here is the keystroke to get rollback to work:

    after the word crosh> type "rollback." It says that it is a powerwash, but it will also bring you back to the previous version of Cloudready you had installed - at least it did for me.

    Hope that helps.

    Peter

    0
    Comment actions Permalink
  • Bidwell Ely

    You might try updating to vs 88.1 (out today) to see if the wifi issues are resolved.

    dev channel to try v88.1 

    https://www.neverware.com/blog

    0
    Comment actions Permalink
  • Peter Watt

    Yes, I updated to 88.1, but it did not solve the issue.

    Peter

    0
    Comment actions Permalink
  • Francisco VALLEJO

    Hello, 

    Does anyone have the Daniel Chun doc ? When I click on the url it does not work :/ 

    And I do not know how works the Andre du Toit's solution.

    Thanks !

    0
    Comment actions Permalink
  • JCloud

    The Andre solution is to block those websites on your wifi modem / router / firewall, so find out what make modem / router / firewall your house has. Then google how to block websites on that model.

    0
    Comment actions Permalink
  • JCloud

    It will be similar to this in theory, but change depending on what brand you have

    https://kb.netgear.com/24053/How-do-I-block-Internet-sites-on-my-NETGEAR-router-using-the-router-web-interface

    0
    Comment actions Permalink
  • Bidwell Ely

    Daniel Chun, I tried to access the document. I got the following from Google Docs

    "You need permission to access this published document."

    So please change the access to the document or publish it on the Forum.

    0
    Comment actions Permalink
  • Alexander David Frick

    Daniel Chun Andre du Toit Peter Watt Michael Walter 

    USE NANO for your edits, not vim, chromiumos now has nano built in. *Yet another example of someone getting stuck on something simple because of vims horrible interface and keybinds*

    The way I have always done it, doesn't require editing, although Daniel Chun thing still works, is to rename update-engine.conf.

    >> https://neverware.zendesk.com/hc/en-us/community/posts/210605208/comments/360008870893 

    0
    Comment actions Permalink
  • C. Nero

    With v96, I see that blocking auto update is recommended and necessary for many of us.  Could somebody kindly provide a link to the procedure that would work for HomeEdition Release 96.3.22.  Many procedures changes with time, go stale, or may even become outright dangerous.

    Kindly help!

    PS. Is Forrest Smith still here? Thank you!

    0
    Comment actions Permalink
  • Joel R.

    This is the latest official guide made by Neverware:

    https://cloudreadykb.neverware.com/s/article/Disable-Auto-Updates-on-Home-edition

    Coincidentally, that was posted days after the announcement of upcoming changes to Cloudready, maybe in anticipation of some users wanting to keep dev mode. The Dev / Beta channels were already at v96 at that time, so I presume the guide will cover v96.3.22.

    0
    Comment actions Permalink
  • C. Nero

    Joel, thank you very much!

    I read Ilya's nice helpful detailed write up.  

    Instead of the above, which looks a bit risky or unfamiliar shall I say to me, is it possible simply to use a     filter with  the 3 neverware server urls in my router firewall?  It is much easier for me to  try and undo if needed. If yes, would you be kind enough to post them here again.  I have a hard time sometimes finding a post again on re-search.  Thank you kindly !

     

    0
    Comment actions Permalink
  • C. Nero

    OK. I found them again, I posting them here again. Will they work with 96.3.22 HomeEdition Stable? Can anybody confirm from experience, or otherwise?

    1. Update Servercloudready-paid-update-server-2.neverware.com 
    2. Update Storage URLs: cloudready-paid-update-storage.neverware.com
    3. Legacy Update Server: cloudready-update-server-2015-03-12.neverware.com
    4.  
    0
    Comment actions Permalink
  • Joel R.

    https://cloudreadykb.neverware.com/s/article/upcoming-changes

    https://cloudreadykb.neverware.com/s/article/How-To-Disable-Auto-Updates

    https://cloudreadykb.neverware.com/s/article/Disable-Auto-Updates-on-Home-edition

    All these docs that provide that information were posted or updated in late January 2022, so I would think they are still reliable. Regarding the command-line method, the changes made seem to be rather benign in my opinion, but it's understandable if you're more risk averse. Disabling verity is probably the main concern there; you can key in 'sudo chromeos-setdevpasswd' as extra protection to password-protect the shell.

    If you're still worried that you'll inadvertently get an update, I suggest that you save a copy of the .bin file of v96.3.22 so that you can reinstall that version if you need to. Then do any of the two Neverware-endorsed methods to disable updates, whichever works. If you really need 100% confirmation, you can tag (with @) Ilya G or Forrest Smith and ask them, but they haven't really been responsive on this forum for a while.

    0
    Comment actions Permalink
  • C. Nero

    Joel, good suggestions.

    I do not see an affirmative way to test if the server url works.  Right now if I check for a new version, it will say, there is no new version.  It would have exactly the same behavior after setting up url filters in my router :) So we don't know if that would work, until the next new version appears.  And then it it would be too late if it does not work.  Is my thinking correct?

    My problem is not just the version but the stateful partition of many years!!

    When is the next version without the console is expected approximately.  Have you seen any chatter about that ?

    Regarding the disabling verity. I have read that a couple of times.  It is not clear to be if this is reversible or not.  That is, once verity is disabled, you cannot get verity back, right?  One of the reasons I use chromeos  is that it has verity.  I have been using a chromebook from its beta CR-48, or lately ClooudReady and had never disabled verity. 

    Could you please confirm if it is reversible or not.  At some point it implies, that when rebooted verity will be re-enabled.

    Ilya G , Forrest Smith could you please confirm the above?  Thank you very much!

     

    0
    Comment actions Permalink
  • Joel R.

    While waiting for Ilya or Forrest, some more suggestions:

    If you have a spare laptop / PC, install an older Cloudready version on that. You posted about a month ago about getting Beta / Dev channel builds, maybe download v96.2.2 again (or older) and install that to your spare device. Try to update it first if you want, just to confirm that it indeed upgrades to 96.3.22-- it should do so. Then reinstall 96.2.2, set up the filters on your router, and try to check for updates. This would be the ultimate confirmation.

    Following Neverware's historical release pattern, there should still be a v96.4 stable release soon. The version/s after that would be the ones without shell access; hopefully Forrest & Ilya can confirm when this will be.

    On disabling verity, Forrest says in this post that "it's impossible" to re-enable as far as he knows. I remember someone here (can't remember who and on which thread) mentioning a while back that verity was re-enabled on their system after an update. Not sure if that was true though; if it was re-enabled by an update, it most likely wasn't by design. Having to reinstall CloudReady entirely makes sense as a recourse since the point of verity anyway is to have a clean and unaltered system.

    0
    Comment actions Permalink
  • C. Nero

    Joel, I really appreciate you staying with me.  You seem to understand fully my concerns and way of thinking!

    In fact I have been thinking of doing exactly what you suggested.  Have not gotten around to check if any of my very old ones will indeed the newer versions any more...

    One comment about you mentioniing v96.4.  You know the 96.3.22 is indeed Release Stable, otherwise I would not have got it by auto update.  Are you saying historically there has been a second stable release often? Good... :)

    0
    Comment actions Permalink
  • Ilya G

    C. Nero those are the correct URLs. 

    We will be releasing a 96.4 stable as well in the next couple of weeks.

    We will provide notice via blog and forum post about upcoming update from CloudReady to Chrome OS Flex and we will start with dev channel updates first. 

    0
    Comment actions Permalink
  • Bidwell Ely

    Ilya G, thanks for responding, as you can imagine, being out in the wilds, sometimes, we have to guess what is going to happen next. Especially after the big hubbub with Chrome OS Flex, to know there is a plan is valuable.

    Bidwell

    0
    Comment actions Permalink
  • C. Nero

    Ilya G

    Thank you very much for that valuable info.

    My router,s url filtering has the following restrictions.  Could you please let me know if either one of those could prevent the filtering on those 3 particular neverware server URLs? Thank you.

    Limitations of the filtering function :

    1. Compressed webpages that use HTTP compression technology cannot be filtered.
      1. Https webpages cannot be filtered

      I have a suspicion the filtering is not taking place. But I dont know how to verify it.

      Thank you!

       

      Edited 2022.03.12

      I tested it. Even with all 3 urls, in my router firewall, it cloudReady updates normally.  So this method will not work with my router for preventing auto update.

    0
    Comment actions Permalink
  • Joel R.

    Hey Ilya G, nice to hear from you. Thanks for confirming the 96.4 release. Would this be the final CloudReady version? I'm curious because I've recently just seen the news on Chrome OS having LTS releases now, v96 being the first one. Does this have any impact on CloudReady? Would be nice to have security and other important fixes carried over to CR so some users can safely stay on v96 until later in the year, when (hopefully) dev access would have been introduced to Chrome OS Flex. Or is this all just wishful thinking?

    0
    Comment actions Permalink
  • Bidwell Ely

    Ilya G, Another question, Is the Home edition going to have the same Long Term Support as the managed editions?

    https://support.google.com/chrome/a/answer/11333726

    0
    Comment actions Permalink


ChromeOS Flex is replacing CloudReady, so this community is no longer accepting new comments.

Please visit the ChromeOS Flex Help Community to post any new questions or thoughts! You can still link back to this or other pages in this community in order to reference past conversations.

Please sign in to leave a comment.