Opera automatically updating from version 22 to 23 without my knowledge or permission
-
blackbird71 last edited byWhen Opera changes their code "unannounced", it affects only their browser and those choosing to use it. Websites are software with functions too, there are web apps, etc. Also, it's very possible leaving Opera outdated will affect websites' functions in the same way or worse than code changes in the new version.
So when does it start to matter? A website coding change potentially affects user interaction with only one site. A browser change potentially affects interaction with all the sites the user visits, or perhaps all the sites using a particular technology (eg Flash, etc).
In any case, what I was responding to in my original statement was @leocg's mention that "(almost) all software will" update with small and silent updates in the near future. If that is an accurate prediction, the software on a user's system will then be auto-updating at all manner of times, and the problems (yes, there WILL be problems) will pop up out of the blue leaving a user mystified as to what suddenly started causing them. I believe a wise user stays in touch with his system's configuration at any given time. That means he either manually updates software or has his updates occur on a scheduled basis so that he can determine more quickly what caused a sudden-appearing problem. Moreover, it allows him to stay abreast of other users' problems with a given update before committing his system to it, so that he can avoid it if the other users' problems matter to him.
An all-too-common offender of this sort currently are antivirus updates, most of which are silent (at least for signatures, and in many cases for program files), and some of which have a track record of sometimes breaking things. If "all" software moves in the silent-update direction, then chaos will indeed reign when a problem suddenly pops up in using a system or any software on it. Did the user get hacked? Was it a browser update? A Flash update? An OS update? An extension update? a hardware failure/intermittent? An AV update? Something the user did wrong? There's no user-evident trail of configuration changes and when they occurred... just that a problem suddenly appeared. Hence my earlier comment.
-
myopera23 last edited by
Very succinctly put! Nothing wrong with O silently updating bug or security fixes, but updating to a new version of O with new features potentially add new problems.
I don't want to be a guinea pig to test the latest version of O. O22 updated to O23 without my knowledge or permission, and that resulted in taskbar problems(see 'Opera always in foreground' thread).
Certainly it can be argued that this is a way to improve security by forcefully and universally removing software holes and flaws as they are revealed, patched, and updates pushed. But that comes at a great 'instability' cost, particularly to technically-informed users who stay abreast of security issues, run "tight" systems, employ layered security, and strive to keep their systems "stable" above all else. The answer is to give users control over if/when software on a system updates itself.
The reality is that every single piece of software has bugs, including every update. A user sometimes has to thread through a minefield of software incompatibilities and hiccups to get a system fully stabilized and smoothly running. An update invariably introduces different software behavior at some point or another that may or may not be evident as a conflict or problem. When a user performs a manual update, has a known scheduled update, or receives a clear and prominent alert that an update has occurred, he at least has a definitive starting point to troubleshoot any performance hiccups that may be the consequence of the update. With silent, forced updates, the user has no starting point for figuring out why things broke on his system - and the more software that pushes auto-updates, the greater the likelihood both that something will be broken by an update and that it will be unclear what its cause is. -
A Former User last edited by admin
See also here -
https://forums.opera.com/topic/4100/enforced-automatic-updates/1 -
myopera23 last edited by
This is the way Opera will work from now on, with small and silent updates.
I'd say that updating an entire version of O is not a small event.
-
Deleted User last edited by
This is the way Opera will work from now on, with small and silent updates.
I'd say that updating an entire version of O is not a small event.
Indeed
-
Deleted User last edited by
Always fighting. Always bickering about this point or that one. Everyone seems to have his opinion and readily defends it against all comers. Ah... pride is such a hard thing to relinquish. I'm right... you're wrong... so there!
Okay, I'll express my opinion as well (might as well). I agree with lem that notification of an upgrade should be provided BUT I'm not going to make this a deal-breaker as some have declared.
-
lem729 last edited by
I not that worried about the permission thing, other than, if you've changed features, let people know. It shows the browser is being worked on. And maybe I'll find the new features helpful. Indeed, if I"m aware of them I might use them.
By the way, on the "heart" features at the right of the address bar, I discovered if you go into Opera://flags, you can change that feature and go back to what was before by disabling it. I'm just mentioning that in case any users are unhappy with the change. For me, it's okay.On about Opera, under browser identification, you get the following: "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36 OPR/23.0.1522.60." Now that probably was what was there before, but it does have me puzzling, now that I'm focusing on it. Does anyone know why that's there? I mean if you're not using the User-Agent Switcher extension, I thought the browser automatically identifies as Opera.
-
-
-
leocg Moderator Volunteer last edited by
On about Opera, under browser identification, you get the following: "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36 OPR/23.0.1522.60." Now that probably was what was there before, but it does have me puzzling, now that I'm focusing on it. Does anyone know why that's there? I mean if you're not using the User-Agent Switcher extension, I thought the browser automatically identifies as Opera.
It's for compatibility and have been that way since Opera 15 iirc. What identifies it as Opera is the OPR/build part.
-
-
burkeknight last edited by
Auto update without permission, opening the browser automatically when doing so, is plain wrong. I also will stop using opera.
Also, your reply text area on this forum, reverts to smaller than one line when typing, making it hard to see what ytou are typing.Seems to me, opera needs to work on their customer relations, and the fact that auto-anything is being frowned upon now due to malware, etc. The also need to get a better community forum program.
-
myopera23 last edited by
Ok thanks. I'll just reinstall O22 and block autoupdate.exe.
It's no good. 'opera_autoupdate.exe' blocked, but O22 still manages to upgrade to O23. Even after reinstalling O22 whilst 'opera_autoupdate.exe' was already blocked.
Time to switch to Firefox/chrome. Shame, O22 was way more compatible with the websites I frequent than any other version.
-
myopera23 last edited by
Forgot to ask how to export bookmarks in O23? If I remember correctly, there was an option to export bookmarks to an html file in previous versions.
-
christoph142 last edited by
Why would you wanna keep an outdated version (unless you're on Windows 7 and experiencing this bloody Auto-hide bug)?
(You can start Opera with the
--disable-update
command line switch. But remember to remove it again when it's not necessary anymore to prevent ending up with outdated versions.) -
A Former User last edited by admin
Why would you wanna keep an outdated version (unless you're on Windows 7 and experiencing this bloody Auto-hide bug)?
There's no point, there's even a workaround for it: https://forums.opera.com/post/45986 -
indonesian last edited by
blackbird71 wrote:
When Opera changes their code "unannounced", it affects only their browser **and those choosing to use it. **Websites are software with functions too, there are web apps, etc. Also, it's very possible leaving Opera outdated will affect websites' functions in the same way or worse than code changes in the new version.
Very primitive minded answer! ....... or it could be agenda related .... because 1 + 1 = 2
Now I will search for a way how to disable this function created by Googles for known obvious reasons ......
**
Its not Opera we talking about ........ Its the Google way & system at work here!In case no one noticed yet!
**
Because its bad news in so many different ways......
**
**
The same thing just happened from the Opera Developer Version 24.0.1558.17 to Version: 24.0.1558.21 - Opera is up to date
**I just tried to fix up a problem with one extension & the upgrade runs in the back without me knowing about it!
Now something is working with the extension which did not work before; but now it does for mystical reasons!
So problem solving becomes imposable with such system for starters!!!
**__Sorry to say; but Auto update is not the way to go at all!!!
Downloading things into your computer without knowing it; is not the way to go! __
In my case I like to know exactly what & when things getting placed onto my computer
especially getting downloaded into my Program Files(86x) directory!!No, no I smell a big rat here!
**
Yes Mr. @blackbird71 you are right;
free man has free Will & free choice what to support and what not to support or blindly submits too; without thinking just past today!
Is it not especially these creators of software which are security fanatics?
So why does that not apply here downloading things into your personal computer without knowing about it?
Looks a bit like a double standard playing out here!
(Is this not all about it when it comes to your individual security of your own computer system?)
-
-
linuxmint7 last edited by
Everyone who is using the Opera Blink (Chromium based) browser, and complaining about the 'Auto-update' feature updating Opera without their knowledge needs to read the E.U.L text that was displayed (and they obviously agreed to) when Opera was installed. Specifically point 1, 2.3, 2.4 and 7.1.
The text can be found in the resource folder of where you installed the latest version of Opera in text format.
All clear now ?.
-
indonesian last edited by admin
No more arguments; we only needs solutions not any arguments in this world full of madness & control freaks! >>>>
Here we go boys & girls ...... for those which like & need it? ...... Simple Fix >> SOLVED FOR ME!
Opera automatically updating from version 22 to 23 without my knowledge or permission!
My quick workaround option! ....... SOLVED!
Op's Posting
__Here we go __.....
For starters I found these lines within my reg file>>>
Just play around with the two options & try the second option first by renaming the specific files ......
ONLY; then move to the registry if this was not enough?They must have joint these action operation with there Laucher.exe once executed!
Option 1):
Make a registry backup first & then remove these entries should to the trick!
Make a backup first & then Delete these entries :
HKEY_CLASSES_ROOT\OperaDeveloper\shell\open\command"C:\Program Files (x86)\Opera Developer\Launcher.exe" -noautoupdate -- "%1"
Make a backup first & then Delete this entry :
HKEY_CURRENT_USER\Software\Classes\OperaDeveloper\shell\open\command
"C:\Program Files (x86)\Opera Developer\Launcher.exe" -noautoupdate -- "%1"
Make a backup first & then Delete this entry :
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\OperaDeveloper\shell\open\command
"C:\Program Files (x86)\Opera Developer\Launcher.exe"
Option (2) which did do the trick for me:
You may just rename these files in your Program file location ........ just in case so they not getting called on & recreating the (reg) entry :Find these files & just rename them temporary until you ready to update your version to a new one:
File Locations depending which version you run:
- C:\Program Files (x86)\Opera\23.0.1522.60
0a) C:\Program Files (x86)\Opera\launcher.exe
-
C:\Program Files (x86)\Opera Developer\launcher.exe
-
C:\Program Files (x86)\Opera Developer\24.0.1558.17
-
C:\Program Files (x86)\Opera Developer\24.0.1558.21
2a, 3a) launcher.exe >>>> to >>> ( _launcher.exe )
2b, 3b) installer.exe >>>> to >>> ( _installer.exe )
3a, 3b) opera_autoupdate.exe >>>> to >>> ( opera_autoupdate.exe )
- & * Note: launcher_lib.dll >>>> to >>> ( _launcher_lib.dll ) >>> * Note: only works for Opera Developer (don't rename it on Stable version)
Also link all your Opera Shortcuts to the ( opera.exe ) directly so you bypassing the original Laucher.exe Shortcut which opens opera browser!
Now I can call up the individual versions & it will not override it through updating it appears!
You can watch the update proses result attempt in the ( About Opera page) beside the version number it shows up.
Should shows this message Version: 23.0.1522.60 - An error occurred while checking for update
Should shows this message (24.0.1558.17 - Failed to download update)
Should shows this message (24.0.1558.21- Failed to download update)
Or this message ( 24.0.1558.21 - An error occurred while checking for updates)
Or this message (24.0.1558.17 - An error occurred while checking for updates)
In my case only the renaming of all these files did the trick ......... no more updating!!
I actually did the renaming first & I did not need to remove any of the registry entry & it fails to update!1
Good! ........ problem solved at least for me!
Now I can call up the individual versions too!
Some more stuff here:
I love to solve problems
Regards:
MO
.
