Rogue Opera 29 Auto Update
-
suntana last edited by
Okay, what gives? All this time, the ole renaming of the opera_autoupdate file to opera_autoupdate_Disabled ... and disabling the Opera scheduled Autoupdate task with CCleaner's Startup Tool had kept Opera at bay, preventing it from performing any auto updates without my consent.
Now all of a sudden the day before yesterday I was slapped in the face with an out of the blue forced update of my Opera 27 to Opera 29. I was pretty sure I had performed my usual NO Auto Update Lockdown routine. But, I went ahead and thought, "Well, who knows? Maybe this time I did forget to perform it and so it updated itself." So, I uninstalled the Opera 29 and reinstalled Opera 27. I then made sure to perform my NO Auto Update Lockdown routine.
I powered up my computer a while ago ... brought up Opera and BAMM! I was again slapped with the Rogue Auto Update sequence. Grrrrrrrrrrr!! So I went and checked things out. Lo & behold, the opera_autoupdate_Disabled file that I had renamed the day before still existed. It obviously just got ignored. And another new opera_autoupdate file was just created. And the Opera scheduled Autoupdate task that I had disabled the day before was now again enabled. Why you sorry piece ___________
Uhhh, anyway, what the heck is going on? Has Opera now finally manipulated things to where there is absolutely NO getting out of the rogue forced updates?
-
suntana last edited by
Remember ... keep in mind that I have Dial Up. I don't care to have any App shove a version update down my Dial Up modem's throat at any second that it pleases. Updates like these I like to do them when I have access to someone's High Speed Internet.
And then if and when I find something with the new version that I don't like, I prefer to be able to downgrade to the old version and STAY there until I am satisfied that the new version's problems have been fixed to my liking. I don't want to be surprised with being updated yet again without my consent a day or two later.
-
falloutboy09 last edited by adminhad the same happen to me after a crash of Opera 25, and it kinda seems that a lot of people here on the forum have an issue with this kind of "update policy".
maybe you get lucky, and still have your preferred version saved and can use leo's suggestion to work for you.
https://forums.opera.com/post/75714 -
suntana last edited by
I went over to the Opera Desktop Blog and brought up my issue there. Hopefully there Devs WILL see it and put a stop to this Riffraff Rogue Forced Updates.
-
badopera100 last edited by
Same crap here...about to leave Opera for FireFox if they insist on forcing a specific version. As soon as I install version 20, it launches before I can delete the auto=update files, and then updates to whatever is new.
All the new version suck IMO. 12 and 20 were awesome...
-
blackbird71 last edited byMy "take" on this is that I own the computer, I've paid for most of the software on it, and I pay for the bandwidth for downloads. System configuration control is my own business, in part because that's how I assure necessary stability for my software so that it all plays nicely with each other and with the users. Whether I load free or paid software on the system, I will NOT give up control over updating that software... updates will occur only if I want them to, at times of my own choosing which fit my system scheduling needs. In some cases, I use 'extreme' measures to block auto-updating in certain stubborn programs (such as renaming updater files, blocking things in task scheduler, or even blocking update sites in outgoing firewall rules. Far more preferable is software that gives me a built-in option to block or only notify me about updates. But ANY software that over-rides my owner control of updating on my own system will only ever do that once, after which it will be thrown off the system. Full stop.
-
suntana last edited by
Exactly.
As far as I'm concerned, in this case Opera 29 behaved like a virus, like malware. I didn't want it in there and despite me having had measures in place so that it wouldn't make it's way into my computer ... it still lowlifely wormed its way in. As a certain President would say --- unacceptable.
Later this evening I will probably try reinstalling Opera 27 yet again and this time completely delete the opera-autoupdate file instead of just renaming it.
I've been keeping an eye on Vivaldi. If Opera 30 and above insist on the same intrusive behavior, I'll have to give Vivaldi a more detailed tryout. At this instant I don't know whether Vivaldi has or doesn't have that same rogue auto update behavior, but at least it'd be something to check out.
-
suntana last edited by
Okay, I'm curious.
So I went ahead and yet again downgraded to Opera 27 and performed the whole shebang enchilada to TRY and prevent Opera from upgrading itself back up to Opera 29.
Now ... I see in the Task Manager an opera_autoupdate process using up around the range of 10,380K. Of course it varies from time to time, but it is pretty consistent around that range.
Does that bottom line mean / indicate that an Opera Auto Update is IN PROGRESS? Or could that mean that the Auto Update function is READY for if I hadn't taken the measures to try and stop it? I mean, after all, I did supposedly DELETE the Opera Auto Update scheduled task in the Startup area with CCleaner.
IS the unwanted Opera Auto Update eating up into my already barely there Dial Up excuse for speed? Is it doing this constantly as I browse ... until it finishes downloading the entire Opera 29 update?
Would it stop if I clicked on "End Process" in the Task Manager?
Would it then subsequently all rogue-like create another opera_autoupdate process in the Task Manager and resume chapping my hide and making me see red? -
suntana last edited by
Well, my question was answered this morning. Opera 29 DID have the audacity to infiltrate, take hostage, hold my computer under seige. Yep! My Opera 27 auto updated to Opera 29 this morning. Grrrrrrrrrrrr! @#$% MAN! What is it going to take for the Devs to understand that this is NOT desired? It is a problem. Opera 29 is just about now achieving Rootkit / Ransomeware status. Sheesh!
-
-
suntana last edited by
Up to right before Opera 29 ... renaming the opera_autoupdate file to opera_autoupdate_Disabled ... and disabling or deleting the Opera autoupdate scheduled task in the Startup area with CCleaner used to do the trick. Heck, there recently I even went a step further and outright deleted the opera_autoupdate file instead of just renaming it. I thought I had seen Rafael Luik mention that. But, that didn't work either. And that's what I had gotten from this forum.
With the arrival of Opera 29, obviously that no longer remotely does the trick. I don't frequent these forums. I only sporadically check things out here. So if something new has come up that DOES work and hogties and keeps Opera 29 from taking over my computer, I am not aware of it. Toss me a link.
See, the thing is, these workarounds are getting ridiculous. We should not have to be going deep into the software jungle to execute complicated Special Forces missions simply to disable a freakin' Auto Update function ... something any and all Apps should already make easily available at the click of a button or by checking a box.
Right now as things are, it is the equivalent of one buying be it a car, a stereo, a computer or whatever and when some problem comes up, the only fix that one is given is for one to personally open up the product and go cut and splice wires ... or to reroute hoses or perform stuff that isn't normal for the consumer to be doing.
-
blackbird71 last edited by
...
See, the thing is, these workarounds are getting ridiculous. We should not have to be going deep into the software jungle to execute complicated Special Forces missions simply to disable a freakin' Auto Update function ... something any and all Apps should already make easily available at the click of a button or by checking a box. ...+1. What is failing to get through with enough force into development departments is that there are users who, for a variety of sound reasons, absolutely need to be able to block updates of whatever software. Virtually all software I've encountered still respects that - the exception being many of the Chromish products. Certainly there are sound and solid reasons a developer wants his software updated ASAP... but there are equally sound and solid reasons that the owner/operator of a system may not want updates on his system occurring outside his immediate control. Since the computer and how he uses it are HIS, I believe his hand holds more justification trump cards.
Continuing to force auto-updating is to force your product users facing such situations to employ other software instead, since little actual choice may be involved on their part (@suntana being on dial-up as but one case in point). This is unlike the situation with typical "features" where one is merely dealing with points of preference. The inclusion of an internal, user-accessible setting to allow a user to prevent auto-updating is an essential point of sound software design, and Opera ought to incorporate it.
-
suntana last edited by
I don't know, blackbird. I could be wrong, but I'm guessing the reason for this rogue auto updating behavior is because of some flawed belief that they're looking out for the users' best interest in the computer security area. To that I say that it is still our call as to what version of ANY app we prefer to use at any given time. Heck, in my backup computer, which has Windows 98SE, I actually use Opera 9.64. OMG! LOL Well, I actually WOULD have a newer version, but Opera 9.64 is the latest version that works with Windows 98 as I found out by attempting to try newer versions.
Anyway, once Opera 29 finally finished its unauthorized upgrade, there was a noticeable difference in my browsing speed now that it wasn't there in the background dragging down things by downloading itself for 1 or 2 days, diluting the barely available speed that I have with my Dial Up to begin with.
I guess I'll go check out some of the older threads to see if I can find the supposed newer, more solid Mercenary Hitman Opera Autoupdate Terminator solution that is supposed to be out there. Otherwise I'll have to go through this again when Opera 30 comes out.
-
59er last edited by
Since 29 does not work on my XP box, I blocked opera. exe 29.0.1795.47, Opera auto-update, and Opera Installer 29.0.1795.47 at the program settings of my firewall (OA Free). For Firewall settings I blocked oaui.exe and opera.exe 29.0.
(Non-firewall step) For good measure I renamed the installation_status.xml file in the Windows Opera program file. Not sure which did the trick but holding steady with Opera 28.
My previously renamed auto update files re-spawned in the Opera 28 file as before, but with the above steps this time 29 did not load. -
suntana last edited by
I can't do any of that Firewall stuff, 59er. I only have the Windows XP Firewall. And that one only has 1 instance of Opera there in the exceptions. If I delete that, Opera won't work.
-
blackbird71 last edited by
I don't know, blackbird. I could be wrong, but I'm guessing the reason for this rogue auto updating behavior is because of some flawed belief that they're looking out for the users' best interest in the computer security area. ...
I agree... that's why I said earlier there certainly are sound and solid reasons why developers would want their products updated by most users as soon as possible, once they release a newer version. And I have no problem with a product that arrives with a default setting to auto-update itself. PROVIDED that there is a readily accessible and effective setting in that same software for a user to block further updating should he deem that necessary on his system. My own guess is that chromium inherently is designed for auto updating, and expending developmental effort at Opera for adding a feature to the UI to block it is simply not very high on their list of things needing done - if it's on the list at all. However, this is one issue I believe which needs continuing user feedback to elevate its significance until an easy and effective user update-block setting is incorporated.
I have two friends who are both on limited income and both use dial-up service at home, much as you do. They have old laptop systems, and don't update any software until they can take the systems to a friend's home or commercial hotspot where wifi is available to do their software updating. If auto-updating can't be readily blocked, there's no way they want to tie up their phone line for the very long periods required by such a forced auto-update. So I've advised both of them to not install New Opera for that specific reason. In my own case, I have software that, when running, absolutely can't be interrupted or crashed by software auto-updating whenever it jolly well feels like it... which is particularly a very real situation if two separate programs decide to update themselves at the same time (which I've had happen). It's simply not a reasonable design principle to make software that autonomously consumes system resources, network connections, and perhaps the primary attention of the OS. The computer owner/operator is supposed be in charge of what his system does and when, if he so elects... and the settings should be immediately accessible within the software on his system.
-
bill-g last edited by
I know this is just another try to block autoupdate but it's easy and might work.
Create a zero-byte text file named "opera_autoupdate.exe", confirm the change extension varning and make the file write protected. Then replace the original "opera_autoupdate.exe" with this write-protected zero-byte file.
-
bill-g last edited by
"operaautoupdate.exe" should be "opera(underscore)autoupdate.exe" in the previous message. underscore made the text slanted (italic) for some reason.
"opera_autoupdate.exe" "opera_autoupdate.exe" "opera_autoupdate.exe" <-- very weird
-
-
jackscolon last edited by
Yeah, I'm "the only one disturbed by this." These fa99ots don't give a damn what you think, they don't care about their user's personal preferences, they only care about copying chrome.
FEEL MY HATE.
