Disbled autoupdates but still getting nagged to update!!
A Former User last edited by
Launch Opera with the key:
Do you happen to know what exactly this function (background-networking) normally does?
burnout426 last edited by
@yanta https://peter.sh/experiments/chromium-command-line-switches/#disable-background-networking gives a tiny description. I'm guess @temkem is saying that it will also disable some background connect that Opera uses to check and notifify for updates?
temkem last edited by temkem
@yanta Disable auto-updates and even down to upgrade extensions.
A Former User last edited by
As far as I know, disabling auto-update also does that.
Opera stable v62.0.3331.99 on Window 7 32-bit (portable installation):
In my Windows Task Manager the "opera_autoupdate.exe" appears as an active process for a short time when closing Opera, if I started the web browser by double-clicking on the "launcher.exe".
If the "launcher.exe" is called with parameter
--disable-background-networking, closing Opera does not trigger the start of "opera_autoupdate.exe".
temkem last edited by
@leocg The fact is that if you delete or rename the file opera_autoupdate which is located in the Opera installation folder, in the folder with the Opera version number, Opera will not be able to update, but anyway when using Opera, you may receive notifications that you need to update Opera.
But if you run Opera with the key:
then Opera will not notify you that you need to upgrade.
If Opera is not the “Default Browser” in the system, then you can not touch the file opera_autoupdate, but just prescribe the key:
and always run Opera from this shortcut.
A Former User last edited by A Former User
What is the idea of those command lines.
There are situations where the automatic update mechanism is simply inconvenient. In my special case, I use Opera in a partially virtualized environment. In this environment, if I do not start Opera with the "--disable-update" command line switch (I'm still testing the second switch), this will cause error messages from the virtualization program. That is the reason for my special interest in this topic.
And, as far as I know, renaming the auto-update executable may have the same effect.
This file is created with every Opera [upgrade] installation anew. Instead of renaming it each time anew, it is more comfortable for me to start Opera via the mentioned command line switch when needed.
Also, if I run Opera "normally" (means: not partially virtualized) the automatic update is desired and I can do so by simply clicking on the "launcher.exe" instead of renaming the renamed "opera_autoupdate.exe" back to its original file name before.
I apologize for my poor English, but you may see that there may be user scenarios that make it desirable to be able to control Opera's update behavior.
slytheringirl last edited by
@temkem Tried your suggestion of adding disable-background-networking to my desktop shortcut and so far Opera hasn't nagged me to update. Not too happy about losing the ability to update extensions, but it's a small price to pay to stop Opera's harrassing me to update.
@leocg I had already deleted all files named auto update. I have been doing that for a while now. I never rename them, just delete them. Also I could find no temp folders for Opera.