Reputation: 4728
Tried solutions mentioned below
https://www.chromium.org/administrators/turning-off-auto-updates - but unsuccessful .
Tried solutions mentioned to delete the "update" folder but unable to find it in the location specified in the image below
Upvotes: 4
Views: 15650
Reputation: 582
I have posted this on a bunch of these chrome auto update issues and reportedly it has worked on both Windows and Linux, so perhaps it might help you as well?
Pass this flag to chrome every time you are running it.
--simulate-outdated-no-au='Tue, 31 Dec 2099 23:59:59 GMT'
You can set a future date. This will let Chrome / Chromium think that it shouldn't be outdated until this date and therefore won't show the outdated message.
By Adalbert Michelic [email protected]
"It's possible to silence this notification by faking the build date
by using this command line parameter:
--simulate-outdated-no-au='Tue, 31 Dec 2099 23:59:59 GMT'"
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943668#15
Upvotes: 3
Reputation: 3361
There's no need to delete anything. Chromium updates or auto updates are handled by Google Omaha client aka Google update client. Open run and then type services.msc
then disable these two Google update services:
Google update service (gupdate)
Google update service (gupdatem)
This will permanently disable update and auto updates in Chrome, as Chrome will try to invoke Google update service to check for updates and initiate the installation process too.
Update:
The above process will disable automatic updates but it is still possible to update Chrome from About Google Chrome page. Google Chrome invokes Google Omaha client and it will find the path of Google Omaha client from here: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Google\Update\Clients\{430FD4D0-B729-4F61-AA34-91526481799D}
If you change the this GUID then Google update client will always fail even if it's explicitly launched from Google Chrome. I would append a text to it rather than editing that GUID so that it would be easy to revert back.
Upvotes: 5