Disbled autoupdates but still getting nagged to update!!

[A Former User]

A Former User last edited by

if Opera is not the "Default Browser", then it is enough to do so

[A Former User]

A Former User @slytheringirl last edited by

@slytheringirl said in Disbled autoupdates but still getting nagged to update!!:

I rolled back to version 58.0.3135.132 because I got tired of constantly having to switch the sidebar off and on when I needed it also I did not like the way Opera 62 screwed with the Speed Dial (there was a huge blank space above my speed dials).

I deleted every entry marked autoupdate or update in every Opera folder I could find plus deleting Opera from Task Scheduler. However, I still get the notification to update Opera at the top of the main Opera menu. The only way I can get rid of it is if I click on Update & Recovery in the menu, but it's only temporary since it just pops right back up if I open Opera again. It's annoying and I DO NOT want to update Opera at all!! Is there any way at all I can stop Opera from nagging me to update every time I open it?

Absolutely incredible that they don't have an option for this - On my newer computer Win 10 - Windows Edge rocks now, but with the Windows 7 - still stuck between Chrome / Opera (one nags for updates and other begs for default browser).

[A Former User]

A Former User @Guest last edited by

@temkem said in Disbled autoupdates but still getting nagged to update!!:

Launch Opera with the key:
disable-background-networking

Do you happen to know what exactly this function (background-networking) normally does?

[burnout426]

burnout426 Volunteer @Guest 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?

[A Former User]

A Former User @Guest last edited by A Former User

@yanta Disable auto-updates and even down to upgrade extensions.

[A Former User]

A Former User @burnout426 last edited by

@burnout426 in fact, if you start Opera with this key, Opera will not be able to search for updates and even prevent your installed extensions from being updated

[leocg]

leocg Moderator Volunteer @Guest last edited by

@temkem As far as I know, disabling auto-update also does that.

[A Former User]

A Former User @leocg 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-update or --disable-background-networking, closing Opera does not trigger the start of "opera_autoupdate.exe".

[leocg]

leocg Moderator Volunteer @Guest last edited by

@yanta What is the idea of those command lines. And, as far as I know, renaming the auto-update executable may have the same effect.

[A Former User]

A Former User @slytheringirl last edited by

@slytheringirl did ya get problem solved.. just check 'n..

[A Former User]

A Former User @leocg 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:
--disable-background-networking
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:
--disable-background-networking
and always run Opera from this shortcut.

[A Former User]

A Former User @leocg last edited by A Former User

@leocg

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]

slytheringirl @Guest 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.

[leocg]

leocg Moderator Volunteer @slytheringirl last edited by

@slytheringirl Rename or delete, makes no difference at all.

And of course I was talking about the system temp folder.